mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* [syzbot] [mm?] WARNING in __page_table_check_ptes_set (3)
@ 2025-11-13 16:44 syzbot
  2026-05-27 17:36 ` syzbot
  0 siblings, 1 reply; 2+ messages in thread
From: syzbot @ 2025-11-13 16:44 UTC (permalink / raw)
  To: akpm, linux-kernel, linux-mm, pasha.tatashin, syzkaller-bugs

Hello,

syzbot found the following issue on:

HEAD commit:    439fc29dfd3b Merge tag 'drm-fixes-2025-11-09' of https://g..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15484412580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=e46b8a1c645465a9
dashboard link: https://syzkaller.appspot.com/bug?extid=18d274a59b87cf80e86d
compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
userspace arch: i386

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/87634fccbb6c/disk-439fc29d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4d7897eed027/vmlinux-439fc29d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/388814b7d484/bzImage-439fc29d.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+18d274a59b87cf80e86d@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 0 PID: 23212 at mm/page_table_check.c:191 page_table_check_pte_flags mm/page_table_check.c:191 [inline]
WARNING: CPU: 0 PID: 23212 at mm/page_table_check.c:191 __page_table_check_ptes_set+0x13e/0x2f0 mm/page_table_check.c:204
Modules linked in:
CPU: 0 UID: 0 PID: 23212 Comm: syz.0.4613 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:page_table_check_pte_flags mm/page_table_check.c:191 [inline]
RIP: 0010:__page_table_check_ptes_set+0x13e/0x2f0 mm/page_table_check.c:204
Code: b8 00 00 00 00 00 00 00 70 49 39 c7 74 21 48 b8 00 00 00 00 00 00 00 6c 49 39 c7 75 1d e8 3a 29 8f ff eb 10 e8 33 29 8f ff 90 <0f> 0b 90 eb 10 e8 28 29 8f ff 90 0f 0b 90 eb 05 e8 1d 29 8f ff 31
RSP: 0000:ffffc9000fd27990 EFLAGS: 00010287
RAX: ffffffff8230ea9d RBX: 00000000397c2c67 RCX: 0000000000080000
RDX: ffffc9000c8da000 RSI: 00000000000042d3 RDI: 00000000000042d4
RBP: 0000000000000001 R08: ffffea0000e5f087 R09: 1ffffd40001cbe10
R10: dffffc0000000000 R11: fffff940001cbe11 R12: 0000000000000001
R13: 00000000397c2c67 R14: ffff8880525baff0 R15: ffff88801a05ab00
FS:  0000000000000000(0000) GS:ffff88812613b000(0063) knlGS:00000000f54bdb40
CS:  0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: 0000000080ffe000 CR3: 0000000077a7e000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 page_table_check_ptes_set include/linux/page_table_check.h:76 [inline]
 set_ptes include/linux/pgtable.h:292 [inline]
 do_swap_page+0x5248/0x5b20 mm/memory.c:4970
 handle_pte_fault mm/memory.c:6180 [inline]
 __handle_mm_fault+0xe55/0x5400 mm/memory.c:6318
 handle_mm_fault+0x40a/0x8e0 mm/memory.c:6487
 do_user_addr_fault+0xa7c/0x1380 arch/x86/mm/fault.c:1336
 handle_page_fault arch/x86/mm/fault.c:1476 [inline]
 exc_page_fault+0x82/0x100 arch/x86/mm/fault.c:1532
 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:618
RIP: 0023:0xf70ef1f0
Code: 50 6a 00 e8 c2 10 14 00 8b 5c 24 2c 8b 4c 24 28 83 c4 20 8b 55 40 89 03 03 11 85 f6 74 18 31 c0 8d b4 26 00 00 00 00 8d 76 00 <89> 02 83 c0 01 83 c2 04 39 c6 75 f4 83 c4 1c 89 f8 5b 5e 5f 5d c3
RSP: 002b:00000000f54bd540 EFLAGS: 00010202
RAX: 0000000000000800 RBX: 00000000800000c0 RCX: 0000000080000000
RDX: 0000000080ffdfff RSI: 0000000000000efe RDI: 0000000000000008
RBP: 0000000080000140 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
 </TASK>
----------------
Code disassembly (best guess):
   0:	50                   	push   %rax
   1:	6a 00                	push   $0x0
   3:	e8 c2 10 14 00       	call   0x1410ca
   8:	8b 5c 24 2c          	mov    0x2c(%rsp),%ebx
   c:	8b 4c 24 28          	mov    0x28(%rsp),%ecx
  10:	83 c4 20             	add    $0x20,%esp
  13:	8b 55 40             	mov    0x40(%rbp),%edx
  16:	89 03                	mov    %eax,(%rbx)
  18:	03 11                	add    (%rcx),%edx
  1a:	85 f6                	test   %esi,%esi
  1c:	74 18                	je     0x36
  1e:	31 c0                	xor    %eax,%eax
  20:	8d b4 26 00 00 00 00 	lea    0x0(%rsi,%riz,1),%esi
  27:	8d 76 00             	lea    0x0(%rsi),%esi
* 2a:	89 02                	mov    %eax,(%rdx) <-- trapping instruction
  2c:	83 c0 01             	add    $0x1,%eax
  2f:	83 c2 04             	add    $0x4,%edx
  32:	39 c6                	cmp    %eax,%esi
  34:	75 f4                	jne    0x2a
  36:	83 c4 1c             	add    $0x1c,%esp
  39:	89 f8                	mov    %edi,%eax
  3b:	5b                   	pop    %rbx
  3c:	5e                   	pop    %rsi
  3d:	5f                   	pop    %rdi
  3e:	5d                   	pop    %rbp
  3f:	c3                   	ret


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [syzbot] [mm?] WARNING in __page_table_check_ptes_set (3)
  2025-11-13 16:44 [syzbot] [mm?] WARNING in __page_table_check_ptes_set (3) syzbot
@ 2026-05-27 17:36 ` syzbot
  0 siblings, 0 replies; 2+ messages in thread
From: syzbot @ 2026-05-27 17:36 UTC (permalink / raw)
  To: akpm, linux-kernel, linux-mm, pasha.tatashin, syzkaller-bugs

syzbot has found a reproducer for the following issue on:

HEAD commit:    4b4362973b6f Merge branch 'for-next/core' into for-kernelci
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=13c4d67e580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=f52fb4a6d220c448
dashboard link: https://syzkaller.appspot.com/bug?extid=18d274a59b87cf80e86d
compiler:       Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
userspace arch: arm64
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=15aab6ec580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1789c6ec580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/cdc9dd8cab69/disk-4b436297.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6bb74747f86d/vmlinux-4b436297.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a20d7153214f/Image-4b436297.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+18d274a59b87cf80e86d@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: mm/page_table_check.c:191 at page_table_check_pte_flags mm/page_table_check.c:191 [inline], CPU#0: syz.0.17/4918
WARNING: mm/page_table_check.c:191 at __page_table_check_ptes_set+0x24c/0x254 mm/page_table_check.c:207, CPU#0: syz.0.17/4918
Modules linked in:
CPU: 0 UID: 0 PID: 4918 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
pstate: 83400005 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
pc : page_table_check_pte_flags mm/page_table_check.c:191 [inline]
pc : __page_table_check_ptes_set+0x24c/0x254 mm/page_table_check.c:207
lr : page_table_check_pte_flags mm/page_table_check.c:191 [inline]
lr : __page_table_check_ptes_set+0x24c/0x254 mm/page_table_check.c:207
sp : ffff800099487420
x29: ffff800099487430 x28: 1ffff00013290efb x27: fffffdffc3a3b640
x26: ffff8000994877d8 x25: 04a8000128ed9f43 x24: 0408000000000000
x23: 0408000000000000 x22: ffff0000dd901f80 x21: ffff0000d0bc0ff0
x20: 0000000000000001 x19: 04a8000128ed9f43 x18: 00000000ffffffff
x17: ffff80008a186c80 x16: ffff80008a4a3638 x15: ffff0000c4c80b50
x14: ffff0000c4c80b30 x13: 0000000000000001 x12: 0000000000000000
x11: 0000000000000000 x10: 0000000000ff0100 x9 : 0000000000000001
x8 : 0000000000000000 x7 : ffff800080af57c0 x6 : 0000000000000000
x5 : 0000000000000030 x4 : 0000000000000001 x3 : ffff800080c10240
x2 : 0408000000000000 x1 : ffff0000c4c80000 x0 : 0000000000000000
Call trace:
 page_table_check_pte_flags mm/page_table_check.c:191 [inline] (P)
 __page_table_check_ptes_set+0x24c/0x254 mm/page_table_check.c:207 (P)
 page_table_check_ptes_set include/linux/page_table_check.h:83 [inline]
 __set_ptes_anysz+0x4dc/0x51c arch/arm64/include/asm/pgtable.h:681
 __set_ptes arch/arm64/include/asm/pgtable.h:714 [inline]
 set_ptes arch/arm64/include/asm/pgtable.h:1782 [inline]
 do_swap_page+0x2464/0x4348 mm/memory.c:5128
 handle_pte_fault mm/memory.c:6414 [inline]
 __handle_mm_fault mm/memory.c:6549 [inline]
 handle_mm_fault+0xd80/0x245c mm/memory.c:6718
 faultin_page mm/gup.c:1126 [inline]
 __get_user_pages+0x678/0x20f0 mm/gup.c:1428
 populate_vma_page_range+0x260/0x358 mm/gup.c:1860
 __mm_populate+0x200/0x324 mm/gup.c:1963
 do_mlock+0x52c/0x630 mm/mlock.c:659
 __do_sys_mlock mm/mlock.c:667 [inline]
 __se_sys_mlock mm/mlock.c:665 [inline]
 __arm64_sys_mlock+0x60/0x78 mm/mlock.c:665
 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
 invoke_syscall+0x98/0x244 arch/arm64/kernel/syscall.c:49
 el0_svc_common+0xe8/0x23c arch/arm64/kernel/syscall.c:121
 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:140
 el0_svc+0x64/0x260 arch/arm64/kernel/entry-common.c:740
 el0t_64_sync_handler+0x48/0x148 arch/arm64/kernel/entry-common.c:759
 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:594
irq event stamp: 960
hardirqs last  enabled at (959): [<ffff8000867c300c>] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:178 [inline]
hardirqs last  enabled at (959): [<ffff8000867c300c>] _raw_spin_unlock_irqrestore+0x38/0x98 kernel/locking/spinlock.c:198
hardirqs last disabled at (960): [<ffff80008679e6f8>] el1_brk64+0x20/0x54 arch/arm64/kernel/entry-common.c:429
softirqs last  enabled at (156): [<ffff800080137ce0>] local_bh_enable include/linux/bottom_half.h:33 [inline]
softirqs last  enabled at (156): [<ffff800080137ce0>] put_cpu_fpsimd_context arch/arm64/kernel/fpsimd.c:251 [inline]
softirqs last  enabled at (156): [<ffff800080137ce0>] do_sve_acc+0x22c/0x3b8 arch/arm64/kernel/fpsimd.c:1360
softirqs last disabled at (154): [<ffff800080137bc0>] local_bh_disable include/linux/bottom_half.h:20 [inline]
softirqs last disabled at (154): [<ffff800080137bc0>] get_cpu_fpsimd_context arch/arm64/kernel/fpsimd.c:234 [inline]
softirqs last disabled at (154): [<ffff800080137bc0>] do_sve_acc+0x10c/0x3b8 arch/arm64/kernel/fpsimd.c:1346
---[ end trace 0000000000000000 ]---


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2026-05-27 17:36 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-11-13 16:44 [syzbot] [mm?] WARNING in __page_table_check_ptes_set (3) syzbot
2026-05-27 17:36 ` syzbot

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®