From: syzbot <syzbot+e89a1109c376e2c3c389@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: [syzbot] WARNING in schedule_bh (2)
Date: Mon, 07 Feb 2022 13:15:20 -0800 [thread overview]
Message-ID: <0000000000001733e105d77419fe@google.com> (raw)
syzbot has found a reproducer for the following issue on:
HEAD commit: dfd42facf1e4 Linux 5.17-rc3
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=145b5a28700000
kernel config: https://syzkaller.appspot.com/x/.config?x=266de9da75c71a45
dashboard link: https://syzkaller.appspot.com/bug?extid=e89a1109c376e2c3c389
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: i386
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15572b0c700000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1220d968700000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e89a1109c376e2c3c389@syzkaller.appspotmail.com
floppy1: floppy timeout called
------------[ cut here ]------------
WARNING: CPU: 0 PID: 11 at drivers/block/floppy.c:1000 schedule_bh+0x5f/0x70 drivers/block/floppy.c:1000
Modules linked in:
CPU: 0 PID: 11 Comm: kworker/u16:1 Not tainted 5.17.0-rc3-syzkaller #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014
Workqueue: floppy floppy_shutdown
RIP: 0010:schedule_bh+0x5f/0x70 drivers/block/floppy.c:1000
Code: d7 65 fd fc 48 89 2d 20 c8 03 0c 5b 48 c7 c2 80 d0 6a 8c 48 8b 35 f1 cc 03 0c bf 08 00 00 00 5d e9 46 9a d1 fc e8 b1 65 fd fc <0f> 0b eb d1 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 e8 9b 65 fd fc
RSP: 0018:ffffc900003cfcf8 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000000
RDX: ffff888010feba00 RSI: ffffffff847b12df RDI: 0000000000000003
RBP: ffffffff847bc790 R08: 0000000000000000 R09: ffffffff8c6ad087
R10: ffffffff847b12af R11: 0000000000000000 R12: 0000000000000001
R13: ffffc900003cfdb8 R14: ffff888010db3e00 R15: ffff888010c71800
FS: 0000000000000000(0000) GS:ffff88802cb00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000f7ea1db0 CR3: 000000001f15c000 CR4: 0000000000150ee0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
floppy_shutdown+0x129/0x170 drivers/block/floppy.c:1890
process_one_work+0x9ac/0x1650 kernel/workqueue.c:2307
worker_thread+0x657/0x1110 kernel/workqueue.c:2454
kthread+0x2e9/0x3a0 kernel/kthread.c:377
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
next reply other threads:[~2022-02-07 21:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 21:15 syzbot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-01 12:37 [syzbot] WARNING in schedule_bh (2) 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 \
--in-reply-to=0000000000001733e105d77419fe@google.com \
--to=syzbot+e89a1109c376e2c3c389@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).