From: syzbot <syzbot+aff8125319e0457b4a25@syzkaller.appspotmail.com>
To: bsegall@google.com, davem@davemloft.net,
dietmar.eggemann@arm.com, edumazet@google.com,
johannes@sipsolutions.net, juri.lelli@redhat.com,
kuba@kernel.org, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, mgorman@suse.de,
mingo@redhat.com, netdev@vger.kernel.org, pabeni@redhat.com,
peterz@infradead.org, rostedt@goodmis.org,
syzkaller-bugs@googlegroups.com, vincent.guittot@linaro.org,
vschneid@redhat.com
Subject: Re: [syzbot] [wireless?] INFO: task hung in regdb_fw_cb (2)
Date: Sat, 08 Mar 2025 01:46:01 -0800 [thread overview]
Message-ID: <67cc11d9.050a0220.24a339.0090.GAE@google.com> (raw)
In-Reply-To: <67012223.050a0220.49194.04be.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit 66951e4860d3c688bfa550ea4a19635b57e00eca
Author: Peter Zijlstra <peterz@infradead.org>
Date: Mon Jan 13 12:50:11 2025 +0000
sched/fair: Fix update_cfs_group() vs DELAY_DEQUEUE
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13d29878580000
start commit: e32cde8d2bd7 Merge tag 'sched_ext-for-6.12-rc1-fixes-1' of..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=1b5201b91035a876
dashboard link: https://syzkaller.appspot.com/bug?extid=aff8125319e0457b4a25
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1561539f980000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: sched/fair: Fix update_cfs_group() vs DELAY_DEQUEUE
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-03-08 9:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-05 11:25 [syzbot] [wireless?] INFO: task hung in regdb_fw_cb (2) syzbot
2025-03-08 9:46 ` 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=67cc11d9.050a0220.24a339.0090.GAE@google.com \
--to=syzbot+aff8125319e0457b4a25@syzkaller.appspotmail.com \
--cc=bsegall@google.com \
--cc=davem@davemloft.net \
--cc=dietmar.eggemann@arm.com \
--cc=edumazet@google.com \
--cc=johannes@sipsolutions.net \
--cc=juri.lelli@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=syzkaller-bugs@googlegroups.com \
--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