From: Pavel Begunkov <[email protected]>
To: syzbot <[email protected]>,
[email protected], [email protected], [email protected],
[email protected], [email protected]
Subject: Re: [syzbot] WARNING in io_ring_exit_work
Date: Fri, 6 Aug 2021 10:20:00 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
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
next prev parent reply other threads:[~2021-08-06 9:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2021-08-06 10:33 ` syzbot
2021-08-06 15:21 ` syzbot
2023-05-29 7:58 ` [syzbot] [io-uring?] " syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox