All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+6f7c31cf5ae4944ad6f0@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 sys_mprotect (8)
Date: Thu, 16 Jan 2025 15:18:05 -0800	[thread overview]
Message-ID: <678993ad.050a0220.20d369.0047.GAE@google.com> (raw)
In-Reply-To: <6708ce33.050a0220.3e960.000e.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=124e5a18580000
start commit:   31eae6d99587 selftests: drv-net: test drivers sleeping in ..
git tree:       net-next
final oops:     https://syzkaller.appspot.com/x/report.txt?x=114e5a18580000
console output: https://syzkaller.appspot.com/x/log.txt?x=164e5a18580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=289acde585746aad
dashboard link: https://syzkaller.appspot.com/bug?extid=6f7c31cf5ae4944ad6f0
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11d7270f980000

Reported-by: syzbot+6f7c31cf5ae4944ad6f0@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-16 23:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-11  7:05 [syzbot] [mm?] INFO: rcu detected stall in sys_mprotect (8) syzbot
2025-01-09 13:23 ` syzbot
2025-01-16 23:18 ` syzbot [this message]
2026-11-06 12:35 ` syzbot

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=678993ad.050a0220.20d369.0047.GAE@google.com \
    --to=syzbot+6f7c31cf5ae4944ad6f0@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 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.