From: syzbot <syzbot+1d4201dfe9f2386fdc0b@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] [block?] WARNING in process_fd_request
Date: Mon, 03 Apr 2023 07:54:54 -0700 [thread overview]
Message-ID: <000000000000ddf5f505f86fbd72@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: ffe78bbd5121 Merge tag 'xtensa-20230327' of https://github..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=146bbb71c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=d40b592130bb7abb
dashboard link: https://syzkaller.appspot.com/bug?extid=1d4201dfe9f2386fdc0b
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+1d4201dfe9f2386fdc0b@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 29261 at drivers/block/floppy.c:999 schedule_bh drivers/block/floppy.c:999 [inline]
WARNING: CPU: 0 PID: 29261 at drivers/block/floppy.c:999 process_fd_request+0x6b/0x70 drivers/block/floppy.c:2847
Modules linked in:
CPU: 0 PID: 29261 Comm: kworker/u8:17 Not tainted 6.3.0-rc4-syzkaller-00039-gffe78bbd5121 #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 drivers/block/floppy.c:999 [inline]
RIP: 0010:process_fd_request+0x6b/0x70 drivers/block/floppy.c:2847
Code: fc 5b bf 08 00 00 00 48 c7 c2 c0 78 45 8d 48 8b 35 6a a3 ec 0c 48 c7 05 7f 9e ec 0c b0 8c 1c 85 e9 ea 70 36 fc e8 05 6d 66 fc <0f> 0b eb ce 90 48 b8 00 00 00 00 00 fc ff df 41 55 49 89 fd 41 54
RSP: 0018:ffffc90002f7fcf0 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000000
RDX: ffff88801d64ba80 RSI: ffffffff851c6b4b RDI: 0000000000000001
RBP: 0000000000000282 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: ffffc90002f7fda8
R13: ffffffff8d457950 R14: ffff88800019f200 R15: ffff888012489000
FS: 0000000000000000(0000) GS:ffff88802ca00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000584eb404 CR3: 0000000023f74000 CR4: 0000000000150ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
floppy_shutdown+0x135/0x230 drivers/block/floppy.c:1889
process_one_work+0x991/0x15c0 kernel/workqueue.c:2390
worker_thread+0x669/0x1090 kernel/workqueue.c:2537
kthread+0x2e8/0x3a0 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
</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.
reply other threads:[~2023-04-03 14:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=000000000000ddf5f505f86fbd72@google.com \
--to=syzbot+1d4201dfe9f2386fdc0b@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