From: syzbot <syzbot+3562be49b8e09d424a6f@syzkaller.appspotmail.com>
To: axboe@kernel.dk, efremov@linux.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in wait_til_done
Date: Sat, 28 May 2022 13:46:29 -0700 [thread overview]
Message-ID: <000000000000743f8505e0188496@google.com> (raw)
In-Reply-To: <000000000000361f9005dd7fea88@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 9d004b2f4fea Merge tag 'cxl-for-5.19' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=118576f3f00000
kernel config: https://syzkaller.appspot.com/x/.config?x=34d5ab77e4ca65e1
dashboard link: https://syzkaller.appspot.com/bug?extid=3562be49b8e09d424a6f
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10f15913f00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=157ad36bf00000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+3562be49b8e09d424a6f@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 3690 at drivers/block/floppy.c:999 schedule_bh drivers/block/floppy.c:999 [inline]
WARNING: CPU: 0 PID: 3690 at drivers/block/floppy.c:999 wait_til_done+0x350/0x3c0 drivers/block/floppy.c:2018
Modules linked in:
CPU: 0 PID: 3690 Comm: syz-executor202 Not tainted 5.18.0-syzkaller-10643-g9d004b2f4fea #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014
RIP: 0010:schedule_bh drivers/block/floppy.c:999 [inline]
RIP: 0010:wait_til_done+0x350/0x3c0 drivers/block/floppy.c:2018
Code: fc 41 83 fd 01 7e ac e8 8e 1e e0 fc 4c 89 e6 48 c7 c7 20 7b 8e 8c e8 8f b4 c0 fc e8 7a 1e e0 fc e9 c3 fd ff ff e8 70 1e e0 fc <0f> 0b e9 4b fd ff ff e8 54 38 2c fd e9 0f fe ff ff e8 5a 1e e0 fc
RSP: 0018:ffffc90002f8f718 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 1ffff920005f1ee3 RCX: 0000000000000000
RDX: ffff88801430c140 RSI: ffffffff84998450 RDI: 0000000000000007
RBP: 0000000000000000 R08: 0000000000000007 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000001
R13: ffffffff84995460 R14: 0000000000000000 R15: 0000000000000003
FS: 0000555556c30300(0000) GS:ffff88802ca00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000088 CR3: 000000002457a000 CR4: 0000000000150ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
floppy_check_events+0x3d0/0x560 drivers/block/floppy.c:4098
disk_check_events+0xc2/0x420 block/disk-events.c:193
disk_clear_events block/disk-events.c:248 [inline]
bdev_check_media_change+0x12c/0x310 block/disk-events.c:279
floppy_open+0x75d/0xd70 drivers/block/floppy.c:4057
blkdev_get_whole+0x99/0x2d0 block/bdev.c:673
blkdev_get_by_dev.part.0+0x5ec/0xb90 block/bdev.c:823
blkdev_get_by_dev+0x6b/0x80 block/bdev.c:857
blkdev_open+0x13c/0x2c0 block/fops.c:481
do_dentry_open+0x4a1/0x11f0 fs/open.c:824
do_open fs/namei.c:3477 [inline]
path_openat+0x1c71/0x2910 fs/namei.c:3610
do_filp_open+0x1aa/0x400 fs/namei.c:3637
do_sys_openat2+0x16d/0x4c0 fs/open.c:1254
do_sys_open fs/open.c:1270 [inline]
__do_sys_openat fs/open.c:1286 [inline]
__se_sys_openat fs/open.c:1281 [inline]
__x64_sys_openat+0x13f/0x1f0 fs/open.c:1281
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x46/0xb0
RIP: 0033:0x7f936c227597
Code: 25 00 00 41 00 3d 00 00 41 00 74 47 64 8b 04 25 18 00 00 00 85 c0 75 6b 44 89 e2 48 89 ee bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 95 00 00 00 48 8b 4c 24 28 64 48 2b 0c 25
RSP: 002b:00007ffc43d5dfb0 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f936c227597
RDX: 0000000000000000 RSI: 00007ffc43d5e030 RDI: 00000000ffffff9c
RBP: 00007ffc43d5e030 R08: 000000000000ffff R09: 00007ffc43d5dec0
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 431bde82d7b634db R14: 0000000000000000 R15: 0000000000000000
</TASK>
prev parent reply other threads:[~2022-05-28 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 19:52 [syzbot] WARNING in wait_til_done syzbot
2022-05-28 20:46 ` 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=000000000000743f8505e0188496@google.com \
--to=syzbot+3562be49b8e09d424a6f@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=efremov@linux.com \
--cc=linux-block@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.