From: syzbot <syzbot+872bccd9a68c6ba47718@syzkaller.appspotmail.com>
To: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
bristot@kernel.org, daniel@iogearbox.net, haoluo@google.com,
jmaloy@redhat.com, john.fastabend@gmail.com, jolsa@kernel.org,
juri.lelli@redhat.com, kpsingh@kernel.org,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
martin.lau@linux.dev, netdev@vger.kernel.org,
peterz@infradead.org, sdf@google.com, song@kernel.org,
syzkaller-bugs@googlegroups.com,
tipc-discussion@lists.sourceforge.net, vineeth@bitbyteword.org,
yonghong.song@linux.dev
Subject: Re: [syzbot] [tipc?] [nfs?] INFO: rcu detected stall in sys_unshare (9)
Date: Tue, 11 Mar 2025 08:56:05 -0700 [thread overview]
Message-ID: <67d05d15.050a0220.1939a6.001a.GAE@google.com> (raw)
In-Reply-To: <000000000000ba5cfd0609d55c40@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=176de7a8580000
start commit: 45ec2f5f6ed3 Merge tag 'mtd/fixes-for-6.8-rc7' of git://gi..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=fad652894fc96962
dashboard link: https://syzkaller.appspot.com/bug?extid=872bccd9a68c6ba47718
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12b890ca180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=154fbfe2180000
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:[~2025-03-11 15:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-11 0:17 [syzbot] [bpf?] INFO: rcu detected stall in sys_unshare (9) syzbot
2025-03-11 15:56 ` 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=67d05d15.050a0220.1939a6.001a.GAE@google.com \
--to=syzbot+872bccd9a68c6ba47718@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=bristot@kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=jmaloy@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=juri.lelli@redhat.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=vineeth@bitbyteword.org \
--cc=yonghong.song@linux.dev \
/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