From: syzbot <syzbot+e24a2e34fad0efbac047@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, david@kernel.org,
harry.yoo@oracle.com, jannh@google.com, liam.howlett@oracle.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
ljs@kernel.org, peterx@redhat.com, riel@surriel.com,
rppt@kernel.org, syzkaller-bugs@googlegroups.com,
vbabka@kernel.org
Subject: Re: [syzbot] [mm?] WARNING in folio_add_new_anon_rmap
Date: Sun, 15 Mar 2026 23:58:05 -0700 [thread overview]
Message-ID: <69b7a9fd.a00a0220.3b25d1.0023.GAE@google.com> (raw)
In-Reply-To: <abehBY7QakYF9bK4@hyeyoo>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+e24a2e34fad0efbac047@syzkaller.appspotmail.com
Tested-by: syzbot+e24a2e34fad0efbac047@syzkaller.appspotmail.com
Tested on:
commit: b84a0ebe Add linux-next specific files for 20260313
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=11f43406580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d079c776411aaf59
dashboard link: https://syzkaller.appspot.com/bug?extid=e24a2e34fad0efbac047
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=16cfdd52580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2026-03-16 6:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-15 19:09 [syzbot] [mm?] WARNING in folio_add_new_anon_rmap syzbot
2026-03-16 6:19 ` Harry Yoo
2026-03-16 6:58 ` syzbot [this message]
2026-03-16 11:01 ` Mike Rapoport
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=69b7a9fd.a00a0220.3b25d1.0023.GAE@google.com \
--to=syzbot+e24a2e34fad0efbac047@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=harry.yoo@oracle.com \
--cc=jannh@google.com \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=peterx@redhat.com \
--cc=riel@surriel.com \
--cc=rppt@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vbabka@kernel.org \
/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