From: syzbot <syzbot+ca14b36a46a8c541b509@syzkaller.appspotmail.com>
To: bristot@kernel.org, cgroups@vger.kernel.org, hannes@cmpxchg.org,
hdanton@sina.com, juri.lelli@redhat.com,
linux-kernel@vger.kernel.org, lizefan.x@bytedance.com,
mkoutny@suse.com, peterz@infradead.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
tj@kernel.org, vincent.guittot@linaro.org,
vineeth@bitbyteword.org
Subject: Re: [syzbot] [cgroups?] possible deadlock in task_rq_lock
Date: Sun, 18 Aug 2024 00:05:02 -0700 [thread overview]
Message-ID: <000000000000b91f33061fefcfbb@google.com> (raw)
In-Reply-To: <000000000000e540f3061fc68863@google.com>
syzbot has bisected this issue to:
commit 5f6bd380c7bdbe10f7b4e8ddcceed60ce0714c6d
Author: Peter Zijlstra <peterz@infradead.org>
Date: Mon May 27 12:06:55 2024 +0000
sched/rt: Remove default bandwidth control
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11a668dd980000
start commit: 367b5c3d53e5 Add linux-next specific files for 20240816
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=13a668dd980000
console output: https://syzkaller.appspot.com/x/log.txt?x=15a668dd980000
kernel config: https://syzkaller.appspot.com/x/.config?x=61ba6f3b22ee5467
dashboard link: https://syzkaller.appspot.com/bug?extid=ca14b36a46a8c541b509
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13d6dbf3980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=142413c5980000
Reported-by: syzbot+ca14b36a46a8c541b509@syzkaller.appspotmail.com
Fixes: 5f6bd380c7bd ("sched/rt: Remove default bandwidth control")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-08-18 7:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 5:50 [syzbot] [cgroups?] possible deadlock in task_rq_lock syzbot
2024-08-17 6:52 ` syzbot
2024-08-18 7:05 ` 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=000000000000b91f33061fefcfbb@google.com \
--to=syzbot+ca14b36a46a8c541b509@syzkaller.appspotmail.com \
--cc=bristot@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=hdanton@sina.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=mkoutny@suse.com \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vineeth@bitbyteword.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