From: syzbot <syzbot+b0c9d1588ae92866515f@syzkaller.appspotmail.com>
To: asml.silence@gmail.com, axboe@kernel.dk, hdanton@sina.com,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in io_try_cancel_userdata
Date: Mon, 23 Aug 2021 15:14:25 -0700 [thread overview]
Message-ID: <00000000000003bb1805ca4157a5@google.com> (raw)
In-Reply-To: <000000000000dd79fc05ca367b9d@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 46debfec12b4 Add linux-next specific files for 20210823
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=12f00c39300000
kernel config: https://syzkaller.appspot.com/x/.config?x=49609005dc034be7
dashboard link: https://syzkaller.appspot.com/bug?extid=b0c9d1588ae92866515f
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=15830bee300000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b0c9d1588ae92866515f@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 7008 at fs/io_uring.c:6082 io_try_cancel_userdata+0x30d/0x540 fs/io_uring.c:6082
Modules linked in:
CPU: 0 PID: 7008 Comm: iou-wrk-7007 Not tainted 5.14.0-rc7-next-20210823-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:io_try_cancel_userdata+0x30d/0x540 fs/io_uring.c:6082
Code: 52 07 e8 66 67 95 ff 48 8b 3c 24 e8 ad 67 52 07 e9 71 fe ff ff e8 53 67 95 ff 41 bf 8e ff ff ff e9 61 fe ff ff e8 43 67 95 ff <0f> 0b 48 b8 00 00 00 00 00 fc ff df 4c 89 fa 48 c1 ea 03 80 3c 02
RSP: 0018:ffffc90003fefac0 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff88801d064c80 RCX: 0000000000000000
RDX: ffff88801ea75580 RSI: ffffffff81e078fd RDI: ffff88801d064cd0
RBP: ffff88801ea75580 R08: ffffffff899adde0 R09: ffffffff81e1e4e4
R10: 0000000000000027 R11: 000000000000000e R12: 1ffff920007fdf59
R13: 0000000000012345 R14: ffff888146628000 R15: ffff88801d064ce0
FS: 00007f0c5b7d6700(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffc3bfd8720 CR3: 0000000070d9c000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
io_async_cancel fs/io_uring.c:6122 [inline]
io_issue_sqe+0x22d5/0x67b0 fs/io_uring.c:6515
io_wq_submit_work+0x1d4/0x300 fs/io_uring.c:6619
io_worker_handle_work+0x1584/0x1810 fs/io-wq.c:533
io_wqe_worker+0x9cd/0xbb0 fs/io-wq.c:606
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
prev parent reply other threads:[~2021-08-23 22:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 9:17 [syzbot] WARNING in io_try_cancel_userdata syzbot
2021-08-23 11:36 ` Pavel Begunkov
2021-08-23 12:33 ` Pavel Begunkov
2021-08-23 22:14 ` syzbot [this message]
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 \
--in-reply-to=00000000000003bb1805ca4157a5@google.com \
--to=syzbot+b0c9d1588ae92866515f@syzkaller.appspotmail.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=hdanton@sina.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.