From: syzbot <syzbot+e24a2e34fad0efbac047@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] WARNING in folio_add_new_anon_rmap
Date: Sun, 15 Mar 2026 23:00:01 -0700 [thread overview]
Message-ID: <69b79c61.050a0220.248e02.010d.GAE@google.com> (raw)
In-Reply-To: <20260316051111.546771-1-kartikey406@gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in folio_add_new_anon_rmap
------------[ cut here ]------------
address < vma->vm_start || address + (nr << 12) > vma->vm_end
WARNING: mm/rmap.c:1682 at folio_add_new_anon_rmap+0x5fe/0x14b0 mm/rmap.c:1681, CPU#1: syz.0.32/6592
Modules linked in:
CPU: 1 UID: 0 PID: 6592 Comm: syz.0.32 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
RIP: 0010:folio_add_new_anon_rmap+0x5fe/0x14b0 mm/rmap.c:1681
Code: 89 f5 4d 8b 36 4c 89 e7 4c 89 f6 e8 0c aa a9 ff 4d 39 f4 73 1a e8 a2 a7 a9 ff 4c 8b 74 24 10 49 bc 00 00 00 00 00 fc ff df 90 <0f> 0b 90 eb 5a 44 89 f8 c1 e0 0c 48 98 49 01 c4 49 83 c5 08 4c 89
RSP: 0018:ffffc90003b175a0 EFLAGS: 00010293
RAX: ffffffff821d01ee RBX: ffffea0001c23500 RCX: ffff88802ebfdb80
RDX: 0000000000000000 RSI: 00002000004ca000 RDI: 00002000004cb000
RBP: 0000000000000000 R08: ffffea0001c23507 R09: 1ffffd40003846a0
R10: dffffc0000000000 R11: fffff940003846a1 R12: dffffc0000000000
R13: ffff888029014a08 R14: ffffea0001c23508 R15: 0000000000000001
FS: 00007f18a29856c0(0000) GS:ffff888125536000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fff5a396d70 CR3: 000000007256a000 CR4: 00000000003526f0
Call Trace:
<TASK>
mfill_atomic_install_pte+0x578/0x870 mm/userfaultfd.c:390
__mfill_atomic_pte+0x3c4/0x5f0 mm/userfaultfd.c:533
mfill_atomic_pte_copy mm/userfaultfd.c:567 [inline]
mfill_atomic_pte mm/userfaultfd.c:875 [inline]
mfill_atomic mm/userfaultfd.c:933 [inline]
mfill_atomic_copy+0x4d4/0x1420 mm/userfaultfd.c:960
userfaultfd_copy fs/userfaultfd.c:1642 [inline]
userfaultfd_ioctl+0x2bbe/0x4c70 fs/userfaultfd.c:2059
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:597 [inline]
__se_sys_ioctl+0xfc/0x170 fs/ioctl.c:583
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f18a1b9c799
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f18a2985028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f18a1e15fa0 RCX: 00007f18a1b9c799
RDX: 0000200000000040 RSI: 00000000c028aa03 RDI: 0000000000000003
RBP: 00007f18a1c32c99 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f18a1e16038 R14: 00007f18a1e15fa0 R15: 00007ffca7001d38
</TASK>
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=15fc5602580000
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=139c5602580000
next parent reply other threads:[~2026-03-16 6:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260316051111.546771-1-kartikey406@gmail.com>
2026-03-16 6:00 ` syzbot [this message]
[not found] <20260316020210.543036-1-kartikey406@gmail.com>
2026-03-16 2:40 ` [syzbot] [mm?] WARNING in folio_add_new_anon_rmap syzbot
2026-03-15 19:09 syzbot
2026-03-16 6:19 ` Harry Yoo
2026-03-16 6:58 ` syzbot
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=69b79c61.050a0220.248e02.010d.GAE@google.com \
--to=syzbot+e24a2e34fad0efbac047@syzkaller.appspotmail.com \
--cc=kartikey406@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.