From: syzbot <syzbot+882589c97d51a9de68eb@syzkaller.appspotmail.com>
To: Liam.Howlett@oracle.com, akpm@linux-foundation.org,
davem@davemloft.net, jannh@google.com, jhs@mojatatu.com,
jiri@resnulli.us, liam.howlett@oracle.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
lorenzo.stoakes@oracle.com, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com, vbabka@suse.cz,
vinicius.gomes@intel.com, xiyou.wangcong@gmail.com
Subject: Re: [syzbot] [mm?] INFO: rcu detected stall in mas_preallocate (2)
Date: Thu, 02 Jan 2025 16:46:02 -0800 [thread overview]
Message-ID: <6777334a.050a0220.3a8527.0058.GAE@google.com> (raw)
In-Reply-To: <6756b479.050a0220.a30f1.0196.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=117df818580000
start commit: feffde684ac2 Merge tag 'for-6.13-rc1-tag' of git://git.ker..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=137df818580000
console output: https://syzkaller.appspot.com/x/log.txt?x=157df818580000
kernel config: https://syzkaller.appspot.com/x/.config?x=50c7a61469ce77e7
dashboard link: https://syzkaller.appspot.com/bug?extid=882589c97d51a9de68eb
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10e8a8df980000
Reported-by: syzbot+882589c97d51a9de68eb@syzkaller.appspotmail.com
Fixes: 5a781ccbd19e ("tc: Add support for configuring the taprio scheduler")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-01-03 0:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 9:12 syzbot
2024-12-09 20:36 ` Liam R. Howlett
2024-12-10 2:48 ` syzbot
2024-12-10 18:04 ` Liam R. Howlett
2025-01-03 0:46 ` syzbot [this message]
2025-01-03 15:20 ` Liam R. Howlett
2025-01-04 0:00 ` Hillf Danton
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=6777334a.050a0220.3a8527.0058.GAE@google.com \
--to=syzbot+882589c97d51a9de68eb@syzkaller.appspotmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=jannh@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vbabka@suse.cz \
--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