From: syzbot <syzbot+de026b20f56e1598e760@syzkaller.appspotmail.com>
To: andrii@kernel.org, asmadeus@codewreck.org, ast@kernel.org,
bpf@vger.kernel.org, bristot@kernel.org, daniel@iogearbox.net,
eddyz87@gmail.com, ericvh@kernel.org, haoluo@google.com,
john.fastabend@gmail.com, jolsa@kernel.org,
juri.lelli@redhat.com, kpsingh@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
lucho@ionkov.net, martin.lau@linux.dev, peterz@infradead.org,
sdf@google.com, song@kernel.org,
syzkaller-bugs@googlegroups.com, v9fs@lists.linux.dev,
vineeth@bitbyteword.org, yonghong.song@linux.dev
Subject: Re: [syzbot] [fs] INFO: rcu detected stall in sys_mount (7)
Date: Thu, 24 Oct 2024 18:14:05 -0700 [thread overview]
Message-ID: <671af0dd.050a0220.2eb763.00ce.GAE@google.com> (raw)
In-Reply-To: <000000000000a519120616f973cb@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=126a5e40580000
start commit: 3b68086599f8 Merge tag 'sched_urgent_for_v6.9_rc5' of git:..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=f47e5e015c177e57
dashboard link: https://syzkaller.appspot.com/bug?extid=de026b20f56e1598e760
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1775971b180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1290b320980000
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-25 1:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 5:48 [syzbot] [v9fs?] INFO: rcu detected stall in sys_mount (7) syzbot
2024-04-26 14:40 ` Eric Van Hensbergen
2024-10-25 1:14 ` 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=671af0dd.050a0220.2eb763.00ce.GAE@google.com \
--to=syzbot+de026b20f56e1598e760@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--cc=asmadeus@codewreck.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=bristot@kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=ericvh@kernel.org \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=juri.lelli@redhat.com \
--cc=kpsingh@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=martin.lau@linux.dev \
--cc=peterz@infradead.org \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=v9fs@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.