Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+19d01f6082ec61dd45b2@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, davem@davemloft.net,
	edumazet@google.com,  gregkh@linuxfoundation.org,
	horms@kernel.org, jhs@mojatatu.com,  jiri@resnulli.us,
	junjie.cao@intel.com, kuba@kernel.org,
	 linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	pabeni@redhat.com,  syzkaller-bugs@googlegroups.com,
	tj@kernel.org, vinicius.gomes@intel.com
Subject: Re: [syzbot] [kernfs?] INFO: rcu detected stall in kernfs_fop_open (7)
Date: Tue, 01 Sep 2026 00:45:02 -0700	[thread overview]
Message-ID: <6a96827e.04428c52.29b18.0003.GAE@google.com> (raw)
In-Reply-To: <20260901014117.416981-1-junjie.cao@intel.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+19d01f6082ec61dd45b2@syzkaller.appspotmail.com
Tested-by: syzbot+19d01f6082ec61dd45b2@syzkaller.appspotmail.com

Tested on:

commit:         abdf623d Merge tag 'wq-for-7.3-rc1-fixes' of git://git..
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=12f51379580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=d7588e5a39260ad2
dashboard link: https://syzkaller.appspot.com/bug?extid=19d01f6082ec61dd45b2
compiler:       Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
patch:          https://syzkaller.appspot.com/x/patch.diff?x=14a46d9e580000

Note: testing is done by a robot and is best-effort only.


      reply	other threads:[~2026-09-01  7:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-28 23:27 [syzbot] [kernfs?] [mm?] INFO: rcu detected stall in kernfs_fop_open (7) syzbot
2026-08-31  8:40 ` Junjie Cao
2026-08-31  9:20   ` [syzbot] [kernfs?] " syzbot
2026-09-01  1:41 ` [syzbot] [kernfs?] [mm?] " Junjie Cao
2026-09-01  7:45   ` 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=6a96827e.04428c52.29b18.0003.GAE@google.com \
    --to=syzbot+19d01f6082ec61dd45b2@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=horms@kernel.org \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=junjie.cao@intel.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pabeni@redhat.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tj@kernel.org \
    --cc=vinicius.gomes@intel.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