Linux-Security-Module Archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+96127c74434e19e4609d@syzkaller.appspotmail.com>
To: brauner@kernel.org, davem@davemloft.net, edumazet@google.com,
	 gregkh@linuxfoundation.org, jack@suse.cz, jiri@nvidia.com,
	jmorris@namei.org,  kuba@kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	 linux-media@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	 linux-usb@vger.kernel.org, mchehab@kernel.org,
	netdev@vger.kernel.org,  oneukum@suse.com, pabeni@redhat.com,
	paul@paul-moore.com,  penguin-kernel@i-love.sakura.ne.jp,
	sean@mess.org, serge@hallyn.com,  stern@rowland.harvard.edu,
	syzkaller-bugs@googlegroups.com,  takedakn@nttdata.co.jp,
	tomoyo-dev-en-owner@lists.osdn.me,  tomoyo-dev-en@lists.osdn.me,
	viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [usb] INFO: rcu detected stall in newfstatat (3)
Date: Thu, 07 Mar 2024 01:22:01 -0800	[thread overview]
Message-ID: <000000000000a4bb3506130e9bc5@google.com> (raw)
In-Reply-To: <0000000000009752a005fdc2d114@google.com>

syzbot has bisected this issue to:

commit c2368b19807affd7621f7c4638cd2e17fec13021
Author: Jiri Pirko <jiri@nvidia.com>
Date:   Fri Jul 29 07:10:35 2022 +0000

    net: devlink: introduce "unregistering" mark and use it during devlinks iteration

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=14dc6736180000
start commit:   29cd507cbec2 Merge tag 'integrity-v6.8-fix' of git://git.k..
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=16dc6736180000
console output: https://syzkaller.appspot.com/x/log.txt?x=12dc6736180000
kernel config:  https://syzkaller.appspot.com/x/.config?x=70429b75d4a1a401
dashboard link: https://syzkaller.appspot.com/bug?extid=96127c74434e19e4609d
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11767d61180000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=15f691a6180000

Reported-by: syzbot+96127c74434e19e4609d@syzkaller.appspotmail.com
Fixes: c2368b19807a ("net: devlink: introduce "unregistering" mark and use it during devlinks iteration")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      parent reply	other threads:[~2024-03-07  9:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-10  9:07 [syzbot] [tomoyo?] [fs?] INFO: rcu detected stall in newfstatat (3) syzbot
2023-06-10 10:09 ` Tetsuo Handa
2024-03-07  9:22 ` 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=000000000000a4bb3506130e9bc5@google.com \
    --to=syzbot+96127c74434e19e4609d@syzkaller.appspotmail.com \
    --cc=brauner@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jack@suse.cz \
    --cc=jiri@nvidia.com \
    --cc=jmorris@namei.org \
    --cc=kuba@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oneukum@suse.com \
    --cc=pabeni@redhat.com \
    --cc=paul@paul-moore.com \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=sean@mess.org \
    --cc=serge@hallyn.com \
    --cc=stern@rowland.harvard.edu \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=takedakn@nttdata.co.jp \
    --cc=tomoyo-dev-en-owner@lists.osdn.me \
    --cc=tomoyo-dev-en@lists.osdn.me \
    --cc=viro@zeniv.linux.org.uk \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).