From: syzbot <syzbot+8715dd783e9b0bef43b1@syzkaller•appspotmail.com>
To: bigeasy@linutronix•de, boqun.feng@gmail•com, bp@alien8•de,
brauner@kernel•org, clrkwllms@kernel•org,
dave.hansen@linux•intel.com, davem@davemloft•net,
dsahern@kernel•org, edumazet@google•com, horms@kernel•org,
hpa@zytor•com, jack@suse•cz, kprateek.nayak@amd•com,
kuba@kernel•org, kuniyu@google•com,
linux-fsdevel@vger•kernel.org, linux-kernel@vger•kernel.org,
linux-rt-devel@lists•linux.dev, luto@kernel•org,
mingo@redhat•com, ncardwell@google•com, neil@brown•name,
netdev@vger•kernel.org, pabeni@redhat•com, peterz@infradead•org,
rostedt@goodmis•org, ryotkkr98@gmail•com,
syzkaller-bugs@googlegroups•com, tglx@linutronix•de,
viro@zeniv•linux.org.uk, x86@kernel•org
Subject: Re: [syzbot] [fs?] kernel BUG in qlist_free_all (2)
Date: Fri, 03 Oct 2025 18:04:03 -0700 [thread overview]
Message-ID: <68e07283.a00a0220.102ee.0118.GAE@google.com> (raw)
In-Reply-To: <68c6c3b1.050a0220.2ff435.0382.GAE@google.com>
syzbot has bisected this issue to:
commit 3253cb49cbad4772389d6ef55be75db1f97da910
Author: Sebastian Andrzej Siewior <bigeasy@linutronix•de>
Date: Thu Sep 4 14:25:25 2025 +0000
softirq: Allow to drop the softirq-BKL lock on PREEMPT_RT
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17566a7c580000
start commit: 7f7072574127 Merge tag 'kbuild-6.18-1' of git://git.kernel..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=14d66a7c580000
console output: https://syzkaller.appspot.com/x/log.txt?x=10d66a7c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b78ebc06b51acd7e
dashboard link: https://syzkaller.appspot.com/bug?extid=8715dd783e9b0bef43b1
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16ba76e2580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17741ee2580000
Reported-by: syzbot+8715dd783e9b0bef43b1@syzkaller•appspotmail.com
Fixes: 3253cb49cbad ("softirq: Allow to drop the softirq-BKL lock on PREEMPT_RT")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
parent reply other threads:[~2025-10-04 1:04 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <68c6c3b1.050a0220.2ff435.0382.GAE@google.com>]
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=68e07283.a00a0220.102ee.0118.GAE@google.com \
--to=syzbot+8715dd783e9b0bef43b1@syzkaller$(echo .)appspotmail.com \
--cc=bigeasy@linutronix$(echo .)de \
--cc=boqun.feng@gmail$(echo .)com \
--cc=bp@alien8$(echo .)de \
--cc=brauner@kernel$(echo .)org \
--cc=clrkwllms@kernel$(echo .)org \
--cc=dave.hansen@linux$(echo .)intel.com \
--cc=davem@davemloft$(echo .)net \
--cc=dsahern@kernel$(echo .)org \
--cc=edumazet@google$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=hpa@zytor$(echo .)com \
--cc=jack@suse$(echo .)cz \
--cc=kprateek.nayak@amd$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=kuniyu@google$(echo .)com \
--cc=linux-fsdevel@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-rt-devel@lists$(echo .)linux.dev \
--cc=luto@kernel$(echo .)org \
--cc=mingo@redhat$(echo .)com \
--cc=ncardwell@google$(echo .)com \
--cc=neil@brown$(echo .)name \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=peterz@infradead$(echo .)org \
--cc=rostedt@goodmis$(echo .)org \
--cc=ryotkkr98@gmail$(echo .)com \
--cc=syzkaller-bugs@googlegroups$(echo .)com \
--cc=tglx@linutronix$(echo .)de \
--cc=viro@zeniv$(echo .)linux.org.uk \
--cc=x86@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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