* [syzbot] WARNING in io_ring_exit_work
@ 2021-03-15 19:08 syzbot
2021-08-06 7:02 ` syzbot
` (2 more replies)
0 siblings, 3 replies; 6+ messages in thread
From: syzbot @ 2021-03-15 19:08 UTC (permalink / raw)
To: asml.silence, axboe, io-uring, linux-kernel, syzkaller-bugs
Hello,
syzbot found the following issue on:
HEAD commit: b01d57bf Add linux-next specific files for 20210310
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10ae049ed00000
kernel config: https://syzkaller.appspot.com/x/.config?x=95af83fd326c2b5
dashboard link: https://syzkaller.appspot.com/bug?extid=00e15cda746c5bc70e24
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: [email protected]
------------[ cut here ]------------
WARNING: CPU: 0 PID: 225 at fs/io_uring.c:8456 io_ring_exit_work+0x130/0xcf0 fs/io_uring.c:8456
Modules linked in:
CPU: 0 PID: 225 Comm: kworker/u4:5 Not tainted 5.12.0-rc2-next-20210310-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events_unbound io_ring_exit_work
RIP: 0010:io_ring_exit_work+0x130/0xcf0 fs/io_uring.c:8456
Code: 7d 00 00 0f 85 bf 09 00 00 48 8b 05 3a 15 e5 09 4d 89 f5 31 ff 49 29 c5 4c 89 ee e8 6a 09 98 ff 4d 85 ed 79 a5 e8 40 01 98 ff <0f> 0b eb 9c e8 37 01 98 ff 31 f6 49 bf 00 00 00 00 00 fc ff df 4c
RSP: 0018:ffffc9000163fbc8 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff88801dd36930 RCX: 0000000000000000
RDX: ffff8880120d9c00 RSI: ffffffff81dbdc60 RDI: 0000000000000003
RBP: fffffbfff1781e30 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffff81dbdc56 R11: 0000000000000000 R12: ffff88801dd364e0
R13: fffffffffffffffe R14: 00000001000040a4 R15: ffff88801dd36000
FS: 0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fcf0ff32000 CR3: 00000000180fb000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
process_one_work+0x98d/0x1600 kernel/workqueue.c:2275
worker_thread+0x64c/0x1120 kernel/workqueue.c:2421
kthread+0x3b1/0x4a0 kernel/kthread.c:292
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294
---
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 [email protected].
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [syzbot] WARNING in io_ring_exit_work
2021-03-15 19:08 [syzbot] WARNING in io_ring_exit_work syzbot
@ 2021-08-06 7:02 ` syzbot
2021-08-06 9:20 ` Pavel Begunkov
2021-08-06 15:21 ` syzbot
2023-05-29 7:58 ` [syzbot] [io-uring?] " syzbot
2 siblings, 1 reply; 6+ messages in thread
From: syzbot @ 2021-08-06 7:02 UTC (permalink / raw)
To: asml.silence, axboe, hdanton, io-uring, linux-kernel, syzkaller-bugs
syzbot has found a reproducer for the following issue on:
HEAD commit: 8d4b477da1a8 Add linux-next specific files for 20210730
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1478e4fa300000
kernel config: https://syzkaller.appspot.com/x/.config?x=4adf4987f875c210
dashboard link: https://syzkaller.appspot.com/bug?extid=00e15cda746c5bc70e24
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15d5cd96300000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1798471e300000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email protected]
------------[ cut here ]------------
WARNING: CPU: 1 PID: 1182 at fs/io_uring.c:8802 io_ring_exit_work+0x24e/0x1600 fs/io_uring.c:8802
Modules linked in:
CPU: 1 PID: 1182 Comm: kworker/u4:5 Not tainted 5.14.0-rc3-next-20210730-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events_unbound io_ring_exit_work
RIP: 0010:io_ring_exit_work+0x24e/0x1600 fs/io_uring.c:8802
Code: 30 11 00 00 48 8b 05 c1 dc 80 09 31 ff 48 8b 2c 24 48 29 c5 48 89 ee e8 c0 a8 95 ff 48 85 ed 0f 89 a8 fe ff ff e8 52 a3 95 ff <0f> 0b e9 9c fe ff ff e8 46 a3 95 ff 48 c7 c2 c0 25 2a 90 48 c7 c6
RSP: 0018:ffffc90004ed7b98 EFLAGS: 00010293
RAX: 0000000000000000 RBX: dffffc0000000000 RCX: 0000000000000000
RDX: ffff88801c921c80 RSI: ffffffff81e014de RDI: 0000000000000003
RBP: ffffffffffffffff R08: 0000000000000000 R09: 0000000000000000
R10: ffffffff81e014d0 R11: 0000000000000000 R12: fffffbfff16c1e30
R13: ffffed100e3f4894 R14: ffff888071fa4920 R15: ffff888071fa4000
FS: 0000000000000000(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000488 CR3: 00000001c82cf000 CR4: 00000000001506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [syzbot] WARNING in io_ring_exit_work
2021-08-06 7:02 ` syzbot
@ 2021-08-06 9:20 ` Pavel Begunkov
2021-08-06 10:33 ` syzbot
0 siblings, 1 reply; 6+ messages in thread
From: Pavel Begunkov @ 2021-08-06 9:20 UTC (permalink / raw)
To: syzbot, axboe, hdanton, io-uring, linux-kernel, syzkaller-bugs
On 8/6/21 8:02 AM, syzbot wrote:
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: 8d4b477da1a8 Add linux-next specific files for 20210730
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=1478e4fa300000
> kernel config: https://syzkaller.appspot.com/x/.config?x=4adf4987f875c210
> dashboard link: https://syzkaller.appspot.com/bug?extid=00e15cda746c5bc70e24
> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15d5cd96300000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1798471e300000
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: [email protected]
#syz test: git://git.kernel.dk/linux-block io_uring-5.14
>
> ------------[ cut here ]------------
> WARNING: CPU: 1 PID: 1182 at fs/io_uring.c:8802 io_ring_exit_work+0x24e/0x1600 fs/io_uring.c:8802
> Modules linked in:
> CPU: 1 PID: 1182 Comm: kworker/u4:5 Not tainted 5.14.0-rc3-next-20210730-syzkaller #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
> Workqueue: events_unbound io_ring_exit_work
> RIP: 0010:io_ring_exit_work+0x24e/0x1600 fs/io_uring.c:8802
> Code: 30 11 00 00 48 8b 05 c1 dc 80 09 31 ff 48 8b 2c 24 48 29 c5 48 89 ee e8 c0 a8 95 ff 48 85 ed 0f 89 a8 fe ff ff e8 52 a3 95 ff <0f> 0b e9 9c fe ff ff e8 46 a3 95 ff 48 c7 c2 c0 25 2a 90 48 c7 c6
> RSP: 0018:ffffc90004ed7b98 EFLAGS: 00010293
> RAX: 0000000000000000 RBX: dffffc0000000000 RCX: 0000000000000000
> RDX: ffff88801c921c80 RSI: ffffffff81e014de RDI: 0000000000000003
> RBP: ffffffffffffffff R08: 0000000000000000 R09: 0000000000000000
> R10: ffffffff81e014d0 R11: 0000000000000000 R12: fffffbfff16c1e30
> R13: ffffed100e3f4894 R14: ffff888071fa4920 R15: ffff888071fa4000
> FS: 0000000000000000(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 0000000020000488 CR3: 00000001c82cf000 CR4: 00000000001506e0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> Call Trace:
> 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
>
--
Pavel Begunkov
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [syzbot] WARNING in io_ring_exit_work
2021-03-15 19:08 [syzbot] WARNING in io_ring_exit_work syzbot
2021-08-06 7:02 ` syzbot
@ 2021-08-06 15:21 ` syzbot
2023-05-29 7:58 ` [syzbot] [io-uring?] " syzbot
2 siblings, 0 replies; 6+ messages in thread
From: syzbot @ 2021-08-06 15:21 UTC (permalink / raw)
To: asml.silence, axboe, gregkh, hdanton, io-uring, linux-kernel,
rafael, syzkaller-bugs
syzbot has bisected this issue to:
commit 6c2450ae55656f6b0370bfd4cb52ec8a4ecd0916
Author: Pavel Begunkov <[email protected]>
Date: Tue Feb 23 12:40:22 2021 +0000
io_uring: allocate memory for overflowed CQEs
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=138a96e6300000
start commit: 8d4b477da1a8 Add linux-next specific files for 20210730
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=104a96e6300000
console output: https://syzkaller.appspot.com/x/log.txt?x=178a96e6300000
kernel config: https://syzkaller.appspot.com/x/.config?x=4adf4987f875c210
dashboard link: https://syzkaller.appspot.com/bug?extid=00e15cda746c5bc70e24
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15d5cd96300000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1798471e300000
Reported-by: [email protected]
Fixes: 6c2450ae5565 ("io_uring: allocate memory for overflowed CQEs")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [syzbot] [io-uring?] WARNING in io_ring_exit_work
2021-03-15 19:08 [syzbot] WARNING in io_ring_exit_work syzbot
2021-08-06 7:02 ` syzbot
2021-08-06 15:21 ` syzbot
@ 2023-05-29 7:58 ` syzbot
2 siblings, 0 replies; 6+ messages in thread
From: syzbot @ 2023-05-29 7:58 UTC (permalink / raw)
To: asml.silence, axboe, deller, gregkh, hdanton, io-uring,
linux-kernel, rafael, syzkaller-bugs
syzbot suspects this issue was fixed by commit:
commit d808459b2e31bd5123a14258a7a529995db974c8
Author: Helge Deller <[email protected]>
Date: Thu Feb 16 08:09:38 2023 +0000
io_uring: Adjust mapping wrt architecture aliasing requirements
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=145bb249280000
start commit: 7c6984405241 Merge tag 'iommu-fixes-v6.2-rc3' of git://git..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=2b6ecad960fc703e
dashboard link: https://syzkaller.appspot.com/bug?extid=00e15cda746c5bc70e24
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15d5e97e480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1407c8da480000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: io_uring: Adjust mapping wrt architecture aliasing requirements
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2023-05-29 7:58 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-03-15 19:08 [syzbot] WARNING in io_ring_exit_work syzbot
2021-08-06 7:02 ` syzbot
2021-08-06 9:20 ` Pavel Begunkov
2021-08-06 10:33 ` syzbot
2021-08-06 15:21 ` syzbot
2023-05-29 7:58 ` [syzbot] [io-uring?] " syzbot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox