From: syzbot <syzbot+334c1c7dfb084b11520e@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 floppy_queue_rq
Date: Fri, 27 May 2022 00:14:17 -0700 [thread overview]
Message-ID: <000000000000f5181405dff90d7f@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: babf0bb978e3 Merge tag 'xfs-5.19-for-linus' of git://git.k..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1257af23f00000
kernel config: https://syzkaller.appspot.com/x/.config?x=fb7a468cb4ea251
dashboard link: https://syzkaller.appspot.com/bug?extid=334c1c7dfb084b11520e
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: i386
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: syzbot+334c1c7dfb084b11520e@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 9 at drivers/block/floppy.c:999 schedule_bh drivers/block/floppy.c:999 [inline]
WARNING: CPU: 0 PID: 9 at drivers/block/floppy.c:999 process_fd_request drivers/block/floppy.c:2847 [inline]
WARNING: CPU: 0 PID: 9 at drivers/block/floppy.c:999 floppy_queue_rq+0x32b/0x390 drivers/block/floppy.c:2879
Modules linked in:
CPU: 0 PID: 9 Comm: kworker/0:1H Not tainted 5.18.0-syzkaller-07857-gbabf0bb978e3 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014
Workqueue: kblockd blk_mq_run_work_fn
RIP: 0010:schedule_bh drivers/block/floppy.c:999 [inline]
RIP: 0010:process_fd_request drivers/block/floppy.c:2847 [inline]
RIP: 0010:floppy_queue_rq+0x32b/0x390 drivers/block/floppy.c:2879
Code: ea 03 80 3c 02 00 75 67 48 8b 56 30 48 c7 c7 80 41 42 8a e8 cd f9 96 04 0f 0b 41 bc 0a 00 00 00 e9 36 ff ff ff e8 a5 b0 e1 fc <0f> 0b e9 ec fe ff ff 48 89 df e8 96 f6 2d fd e9 ee fc ff ff 48 89
RSP: 0018:ffffc900003af928 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000000
RDX: ffff888011408000 RSI: ffffffff849817cb RDI: 0000000000000003
RBP: ffffffff8c8e9820 R08: 0000000000000000 R09: ffffffff8c8e8b47
R10: ffffffff849816b5 R11: 00000000ffffff80 R12: ffff888019d7f048
R13: ffff888019d7f000 R14: ffffc900003afb68 R15: ffff888019d7f048
FS: 0000000000000000(0000) GS:ffff88802ca00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000030921000 CR3: 0000000057352000 CR4: 0000000000150ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
blk_mq_dispatch_rq_list+0x6ea/0x2340 block/blk-mq.c:1908
__blk_mq_do_dispatch_sched block/blk-mq-sched.c:173 [inline]
blk_mq_do_dispatch_sched+0x96a/0xc20 block/blk-mq-sched.c:187
__blk_mq_sched_dispatch_requests+0x26d/0x3d0 block/blk-mq-sched.c:313
blk_mq_sched_dispatch_requests+0x101/0x180 block/blk-mq-sched.c:339
__blk_mq_run_hw_queue+0xff/0x350 block/blk-mq.c:2025
blk_mq_run_work_fn+0x55/0x70 block/blk-mq.c:2363
process_one_work+0x996/0x1610 kernel/workqueue.c:2289
worker_thread+0x665/0x1080 kernel/workqueue.c:2436
kthread+0x2e9/0x3a0 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:302
</TASK>
---
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 syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
next reply other threads:[~2022-05-27 7:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 7:14 syzbot [this message]
2022-06-20 20:32 ` [syzbot] WARNING in floppy_queue_rq 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=000000000000f5181405dff90d7f@google.com \
--to=syzbot+334c1c7dfb084b11520e@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.