All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+0b56d6ed0d0c0c9a79dc@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	 linux-mm@kvack.org, pasha.tatashin@soleen.com,
	peterx@redhat.com,  syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] WARNING in __page_table_check_ptes_set (2)
Date: Sun, 29 Sep 2024 04:39:24 -0700	[thread overview]
Message-ID: <66f93c6c.050a0220.6bad9.000c.GAE@google.com> (raw)
In-Reply-To: <000000000000b7b11a061ab49122@google.com>

syzbot has found a reproducer for the following issue on:

HEAD commit:    3efc57369a0c Merge tag 'for-linus' of git://git.kernel.org..
git tree:       upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=177e0127980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=a4fcb065287cdb84
dashboard link: https://syzkaller.appspot.com/bug?extid=0b56d6ed0d0c0c9a79dc
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17a7de80580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=16b67507980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b5a4faec7a99/disk-3efc5736.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/971adf9a5295/vmlinux-3efc5736.xz
kernel image: https://storage.googleapis.com/syzbot-assets/49516da34e16/bzImage-3efc5736.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 5229 at mm/page_table_check.c:209 page_table_check_pte_flags mm/page_table_check.c:209 [inline]
WARNING: CPU: 1 PID: 5229 at mm/page_table_check.c:209 __page_table_check_ptes_set+0x3bf/0x410 mm/page_table_check.c:220
Modules linked in:
CPU: 1 UID: 0 PID: 5229 Comm: syz-executor342 Not tainted 6.11.0-syzkaller-11993-g3efc57369a0c #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:page_table_check_pte_flags mm/page_table_check.c:209 [inline]
RIP: 0010:__page_table_check_ptes_set+0x3bf/0x410 mm/page_table_check.c:220
Code: 00 6c 49 39 c4 74 1d 48 b8 00 00 00 00 00 00 00 68 49 39 c4 75 1c e8 60 6b 89 ff eb 0c e8 59 6b 89 ff eb 05 e8 52 6b 89 ff 90 <0f> 0b 90 e9 98 fd ff ff e8 44 6b 89 ff e9 8e fd ff ff e8 da b9 b9
RSP: 0018:ffffc90002fe7000 EFLAGS: 00010293
RAX: ffffffff820b7ac0 RBX: d7ffe7fff1ed7c06 RCX: ffff88801cba3c00
RDX: 0000000000000000 RSI: ffffffff8ea73b20 RDI: 6800000000000000
RBP: ffffc90002fe70b0 R08: 0000000000000007 R09: ffffffff820b7a8e
R10: 0000000000000003 R11: ffff88801cba3c00 R12: 6800000000000000
R13: 0000000000000000 R14: 1ffff920005fce04 R15: 0000000000000001
FS:  00005555848eb380(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000005fdeb8 CR3: 0000000076e54000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 page_table_check_ptes_set include/linux/page_table_check.h:74 [inline]
 set_ptes include/linux/pgtable.h:267 [inline]
 try_to_migrate_one+0x2683/0x4240 mm/rmap.c:2300
 rmap_walk_anon+0x4cd/0x8a0 mm/rmap.c:2638
 try_to_migrate+0x3de/0x4b0
 migrate_folio_unmap mm/migrate.c:1326 [inline]
 migrate_pages_batch+0x113d/0x36d0 mm/migrate.c:1797
 migrate_pages_sync mm/migrate.c:1963 [inline]
 migrate_pages+0x2062/0x3560 mm/migrate.c:2072
 migrate_to_node mm/mempolicy.c:1095 [inline]
 do_migrate_pages+0x7ef/0xa30 mm/mempolicy.c:1194
 kernel_migrate_pages mm/mempolicy.c:1709 [inline]
 __do_sys_migrate_pages mm/mempolicy.c:1727 [inline]
 __se_sys_migrate_pages+0x6c4/0x740 mm/mempolicy.c:1723
 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:0x7fd4c1b123e9
Code: 48 83 c4 28 c3 e8 37 17 00 00 0f 1f 80 00 00 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffc3a5f83d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000100
RAX: ffffffffffffffda RBX: 00007ffc3a5f85b8 RCX: 00007fd4c1b123e9
RDX: 0000000020000040 RSI: 0000000000000003 RDI: 0000000000000000
RBP: 00007fd4c1b85610 R08: 00000000ffffc000 R09: 00000000ffffc000
R10: 0000000020000300 R11: 0000000000000246 R12: 0000000000000001
R13: 00007ffc3a5f85a8 R14: 0000000000000001 R15: 0000000000000001
 </TASK>


---
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.


  parent reply	other threads:[~2024-09-29 11:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12 17:18 [syzbot] [mm?] WARNING in __page_table_check_ptes_set (2) syzbot
2024-06-12 17:47 ` Andrew Morton
2024-06-12 18:17   ` Peter Xu
2024-06-12 19:30     ` Andrew Morton
2024-06-12 19:47       ` Peter Xu
2024-09-29 11:39 ` syzbot [this message]
2024-09-30 14:33 ` syzbot

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=66f93c6c.050a0220.6bad9.000c.GAE@google.com \
    --to=syzbot+0b56d6ed0d0c0c9a79dc@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pasha.tatashin@soleen.com \
    --cc=peterx@redhat.com \
    --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.