From: syzbot <syzbot+e4aa91d7f20c34417d4e@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, davem@davemloft.net,
dvyukov@google.com, edumazet@google.com, elver@google.com,
glider@google.com, horms@kernel.org, jannh@google.com,
jhs@mojatatu.com, jiri@resnulli.us, junjie.cao@intel.com,
kasan-dev@googlegroups.com, kuba@kernel.org,
liam.howlett@oracle.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, lorenzo.stoakes@oracle.com,
netdev@vger.kernel.org, pabeni@redhat.com, pfalcato@suse.de,
syzkaller-bugs@googlegroups.com, vbabka@suse.cz,
vinicius.gomes@intel.com
Subject: Re: [syzbot] [mm?] INFO: rcu detected stall in __mmap_complete
Date: Mon, 31 Aug 2026 04:43:03 -0700 [thread overview]
Message-ID: <6a9568c7.a8e469d2.cbf3.5619.GAE@google.com> (raw)
In-Reply-To: <20260831084159.410474-1-junjie.cao@intel.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+e4aa91d7f20c34417d4e@syzkaller.appspotmail.com
Tested-by: syzbot+e4aa91d7f20c34417d4e@syzkaller.appspotmail.com
Tested on:
commit: 1bb784eb Merge branch 'net-phy-fix-cleanup-after-probe..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git
console output: https://syzkaller.appspot.com/x/log.txt?x=17e3be25580000
kernel config: https://syzkaller.appspot.com/x/.config?x=5e4e3a0e188a497e
dashboard link: https://syzkaller.appspot.com/bug?extid=e4aa91d7f20c34417d4e
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=171ebe25580000
Note: testing is done by a robot and is best-effort only.
prev parent reply other threads:[~2026-08-31 11:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-04 22:55 [syzbot] [mm?] INFO: rcu detected stall in __mmap_complete syzbot
2026-08-29 20:56 ` syzbot
2026-08-29 21:58 ` Andrew Morton
2026-08-29 23:44 ` syzbot
2026-08-31 8:41 ` Junjie Cao
2026-08-31 11:43 ` 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=6a9568c7.a8e469d2.cbf3.5619.GAE@google.com \
--to=syzbot+e4aa91d7f20c34417d4e@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=horms@kernel.org \
--cc=jannh@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=junjie.cao@intel.com \
--cc=kasan-dev@googlegroups.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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pfalcato@suse.de \
--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