From: syzbot <syzbot+5c3c53e6db862466e7b6@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] possible deadlock in corrupted
Date: Mon, 06 Jun 2022 10:18:23 -0700 [thread overview]
Message-ID: <000000000000cbe0e605e0caa8e0@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: d1dc87763f40 assoc_array: Fix BUG_ON during garbage collect
git tree: upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=125e36ebf00000
kernel config: https://syzkaller.appspot.com/x/.config?x=e652a1bc921d8948
dashboard link: https://syzkaller.appspot.com/bug?extid=5c3c53e6db862466e7b6
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=141cc87df00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12613edbf00000
Bisection is inconclusive: the issue happens on the oldest tested release.
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1679bfcbf00000
final oops: https://syzkaller.appspot.com/x/report.txt?x=1579bfcbf00000
console output: https://syzkaller.appspot.com/x/log.txt?x=1179bfcbf00000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+5c3c53e6db862466e7b6@syzkaller.appspotmail.com
=====================================================
WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected
5.18.0-syzkaller-11972-gd1dc87763f40 #0 Not tainted
-----------------------------------------------------
syz-executor227/3609 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire:
ffff88801b5aa0c0 (&new->fa_lock){....}-{2:2}, at:
---
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.
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-06-06 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 17:18 syzbot [this message]
2022-07-23 11:12 ` [syzbot] possible deadlock in corrupted 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=000000000000cbe0e605e0caa8e0@google.com \
--to=syzbot+5c3c53e6db862466e7b6@syzkaller.appspotmail.com \
--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