Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+8785aaf121cfb2141e0d@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, bigeasy@linutronix.de,
	davem@davemloft.net,  david@kernel.org, edumazet@google.com,
	harry.yoo@oracle.com, horms@kernel.org,  jannh@google.com,
	jhs@mojatatu.com, jiri@resnulli.us, jpoimboe@kernel.org,
	 junjie.cao@intel.com, kuba@kernel.org, liam.howlett@oracle.com,
	 linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	lorenzo.stoakes@oracle.com,  pabeni@redhat.com,
	peterz@infradead.org, pfalcato@suse.de, riel@surriel.com,
	 syzkaller-bugs@googlegroups.com, vbabka@suse.cz,
	vinicius.gomes@intel.com
Subject: Re: [syzbot] [mm?] INFO: rcu detected stall in sys_munmap (2)
Date: Tue, 01 Sep 2026 00:55:03 -0700	[thread overview]
Message-ID: <6a9684d7.2d75a5c4.15ddf4.0003.GAE@google.com> (raw)
In-Reply-To: <20260901014242.417011-1-junjie.cao@intel.com>

Hello,

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

Reported-by: syzbot+8785aaf121cfb2141e0d@syzkaller.appspotmail.com
Tested-by: syzbot+8785aaf121cfb2141e0d@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=15b33b79580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=9cc692b98d9b4fdb
dashboard link: https://syzkaller.appspot.com/bug?extid=8785aaf121cfb2141e0d
compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
patch:          https://syzkaller.appspot.com/x/patch.diff?x=100b3379580000

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


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

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-22  4:15 [syzbot] [mm?] INFO: rcu detected stall in sys_munmap (2) syzbot
2025-08-22 12:08 ` Lorenzo Stoakes
2025-08-22 13:55   ` Harry Yoo
2025-08-28  0:29     ` Josh Poimboeuf
2025-08-28  1:57       ` Liam R. Howlett
2025-08-28  3:35         ` Liam R. Howlett
2025-08-28  2:05 ` Liam R. Howlett
2025-08-28  2:05   ` syzbot
2025-08-28  2:20 ` Liam R. Howlett
2025-08-28  3:08   ` syzbot
2025-12-19 19:37 ` syzbot
2026-08-31  8:41   ` Junjie Cao
2026-08-31 10:45     ` syzbot
2026-09-01  1:42   ` Junjie Cao
2026-09-01  7:55     ` 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=6a9684d7.2d75a5c4.15ddf4.0003.GAE@google.com \
    --to=syzbot+8785aaf121cfb2141e0d@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bigeasy@linutronix.de \
    --cc=davem@davemloft.net \
    --cc=david@kernel.org \
    --cc=edumazet@google.com \
    --cc=harry.yoo@oracle.com \
    --cc=horms@kernel.org \
    --cc=jannh@google.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=jpoimboe@kernel.org \
    --cc=junjie.cao@intel.com \
    --cc=kuba@kernel.org \
    --cc=liam.howlett@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=pabeni@redhat.com \
    --cc=peterz@infradead.org \
    --cc=pfalcato@suse.de \
    --cc=riel@surriel.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=vbabka@suse.cz \
    --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