From: Hao Sun <[email protected]>
To: Jens Axboe <[email protected]>,
[email protected], Pavel Begunkov <[email protected]>,
Linux Kernel Mailing List <[email protected]>
Subject: WARNING in io_ring_exit_work
Date: Wed, 27 Oct 2021 09:26:49 +0800 [thread overview]
Message-ID: <CACkBjsY6iQ7JObmRiU+ztLayVoLi7X42=VFT38aC3Agj_KLkxw@mail.gmail.com> (raw)
Hello,
When using Healer to fuzz the latest Linux kernel, the following crash
was triggered.
HEAD commit: 519d81956ee2 Linux 5.15-rc6
git tree: upstream
console output:
https://drive.google.com/file/d/1d_-yYvTUew4bWhNCFt9Fs2zdpijQwnwd/view?usp=sharing
kernel config: https://drive.google.com/file/d/12PUnxIM1EPBgW4ZJmI7WJBRaY1lA83an/view?usp=sharing
Sorry, I don't have a reproducer for this crash, hope the symbolized
report can help.
If you fix this issue, please add the following tag to the commit:
Reported-by: Hao Sun <[email protected]>
------------[ cut here ]------------
WARNING: CPU: 2 PID: 16505 at fs/io_uring.c:9413
io_ring_exit_work+0x23e/0x1550 fs/io_uring.c:9413
Modules linked in:
CPU: 2 PID: 16505 Comm: kworker/u9:6 Not tainted 5.15.0-rc6 #4
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
1.13.0-1ubuntu1.1 04/01/2014
Workqueue: events_unbound io_ring_exit_work
RIP: 0010:io_ring_exit_work+0x23e/0x1550 fs/io_uring.c:9413
Code: 00 0f 85 67 0f 00 00 48 8b 05 ce b4 7c 09 31 ff 4c 8b 64 24 40
49 29 c4 4c 89 e6 e8 7c 23 92 ff 4d 85 e4 79 0d e8 f2 21 92 ff <0f> 0b
41 bd 70 17 00 00 e8 e5 21 92 ff 4c 89 ee 4c 89 ff e8 6a 42
RSP: 0018:ffffc90001fafbb0 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff88802fd22000 RCX: ffff8880144ab900
RDX: 0000000000000000 RSI: ffff8880144ab900 RDI: 0000000000000002
RBP: ffffc90001fafd28 R08: ffffffff81e43cce R09: 0000000000000000
R10: 0000000000000007 R11: ffffed1005fa44c0 R12: fffffffffffffffc
R13: 0000000000000005 R14: dffffc0000000000 R15: ffff88802fd22920
FS: 0000000000000000(0000) GS:ffff888063f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3bcc12b000 CR3: 000000000b68e000 CR4: 0000000000350ee0
Call Trace:
process_one_work+0x9df/0x16d0 kernel/workqueue.c:2297
worker_thread+0x90/0xed0 kernel/workqueue.c:2444
kthread+0x3e5/0x4d0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
Kernel panic - not syncing: panic_on_warn set ...
CPU: 2 PID: 16505 Comm: kworker/u9:6 Not tainted 5.15.0-rc6 #4
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
1.13.0-1ubuntu1.1 04/01/2014
Workqueue: events_unbound io_ring_exit_work
Call Trace:
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
panic+0x2b0/0x6dd kernel/panic.c:232
__warn.cold+0x20/0x2f kernel/panic.c:603
report_bug+0x273/0x300 lib/bug.c:199
handle_bug+0x3c/0x60 arch/x86/kernel/traps.c:239
exc_invalid_op+0x14/0x40 arch/x86/kernel/traps.c:259
asm_exc_invalid_op+0x12/0x20 arch/x86/include/asm/idtentry.h:566
RIP: 0010:io_ring_exit_work+0x23e/0x1550 fs/io_uring.c:9413
Code: 00 0f 85 67 0f 00 00 48 8b 05 ce b4 7c 09 31 ff 4c 8b 64 24 40
49 29 c4 4c 89 e6 e8 7c 23 92 ff 4d 85 e4 79 0d e8 f2 21 92 ff <0f> 0b
41 bd 70 17 00 00 e8 e5 21 92 ff 4c 89 ee 4c 89 ff e8 6a 42
RSP: 0018:ffffc90001fafbb0 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff88802fd22000 RCX: ffff8880144ab900
RDX: 0000000000000000 RSI: ffff8880144ab900 RDI: 0000000000000002
RBP: ffffc90001fafd28 R08: ffffffff81e43cce R09: 0000000000000000
R10: 0000000000000007 R11: ffffed1005fa44c0 R12: fffffffffffffffc
R13: 0000000000000005 R14: dffffc0000000000 R15: ffff88802fd22920
process_one_work+0x9df/0x16d0 kernel/workqueue.c:2297
worker_thread+0x90/0xed0 kernel/workqueue.c:2444
kthread+0x3e5/0x4d0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
Dumping ftrace buffer:
(ftrace buffer empty)
Kernel Offset: disabled
Rebooting in 1 seconds..
reply other threads:[~2021-10-27 1:27 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='CACkBjsY6iQ7JObmRiU+ztLayVoLi7X42=VFT38aC3Agj_KLkxw@mail.gmail.com' \
[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