From: syzbot <syzbot+7da6c19dc528c2ebc612@syzkaller.appspotmail.com>
To: Jason@zx2c4.com, bsegall@google.com, davem@davemloft.net,
dietmar.eggemann@arm.com, dsahern@kernel.org,
edumazet@google.com, jason@zx2c4.com, juri.lelli@redhat.com,
kuba@kernel.org, linux-kernel@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, wireguard@lists.zx2c4.com
Subject: Re: [syzbot] [wireguard?] INFO: task hung in wg_destruct (2)
Date: Wed, 09 Oct 2024 00:44:03 -0700 [thread overview]
Message-ID: <67063443.050a0220.22840d.000f.GAE@google.com> (raw)
In-Reply-To: <66fa2708.050a0220.aab67.0025.GAE@google.com>
syzbot has bisected this issue to:
commit dfa0a574cbc47bfd5f8985f74c8ea003a37fa078
Author: Peter Zijlstra <peterz@infradead.org>
Date: Wed Jun 5 10:09:11 2024 +0000
sched/uclamg: Handle delayed dequeue
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13c2d7d0580000
start commit: e32cde8d2bd7 Merge tag 'sched_ext-for-6.12-rc1-fixes-1' of..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1022d7d0580000
console output: https://syzkaller.appspot.com/x/log.txt?x=17c2d7d0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=286b31f2cf1c36b5
dashboard link: https://syzkaller.appspot.com/bug?extid=7da6c19dc528c2ebc612
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=146ae580580000
Reported-by: syzbot+7da6c19dc528c2ebc612@syzkaller.appspotmail.com
Fixes: dfa0a574cbc4 ("sched/uclamg: Handle delayed dequeue")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-10-09 7:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 4:20 [syzbot] [wireguard?] INFO: task hung in wg_destruct (2) syzbot
2024-10-02 20:19 ` syzbot
2024-10-09 7:44 ` syzbot [this message]
2025-03-28 23:20 ` 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=67063443.050a0220.22840d.000f.GAE@google.com \
--to=syzbot+7da6c19dc528c2ebc612@syzkaller.appspotmail.com \
--cc=Jason@zx2c4.com \
--cc=bsegall@google.com \
--cc=davem@davemloft.net \
--cc=dietmar.eggemann@arm.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=juri.lelli@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@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 \
--cc=wireguard@lists.zx2c4.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;
as well as URLs for NNTP newsgroup(s).