[syzbot] kernel BUG in io_queue_async_work
13 views
Skip to first unread message
syzbot
Jul 12, 2021, 5:28:19 AM7/12/21
to asml.s...@gmail.com, ax...@kernel.dk, io-u...@vger.kernel.org, linux-...@vger.kernel.org, syzkall...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: e2f74b13 Add linux-next specific files for 20210708
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14fc6fb4300000
kernel config: https://syzkaller.appspot.com/x/.config?x=59e1e3bbc3afca75
dashboard link: https://syzkaller.appspot.com/bug?extid=d50e4f20cfad4510ec22
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d50e4f...@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at fs/io_uring.c:1293!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 18789 Comm: kworker/0:10 Not tainted 5.13.0-next-20210708-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events io_fallback_req_func
RIP: 0010:io_queue_async_work+0x539/0x5f0 fs/io_uring.c:1293
Code: 89 be 89 00 00 00 48 c7 c7 00 8a 9a 89 c6 05 28 5f 77 0b 01 e8 be e9 06 07 e9 6e ff ff ff e8 be 1e 95 ff 0f 0b e8 b7 1e 95 ff <0f> 0b e8 b0 1e 95 ff 0f 0b e9 1a fd ff ff e8 d4 2f db ff e9 47 fb
RSP: 0018:ffffc900032efba8 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff88802840c800 RCX: 0000000000000000
RDX: ffff888082e09c80 RSI: ffffffff81e07d49 RDI: ffff8880224da498
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000043736500
R10: ffffffff81e222ff R11: 0000000000000000 R12: ffff8880782e78c0
R13: 0000000000000019 R14: ffff88802840c8b0 R15: ffff8880782e7918
FS: 0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffe2796bd8c CR3: 000000000b68e000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__io_queue_sqe+0x913/0xf10 fs/io_uring.c:6444
io_req_task_submit+0x100/0x120 fs/io_uring.c:2020
io_fallback_req_func+0x81/0xb0 fs/io_uring.c:2437
process_one_work+0x98d/0x1630 kernel/workqueue.c:2276
worker_thread+0x658/0x11f0 kernel/workqueue.c:2422
kthread+0x3e5/0x4d0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
Modules linked in:
---[ end trace 4d51acadba583174 ]---
RIP: 0010:io_queue_async_work+0x539/0x5f0 fs/io_uring.c:1293
Code: 89 be 89 00 00 00 48 c7 c7 00 8a 9a 89 c6 05 28 5f 77 0b 01 e8 be e9 06 07 e9 6e ff ff ff e8 be 1e 95 ff 0f 0b e8 b7 1e 95 ff <0f> 0b e8 b0 1e 95 ff 0f 0b e9 1a fd ff ff e8 d4 2f db ff e9 47 fb
RSP: 0018:ffffc900032efba8 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff88802840c800 RCX: 0000000000000000
RDX: ffff888082e09c80 RSI: ffffffff81e07d49 RDI: ffff8880224da498
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000043736500
R10: ffffffff81e222ff R11: 0000000000000000 R12: ffff8880782e78c0
R13: 0000000000000019 R14: ffff88802840c8b0 R15: ffff8880782e7918
FS: 0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3dee45e000 CR3: 000000002dd4e000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot found the following issue on:
HEAD commit: e2f74b13 Add linux-next specific files for 20210708
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14fc6fb4300000
kernel config: https://syzkaller.appspot.com/x/.config?x=59e1e3bbc3afca75
dashboard link: https://syzkaller.appspot.com/bug?extid=d50e4f20cfad4510ec22
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d50e4f...@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at fs/io_uring.c:1293!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 18789 Comm: kworker/0:10 Not tainted 5.13.0-next-20210708-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events io_fallback_req_func
RIP: 0010:io_queue_async_work+0x539/0x5f0 fs/io_uring.c:1293
Code: 89 be 89 00 00 00 48 c7 c7 00 8a 9a 89 c6 05 28 5f 77 0b 01 e8 be e9 06 07 e9 6e ff ff ff e8 be 1e 95 ff 0f 0b e8 b7 1e 95 ff <0f> 0b e8 b0 1e 95 ff 0f 0b e9 1a fd ff ff e8 d4 2f db ff e9 47 fb
RSP: 0018:ffffc900032efba8 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff88802840c800 RCX: 0000000000000000
RDX: ffff888082e09c80 RSI: ffffffff81e07d49 RDI: ffff8880224da498
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000043736500
R10: ffffffff81e222ff R11: 0000000000000000 R12: ffff8880782e78c0
R13: 0000000000000019 R14: ffff88802840c8b0 R15: ffff8880782e7918
FS: 0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffe2796bd8c CR3: 000000000b68e000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__io_queue_sqe+0x913/0xf10 fs/io_uring.c:6444
io_req_task_submit+0x100/0x120 fs/io_uring.c:2020
io_fallback_req_func+0x81/0xb0 fs/io_uring.c:2437
process_one_work+0x98d/0x1630 kernel/workqueue.c:2276
worker_thread+0x658/0x11f0 kernel/workqueue.c:2422
kthread+0x3e5/0x4d0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
Modules linked in:
---[ end trace 4d51acadba583174 ]---
RIP: 0010:io_queue_async_work+0x539/0x5f0 fs/io_uring.c:1293
Code: 89 be 89 00 00 00 48 c7 c7 00 8a 9a 89 c6 05 28 5f 77 0b 01 e8 be e9 06 07 e9 6e ff ff ff e8 be 1e 95 ff 0f 0b e8 b7 1e 95 ff <0f> 0b e8 b0 1e 95 ff 0f 0b e9 1a fd ff ff e8 d4 2f db ff e9 47 fb
RSP: 0018:ffffc900032efba8 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff88802840c800 RCX: 0000000000000000
RDX: ffff888082e09c80 RSI: ffffffff81e07d49 RDI: ffff8880224da498
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000043736500
R10: ffffffff81e222ff R11: 0000000000000000 R12: ffff8880782e78c0
R13: 0000000000000019 R14: ffff88802840c8b0 R15: ffff8880782e7918
FS: 0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3dee45e000 CR3: 000000002dd4e000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
Pavel Begunkov
Jul 12, 2021, 9:00:29 AM7/12/21
to syzbot, ax...@kernel.dk, io-u...@vger.kernel.org, linux-...@vger.kernel.org, syzkall...@googlegroups.com
On 7/12/21 10:28 AM, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: e2f74b13 Add linux-next specific files for 20210708
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=14fc6fb4300000
> kernel config: https://syzkaller.appspot.com/x/.config?x=59e1e3bbc3afca75
> dashboard link: https://syzkaller.appspot.com/bug?extid=d50e4f20cfad4510ec22
>
> Unfortunately, I don't have any reproducer for this issue yet.
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+d50e4f...@syzkaller.appspotmail.com
[...]
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: e2f74b13 Add linux-next specific files for 20210708
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=14fc6fb4300000
> kernel config: https://syzkaller.appspot.com/x/.config?x=59e1e3bbc3afca75
> dashboard link: https://syzkaller.appspot.com/bug?extid=d50e4f20cfad4510ec22
>
> Unfortunately, I don't have any reproducer for this issue yet.
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+d50e4f...@syzkaller.appspotmail.com
> __io_queue_sqe+0x913/0xf10 fs/io_uring.c:6444
Shouldn't have got here from fallback, so very similar to a bug fixed
by an already sent "io_uring: use right task for exiting checks"
Pavel Begunkov
syzbot
Jul 12, 2021, 9:19:19 PM7/12/21
to asml.s...@gmail.com, ax...@kernel.dk, io-u...@vger.kernel.org, linux-...@vger.kernel.org, syzkall...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 7fef2edf sd: don't mess with SD_MINORS for CONFIG_DEBUG_BL..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1575c9b0300000
kernel config: https://syzkaller.appspot.com/x/.config?x=957eaf08bd3bb8d6
dashboard link: https://syzkaller.appspot.com/bug?extid=d50e4f20cfad4510ec22
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=104c3949d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=167cc06c300000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d50e4f...@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at fs/io_uring.c:1293!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 8139 Comm: kworker/1:3 Tainted: G W 5.14.0-rc1-syzkaller #0
RSP: 0018:ffffc9000c627ba8 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff88802d256000 RCX: 0000000000000000
RDX: ffff888030f4e180 RSI: ffffffff81df55c9 RDI: ffff88802ef66a50
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000019
R10: ffffffff81df517c R11: 000000000000000f R12: ffff8880441eb6c0
R13: 0000000000000019 R14: ffff88802d2560b0 R15: ffff8880441eb718
FS: 0000000000000000(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
io_req_task_submit+0x100/0x120 fs/io_uring.c:2020
io_fallback_req_func+0x81/0xb0 fs/io_uring.c:2441
RSP: 0018:ffffc9000c627ba8 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff88802d256000 RCX: 0000000000000000
RDX: ffff888030f4e180 RSI: ffffffff81df55c9 RDI: ffff88802ef66a50
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000019
R10: ffffffff81df517c R11: 000000000000000f R12: ffff8880441eb6c0
R13: 0000000000000019 R14: ffff88802d2560b0 R15: ffff8880441eb718
FS: 0000000000000000(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
HEAD commit: 7fef2edf sd: don't mess with SD_MINORS for CONFIG_DEBUG_BL..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1575c9b0300000
kernel config: https://syzkaller.appspot.com/x/.config?x=957eaf08bd3bb8d6
dashboard link: https://syzkaller.appspot.com/bug?extid=d50e4f20cfad4510ec22
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=104c3949d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=167cc06c300000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d50e4f...@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at fs/io_uring.c:1293!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events io_fallback_req_func
RIP: 0010:io_queue_async_work+0x539/0x5f0 fs/io_uring.c:1293
Code: 89 be 89 00 00 00 48 c7 c7 40 53 9a 89 c6 05 de 38 78 0b 01 e8 72 6b 08 07 e9 6e ff ff ff e8 ee 68 95 ff 0f 0b e8 e7 68 95 ff <0f> 0b e8 e0 68 95 ff 0f 0b e9 1a fd ff ff e8 34 0f db ff e9 47 fb
Workqueue: events io_fallback_req_func
RIP: 0010:io_queue_async_work+0x539/0x5f0 fs/io_uring.c:1293
RSP: 0018:ffffc9000c627ba8 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff88802d256000 RCX: 0000000000000000
RDX: ffff888030f4e180 RSI: ffffffff81df55c9 RDI: ffff88802ef66a50
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000019
R10: ffffffff81df517c R11: 000000000000000f R12: ffff8880441eb6c0
R13: 0000000000000019 R14: ffff88802d2560b0 R15: ffff8880441eb718
FS: 0000000000000000(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000049a01d CR3: 00000000396af000 CR4: 00000000001506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__io_queue_sqe+0x913/0xf10 fs/io_uring.c:6448
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
io_req_task_submit+0x100/0x120 fs/io_uring.c:2020
io_fallback_req_func+0x81/0xb0 fs/io_uring.c:2441
process_one_work+0x98d/0x1630 kernel/workqueue.c:2276
worker_thread+0x658/0x11f0 kernel/workqueue.c:2422
kthread+0x3e5/0x4d0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
Modules linked in:
---[ end trace aa15edd5dcdbd7e3 ]---
worker_thread+0x658/0x11f0 kernel/workqueue.c:2422
kthread+0x3e5/0x4d0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
Modules linked in:
RIP: 0010:io_queue_async_work+0x539/0x5f0 fs/io_uring.c:1293
Code: 89 be 89 00 00 00 48 c7 c7 40 53 9a 89 c6 05 de 38 78 0b 01 e8 72 6b 08 07 e9 6e ff ff ff e8 ee 68 95 ff 0f 0b e8 e7 68 95 ff <0f> 0b e8 e0 68 95 ff 0f 0b e9 1a fd ff ff e8 34 0f db ff e9 47 fb
RSP: 0018:ffffc9000c627ba8 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff88802d256000 RCX: 0000000000000000
RDX: ffff888030f4e180 RSI: ffffffff81df55c9 RDI: ffff88802ef66a50
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000019
R10: ffffffff81df517c R11: 000000000000000f R12: ffff8880441eb6c0
R13: 0000000000000019 R14: ffff88802d2560b0 R15: ffff8880441eb718
FS: 0000000000000000(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000444 CR3: 0000000042660000 CR4: 00000000001506e0
Pavel Begunkov
Jul 13, 2021, 4:37:33 AM7/13/21
to syzbot, ax...@kernel.dk, io-u...@vger.kernel.org, linux-...@vger.kernel.org, syzkall...@googlegroups.com
On 7/13/21 2:19 AM, syzbot wrote:
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: 7fef2edf sd: don't mess with SD_MINORS for CONFIG_DEBUG_BL..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1575c9b0300000
> kernel config: https://syzkaller.appspot.com/x/.config?x=957eaf08bd3bb8d6
> dashboard link: https://syzkaller.appspot.com/bug?extid=d50e4f20cfad4510ec22
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=104c3949d00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=167cc06c300000
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+d50e4f...@syzkaller.appspotmail.com
#syz test: https://github.com/isilence/linux.git drain_fix_syztest
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: 7fef2edf sd: don't mess with SD_MINORS for CONFIG_DEBUG_BL..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1575c9b0300000
> kernel config: https://syzkaller.appspot.com/x/.config?x=957eaf08bd3bb8d6
> dashboard link: https://syzkaller.appspot.com/bug?extid=d50e4f20cfad4510ec22
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=104c3949d00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=167cc06c300000
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+d50e4f...@syzkaller.appspotmail.com
Pavel Begunkov
syzbot
Jul 13, 2021, 7:02:07 AM7/13/21
to asml.s...@gmail.com, ax...@kernel.dk, io-u...@vger.kernel.org, linux-...@vger.kernel.org, syzkall...@googlegroups.com
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+d50e4f...@syzkaller.appspotmail.com
Tested on:
commit: 66af6ccf io_uring: fix io_drain_req()
git tree: https://github.com/isilence/linux.git drain_fix_syztest
kernel config: https://syzkaller.appspot.com/x/.config?x=77d8505826d1a1c4
dashboard link: https://syzkaller.appspot.com/bug?extid=d50e4f20cfad4510ec22
compiler:
Note: testing is done by a robot and is best-effort only.
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+d50e4f...@syzkaller.appspotmail.com
Tested on:
commit: 66af6ccf io_uring: fix io_drain_req()
git tree: https://github.com/isilence/linux.git drain_fix_syztest
kernel config: https://syzkaller.appspot.com/x/.config?x=77d8505826d1a1c4
dashboard link: https://syzkaller.appspot.com/bug?extid=d50e4f20cfad4510ec22
compiler:
Note: testing is done by a robot and is best-effort only.
syzbot
Sep 26, 2022, 10:18:30 PM9/26/22
to syzkall...@googlegroups.com
Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.
No recent activity, existing reproducers are no longer triggering the issue.
Reply all
Reply to author
Forward
0 new messages