From: syzbot <[email protected]>
To: [email protected], [email protected],
[email protected], [email protected],
[email protected]
Subject: [syzbot] WARNING in io_rsrc_node_switch
Date: Thu, 29 Apr 2021 03:22:18 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: d72cd4ad Merge tag 'scsi-misc' of git://git.kernel.org/pub..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=143aae7dd00000
kernel config: https://syzkaller.appspot.com/x/.config?x=65c207250bba4efe
dashboard link: https://syzkaller.appspot.com/bug?extid=a4715dd4b7c866136f79
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]
R13: 0000000020ffc000 R14: 0000000020000040 R15: 0000000020ee7000
------------[ cut here ]------------
WARNING: CPU: 1 PID: 27734 at fs/io_uring.c:7081 io_rsrc_node_switch+0x2a5/0x390 fs/io_uring.c:7081
Modules linked in:
CPU: 1 PID: 27734 Comm: syz-executor.1 Not tainted 5.12.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:io_rsrc_node_switch+0x2a5/0x390 fs/io_uring.c:7081
Code: ff 4d 85 e4 74 a4 48 83 c4 20 5b 5d 41 5c 41 5d 41 5e 41 5f e9 fc 00 99 ff e8 f7 00 99 ff 0f 0b e9 ee fd ff ff e8 eb 00 99 ff <0f> 0b e9 9d fd ff ff 4c 89 f7 e8 7c e0 dc ff eb 8b 4c 89 ef e8 72
RSP: 0018:ffffc9000a407d90 EFLAGS: 00010246
RAX: 0000000000040000 RBX: ffff888093390000 RCX: ffffc9000af4b000
RDX: 0000000000040000 RSI: ffffffff81db5d25 RDI: ffff888093390000
RBP: 0000000000000000 R08: 0000000000000dc0 R09: ffffffff8c0b37d3
R10: fffffbfff18166fa R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: ffff888093390808 R15: 0000000000000000
FS: 00007f6a99229700(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000563680f98258 CR3: 0000000096847000 CR4: 0000000000350ef0
Call Trace:
io_uring_create fs/io_uring.c:9611 [inline]
io_uring_setup+0xf75/0x2a80 fs/io_uring.c:9689
do_syscall_64+0x3a/0xb0 arch/x86/entry/common.c:47
entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x4665f9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f6a99229108 EFLAGS: 00000202 ORIG_RAX: 00000000000001a9
RAX: ffffffffffffffda RBX: 000000000056bf60 RCX: 00000000004665f9
RDX: 0000000020ffc000 RSI: 00000000200002c0 RDI: 0000000000000182
RBP: 00000000200002c0 R08: 00000000200001c0 R09: 00000000200001c0
R10: 0000000020000040 R11: 0000000000000202 R12: 00000000200001c0
R13: 0000000020ffc000 R14: 0000000020000040 R15: 0000000020ee7000
---
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.
next reply other threads:[~2021-04-29 10:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 10:22 syzbot [this message]
2021-04-29 10:32 ` [syzbot] WARNING in io_rsrc_node_switch syzbot
2021-04-29 11:49 ` Pavel Begunkov
2021-04-29 14:18 ` syzbot
2021-04-29 14:00 ` 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] \
/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