From: syzbot <syzbot+c27cd2da6c2dc003b4a1@syzkaller.appspotmail.com>
To: bigeasy@linutronix.de, bp@alien8.de, bsegall@google.com,
dave.hansen@linux.intel.com, dietmar.eggemann@arm.com,
edumazet@google.com, hpa@zytor.com, juri.lelli@redhat.com,
kerneljasonxing@gmail.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, mgorman@suse.de, 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, x86@kernel.org
Subject: Re: [syzbot] [kernel?] INFO: task hung in worker_thread (5)
Date: Fri, 16 May 2025 06:12:03 -0700 [thread overview]
Message-ID: <682739a3.a00a0220.398d88.020b.GAE@google.com> (raw)
In-Reply-To: <66fa9da7.050a0220.6bad9.003c.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=100696f4580000
start commit: aa486552a110 Merge tag 'memblock-v6.12-rc1' of git://git.k..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=6c71bad3e6ab6955
dashboard link: https://syzkaller.appspot.com/bug?extid=c27cd2da6c2dc003b4a1
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12afcaa9980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10edb627980000
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-05-16 13:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 12:46 [syzbot] [kernel?] INFO: task hung in worker_thread (5) syzbot
2025-05-16 13:12 ` 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=682739a3.a00a0220.398d88.020b.GAE@google.com \
--to=syzbot+c27cd2da6c2dc003b4a1@syzkaller.appspotmail.com \
--cc=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=bsegall@google.com \
--cc=dave.hansen@linux.intel.com \
--cc=dietmar.eggemann@arm.com \
--cc=edumazet@google.com \
--cc=hpa@zytor.com \
--cc=juri.lelli@redhat.com \
--cc=kerneljasonxing@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--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 \
--cc=x86@kernel.org \
/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