From: syzbot <syzbot+23e14ec82f3c8692eaa9@syzkaller.appspotmail.com>
To: anna-maria@linutronix.de, davem@davemloft.net,
frederic@kernel.org, gregkh@linuxfoundation.org,
jhs@mojatatu.com, jiri@resnulli.us,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-usb@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, tj@kernel.org, vinicius.gomes@intel.com,
xiyou.wangcong@gmail.com
Subject: Re: [syzbot] [fs?] [mm?] INFO: rcu detected stall in sys_readlink (5)
Date: Wed, 15 Jan 2025 00:39:02 -0800 [thread overview]
Message-ID: <67877426.050a0220.20d369.0009.GAE@google.com> (raw)
In-Reply-To: <6712465a.050a0220.1e4b4d.0012.GAE@google.com>
syzbot has bisected this issue to:
commit 5a781ccbd19e4664babcbe4b4ead7aa2b9283d22
Author: Vinicius Costa Gomes <vinicius.gomes@intel.com>
Date: Sat Sep 29 00:59:43 2018 +0000
tc: Add support for configuring the taprio scheduler
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=124487c4580000
start commit: 7dc8f809b87d Merge tag 'linux-can-next-for-6.14-20250110' ..
git tree: net-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=114487c4580000
console output: https://syzkaller.appspot.com/x/log.txt?x=164487c4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=28dc37e0ec0dfc41
dashboard link: https://syzkaller.appspot.com/bug?extid=23e14ec82f3c8692eaa9
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1634f218580000
Reported-by: syzbot+23e14ec82f3c8692eaa9@syzkaller.appspotmail.com
Fixes: 5a781ccbd19e ("tc: Add support for configuring the taprio scheduler")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
parent reply other threads:[~2025-01-15 8:39 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <6712465a.050a0220.1e4b4d.0012.GAE@google.com>]
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=67877426.050a0220.20d369.0009.GAE@google.com \
--to=syzbot+23e14ec82f3c8692eaa9@syzkaller.appspotmail.com \
--cc=anna-maria@linutronix.de \
--cc=davem@davemloft.net \
--cc=frederic@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=vinicius.gomes@intel.com \
--cc=xiyou.wangcong@gmail.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