From: syzbot <[email protected]>
To: [email protected], [email protected],
[email protected], [email protected],
[email protected]
Subject: [syzbot] WARNING in io_ring_exit_work
Date: Mon, 15 Mar 2021 12:08:40 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: b01d57bf Add linux-next specific files for 20210310
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10ae049ed00000
kernel config: https://syzkaller.appspot.com/x/.config?x=95af83fd326c2b5
dashboard link: https://syzkaller.appspot.com/bug?extid=00e15cda746c5bc70e24
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: [email protected]
------------[ cut here ]------------
WARNING: CPU: 0 PID: 225 at fs/io_uring.c:8456 io_ring_exit_work+0x130/0xcf0 fs/io_uring.c:8456
Modules linked in:
CPU: 0 PID: 225 Comm: kworker/u4:5 Not tainted 5.12.0-rc2-next-20210310-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events_unbound io_ring_exit_work
RIP: 0010:io_ring_exit_work+0x130/0xcf0 fs/io_uring.c:8456
Code: 7d 00 00 0f 85 bf 09 00 00 48 8b 05 3a 15 e5 09 4d 89 f5 31 ff 49 29 c5 4c 89 ee e8 6a 09 98 ff 4d 85 ed 79 a5 e8 40 01 98 ff <0f> 0b eb 9c e8 37 01 98 ff 31 f6 49 bf 00 00 00 00 00 fc ff df 4c
RSP: 0018:ffffc9000163fbc8 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff88801dd36930 RCX: 0000000000000000
RDX: ffff8880120d9c00 RSI: ffffffff81dbdc60 RDI: 0000000000000003
RBP: fffffbfff1781e30 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffff81dbdc56 R11: 0000000000000000 R12: ffff88801dd364e0
R13: fffffffffffffffe R14: 00000001000040a4 R15: ffff88801dd36000
FS: 0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fcf0ff32000 CR3: 00000000180fb000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
process_one_work+0x98d/0x1600 kernel/workqueue.c:2275
worker_thread+0x64c/0x1120 kernel/workqueue.c:2421
kthread+0x3b1/0x4a0 kernel/kthread.c:292
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294
---
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 [email protected].
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
next reply other threads:[~2021-03-15 19:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 19:08 syzbot [this message]
2021-08-06 7:02 ` [syzbot] WARNING in io_ring_exit_work syzbot
2021-08-06 9:20 ` Pavel Begunkov
2021-08-06 10:33 ` syzbot
2021-08-06 15:21 ` syzbot
2023-05-29 7:58 ` [syzbot] [io-uring?] " 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 \
[email protected] \
[email protected] \
[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