From: syzbot <syzbot+f87fd2bd13a4c9c5af8a@syzkaller.appspotmail.com>
To: bp@alien8.de, bristot@kernel.org, dave.hansen@linux.intel.com,
hpa@zytor.com, juri.lelli@redhat.com,
linux-kernel@vger.kernel.org, mingo@redhat.com,
peterz@infradead.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, vineeth@bitbyteword.org, x86@kernel.org
Subject: Re: [syzbot] [kernel?] INFO: rcu detected stall in rt_sigreturn
Date: Fri, 04 Oct 2024 13:32:02 -0700 [thread overview]
Message-ID: <670050c2.050a0220.49194.049e.GAE@google.com> (raw)
In-Reply-To: <0000000000009afb860616fa87cf@google.com>
syzbot suspects this issue was fixed by commit:
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=15678d80580000
start commit: 48cf398f15fc Merge tag 'char-misc-6.9-rc5' of git://git.ke..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=85dbe39cf8e4f599
dashboard link: https://syzkaller.appspot.com/bug?extid=f87fd2bd13a4c9c5af8a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=152c59fd180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=112d3227180000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: sched/rt: Remove default bandwidth control
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-10-04 20:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 7:05 [syzbot] [kernel?] INFO: rcu detected stall in rt_sigreturn syzbot
2024-10-04 20:32 ` 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=670050c2.050a0220.49194.049e.GAE@google.com \
--to=syzbot+f87fd2bd13a4c9c5af8a@syzkaller.appspotmail.com \
--cc=bp@alien8.de \
--cc=bristot@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=vineeth@bitbyteword.org \
--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