From: syzbot <[email protected]>
To: [email protected], [email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected]
Subject: [syzbot] WARNING: still has locks held in io_ring_submit_lock
Date: Sun, 15 May 2022 07:52:22 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 1e1b28b936ae Add linux-next specific files for 20220513
git tree: linux-next
console+strace: https://syzkaller.appspot.com/x/log.txt?x=10872211f00000
kernel config: https://syzkaller.appspot.com/x/.config?x=e4eb3c0c4b289571
dashboard link: https://syzkaller.appspot.com/bug?extid=987d7bb19195ae45208c
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1141bd21f00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=167ebdbef00000
The issue was bisected to:
commit 6da69b1da130e7d96766042750cd9f902e890eba
Author: Xiaomeng Tong <[email protected]>
Date: Mon Mar 28 03:24:31 2022 +0000
net: dsa: bcm_sf2_cfp: fix an incorrect NULL check on list iterator
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1652eb11f00000
final oops: https://syzkaller.appspot.com/x/report.txt?x=1552eb11f00000
console output: https://syzkaller.appspot.com/x/log.txt?x=1152eb11f00000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email protected]
Fixes: 6da69b1da130 ("net: dsa: bcm_sf2_cfp: fix an incorrect NULL check on list iterator")
====================================
WARNING: iou-wrk-3613/3623 still has locks held!
5.18.0-rc6-next-20220513-syzkaller #0 Not tainted
------------------------------------
1 lock held by iou-wrk-3613/3623:
#0: ffff888140bfe0a8 (&ctx->uring_lock){+.+.}-{3:3}, at: io_ring_submit_lock+0x75/0xc0 fs/io_uring.c:1494
stack backtrace:
CPU: 0 PID: 3623 Comm: iou-wrk-3613 Not tainted 5.18.0-rc6-next-20220513-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
try_to_freeze include/linux/freezer.h:66 [inline]
get_signal+0x1424/0x2600 kernel/signal.c:2647
io_wqe_worker+0x64b/0xdb0 fs/io-wq.c:663
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:297
</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 [email protected].
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
next reply other threads:[~2022-05-15 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-15 14:52 syzbot [this message]
2022-05-15 17:22 ` [syzbot] WARNING: still has locks held in io_ring_submit_lock Jens Axboe
2022-05-15 17:42 ` syzbot
2022-05-15 17:45 ` Jens Axboe
2022-05-15 18:06 ` 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] \
[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