From: syzbot <syzbot+46c3d1706c2d2688baba@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, bigeasy@linutronix.de,
bsegall@google.com, dietmar.eggemann@arm.com,
edumazet@google.com, juri.lelli@redhat.com,
kerneljasonxing@gmail.com, kuba@kernel.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, luiz.dentz@gmail.com, marcel@holtmann.org,
mgorman@suse.de, mingo@kernel.org, mingo@redhat.com,
pabeni@redhat.com, peterz@infradead.org, rostedt@goodmis.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
vincent.guittot@linaro.org, vschneid@redhat.com
Subject: Re: [syzbot] [mm?] INFO: rcu detected stall in vhci_release
Date: Wed, 04 Jun 2025 06:49:02 -0700 [thread overview]
Message-ID: <68404ece.a00a0220.d4325.000d.GAE@google.com> (raw)
In-Reply-To: <66f7eee8.050a0220.4a974.0006.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit 6d71a9c6160479899ee744d2c6d6602a191deb1f
Author: Peter Zijlstra <peterz@infradead.org>
Date: Thu Jan 9 10:59:59 2025 +0000
sched/fair: Fix EEVDF entity placement bug causing scheduling lag
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15a9780c580000
start commit: abf2050f51fd Merge tag 'media/v6.12-1' of git://git.kernel..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=2a8c36c5e2b56016
dashboard link: https://syzkaller.appspot.com/bug?extid=46c3d1706c2d2688baba
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10564c80580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: sched/fair: Fix EEVDF entity placement bug causing scheduling lag
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-06-04 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-28 11:56 [syzbot] [mm?] [bluetooth?] " syzbot
2024-10-07 17:56 ` syzbot
2025-06-04 13:49 ` syzbot [this message]
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=68404ece.a00a0220.d4325.000d.GAE@google.com \
--to=syzbot+46c3d1706c2d2688baba@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=edumazet@google.com \
--cc=juri.lelli@redhat.com \
--cc=kerneljasonxing@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=pabeni@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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