All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+c0673e1f1f054fac28c2@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] WARNING in __folio_rmap_sanity_checks (2)
Date: Sat, 28 Dec 2024 04:20:02 -0800	[thread overview]
Message-ID: <676fecf2.050a0220.226966.00ad.GAE@google.com> (raw)
In-Reply-To: <20241228103627.577-1-hdanton@sina.com>

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in __folio_rmap_sanity_checks

 do_ftruncate+0x4a1/0x540 fs/open.c:192
 do_sys_ftruncate fs/open.c:207 [inline]
 __do_sys_ftruncate fs/open.c:212 [inline]
 __se_sys_ftruncate fs/open.c:210 [inline]
 __x64_sys_ftruncate+0x94/0xf0 fs/open.c:210
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
------------[ cut here ]------------
WARNING: CPU: 0 PID: 8512 at ./include/linux/rmap.h:222 __folio_rmap_sanity_checks+0x52a/0xb30 include/linux/rmap.h:222
Modules linked in:
CPU: 0 UID: 0 PID: 8512 Comm: syz.4.115 Not tainted 6.13.0-rc3-next-20241220-syzkaller-05236-g8155b4ef3466-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:__folio_rmap_sanity_checks+0x52a/0xb30 include/linux/rmap.h:222
Code: 49 ff cd e9 29 fd ff ff e8 e3 c3 ab ff 48 ff cd e9 6b fd ff ff e8 d6 c3 ab ff 4c 89 e7 48 c7 c6 60 aa 15 8c e8 87 9c f5 ff 90 <0f> 0b 90 e9 66 fd ff ff e8 b9 c3 ab ff 48 ff cd e9 a6 fd ff ff e8
RSP: 0018:ffffc9000d986fb8 EFLAGS: 00010246
RAX: 9579638a77c65000 RBX: 00000000000001f8 RCX: ffffc9000d986b03
RDX: 0000000000000005 RSI: ffffffff8c0aac20 RDI: ffffffff8c5ff180
RBP: ffffea00014d8200 R08: ffffffff901ab2f7 R09: 1ffffffff203565e
R10: dffffc0000000000 R11: fffffbfff203565f R12: ffffea00014d0000
R13: ffffea00014d8200 R14: dffffc0000000000 R15: ffffea00014d8200
FS:  00007f399ed686c0(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005555898e7808 CR3: 00000000776f0000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 __folio_add_rmap mm/rmap.c:1170 [inline]
 __folio_add_file_rmap mm/rmap.c:1489 [inline]
 folio_add_file_rmap_ptes+0x82/0x380 mm/rmap.c:1511
 set_pte_range+0x30c/0x750 mm/memory.c:5136
 filemap_map_folio_range mm/filemap.c:3639 [inline]
 filemap_map_pages+0xfbe/0x1900 mm/filemap.c:3748
 do_fault_around mm/memory.c:5351 [inline]
 do_read_fault mm/memory.c:5384 [inline]
 do_fault mm/memory.c:5527 [inline]
 do_pte_missing mm/memory.c:4048 [inline]
 handle_pte_fault+0x3888/0x5ee0 mm/memory.c:5890
 __handle_mm_fault mm/memory.c:6033 [inline]
 handle_mm_fault+0x11f5/0x1d50 mm/memory.c:6202
 faultin_page mm/gup.c:1196 [inline]
 __get_user_pages+0x1a92/0x4140 mm/gup.c:1491
 populate_vma_page_range+0x264/0x330 mm/gup.c:1929
 __mm_populate+0x27a/0x460 mm/gup.c:2032
 mm_populate include/linux/mm.h:3400 [inline]
 vm_mmap_pgoff+0x303/0x430 mm/util.c:585
 ksys_mmap_pgoff+0x4eb/0x720 mm/mmap.c:607
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f399df85d29
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f399ed68038 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
RAX: ffffffffffffffda RBX: 00007f399e175fa0 RCX: 00007f399df85d29
RDX: 0000000000000002 RSI: 0000000000b36000 RDI: 0000000020000000
RBP: 00007f399e001b08 R08: 0000000000000004 R09: 0000000000000000
R10: 0000000000028011 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f399e175fa0 R15: 00007fff8d381608
 </TASK>


Tested on:

commit:         8155b4ef Add linux-next specific files for 20241220
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=12d84818580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=9c90bb7161a56c88
dashboard link: https://syzkaller.appspot.com/bug?extid=c0673e1f1f054fac28c2
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=12c850b0580000


  reply	other threads:[~2024-12-28 12:20 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11  1:54 [syzbot] [mm?] WARNING in __folio_rmap_sanity_checks (2) syzbot
2024-12-11 10:06 ` David Hildenbrand
2024-12-28  4:56 ` syzbot
2024-12-28  7:54   ` Hillf Danton
2024-12-28  8:03     ` syzbot
2024-12-28 10:36   ` Hillf Danton
2024-12-28 12:20     ` syzbot [this message]
2024-12-29  0:00   ` Hillf Danton
2024-12-29  1:14     ` syzbot
2024-12-29  6:42   ` Hillf Danton
2024-12-29  7:13     ` syzbot
2024-12-30 10:40   ` Hillf Danton
2024-12-30 11:08     ` syzbot
2024-12-30 11:17   ` Hillf Danton
2024-12-30 11:49     ` syzbot
2024-12-30 12:02   ` Hillf Danton
2024-12-30 12:20     ` syzbot
2024-12-31  8:41   ` Hillf Danton
2024-12-31  9:09     ` syzbot
2025-01-10 16:35     ` David Hildenbrand
2025-01-11  1:00       ` Hillf Danton
2025-01-11 10:03         ` David Hildenbrand
2024-12-28 12:25 ` syzbot
2025-01-10 15:48   ` David Hildenbrand
2025-01-10 16:14     ` Matthew Wilcox
2025-01-10 16:19       ` David Hildenbrand
2025-01-10 16:27         ` Matthew Wilcox
2025-01-10 16:31           ` David Hildenbrand
2025-01-10 19:55             ` Liam R. Howlett
2025-01-10 21:24               ` Suren Baghdasaryan
2025-01-11  4:29                 ` Liam R. Howlett
2025-01-10 21:03   ` Liam R. Howlett
2025-01-11  6:15     ` syzbot
2025-01-11  9:25     ` David Hildenbrand
2025-01-11  9:54       ` syzbot
2025-01-13 15:39         ` David Hildenbrand
2025-01-13 15:45           ` Liam R. Howlett
2025-01-13 15:50             ` David Hildenbrand

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=676fecf2.050a0220.226966.00ad.GAE@google.com \
    --to=syzbot+c0673e1f1f054fac28c2@syzkaller.appspotmail.com \
    --cc=hdanton@sina.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.