[v5.15] Internal error in sys_move_pages

2 views
Skip to first unread message

syzbot

unread,
Aug 8, 2025, 10:34:29 AM8/8/25
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: c79648372d02 Linux 5.15.189
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=122c41a2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9e47345638b85bd0
dashboard link: https://syzkaller.appspot.com/bug?extid=653672cbf6e0a3755987
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7ab49562317a/disk-c7964837.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e847ec1e38d3/vmlinux-c7964837.xz
kernel image: https://storage.googleapis.com/syzbot-assets/263158c6371c/Image-c7964837.gz.xz

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

Internal error: Oops - BTI: 0000000036000001 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 8991 Comm: syz.3.2206 Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025
pstate: 42400405 (nZcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=jc)
pc : store_status mm/migrate.c:1660 [inline]
pc : do_pages_move mm/migrate.c:1862 [inline]
pc : kernel_move_pages mm/migrate.c:2051 [inline]
pc : __do_sys_move_pages mm/migrate.c:2065 [inline]
pc : __se_sys_move_pages mm/migrate.c:2060 [inline]
pc : __arm64_sys_move_pages+0xf54/0x19d4 mm/migrate.c:2060
lr : store_status mm/migrate.c:1660 [inline]
lr : do_pages_move mm/migrate.c:1862 [inline]
lr : kernel_move_pages mm/migrate.c:2051 [inline]
lr : __do_sys_move_pages mm/migrate.c:2065 [inline]
lr : __se_sys_move_pages mm/migrate.c:2060 [inline]
lr : __arm64_sys_move_pages+0xf30/0x19d4 mm/migrate.c:2060
sp : ffff80001fdc7b20
x29: ffff80001fdc7d20 x28: 0000000000000000 x27: ffff700003fb8f78
x26: 0000000000000000 x25: 0000000000000000 x24: 0000000000000000
x23: 0000000000000000 x22: ffff0000ee2a9700 x21: 00000000fffffff2
x20: 00000000fffffff2 x19: dfff800000000000 x18: 1fffe0003421cd96
x17: 1fffe0003421cd96 x16: ffff80000884b464 x15: ffff80001420eda0
x14: ffff0001a10e6cc0 x13: 1ffff0000282e06b x12: 0000000000ff0100
x11: 0000000000000000 x10: 0000ffffffffffff x9 : 0000000000000000
x8 : 0000000000000000 x7 : ffff800008750ed4 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000001
x2 : 0000000000000008 x1 : 0000000000000001 x0 : 0000000000000000
Call trace:
store_status mm/migrate.c:1660 [inline]
do_pages_move mm/migrate.c:1862 [inline]
kernel_move_pages mm/migrate.c:2051 [inline]
__do_sys_move_pages mm/migrate.c:2065 [inline]
__se_sys_move_pages mm/migrate.c:2060 [inline]
__arm64_sys_move_pages+0xf54/0x19d4 mm/migrate.c:2060
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: d503229f 2a1903f4 2a1903e0 b8000935 (2a1403e1)
---[ end trace d55a57883028e781 ]---
----------------
Code disassembly (best guess):
0: d503229f csdb
4: 2a1903f4 mov w20, w25
8: 2a1903e0 mov w0, w25
c: b8000935 sttr w21, [x9]
* 10: 2a1403e1 mov w1, w20 <-- trapping instruction


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

syzbot

unread,
Aug 10, 2025, 8:00:31 PM8/10/25
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: c79648372d02 Linux 5.15.189
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13a9c9a2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9e47345638b85bd0
dashboard link: https://syzkaller.appspot.com/bug?extid=653672cbf6e0a3755987
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=160771a2580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1567f2f0580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7ab49562317a/disk-c7964837.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e847ec1e38d3/vmlinux-c7964837.xz
kernel image: https://storage.googleapis.com/syzbot-assets/263158c6371c/Image-c7964837.gz.xz

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

Internal error: Oops - BTI: 0000000036000001 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 4185 Comm: syz.0.17 Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025
pstate: 42400405 (nZcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=jc)
pc : store_status mm/migrate.c:1660 [inline]
pc : do_pages_move mm/migrate.c:1862 [inline]
pc : kernel_move_pages mm/migrate.c:2051 [inline]
pc : __do_sys_move_pages mm/migrate.c:2065 [inline]
pc : __se_sys_move_pages mm/migrate.c:2060 [inline]
pc : __arm64_sys_move_pages+0xf54/0x19d4 mm/migrate.c:2060
lr : store_status mm/migrate.c:1660 [inline]
lr : do_pages_move mm/migrate.c:1862 [inline]
lr : kernel_move_pages mm/migrate.c:2051 [inline]
lr : __do_sys_move_pages mm/migrate.c:2065 [inline]
lr : __se_sys_move_pages mm/migrate.c:2060 [inline]
lr : __arm64_sys_move_pages+0xf30/0x19d4 mm/migrate.c:2060
sp : ffff80001fc57b20
x29: ffff80001fc57d20 x28: 0000000000000000 x27: ffff700003f8af78
x26: 0000000000000000 x25: 0000000000000000 x24: 0000000000000000
x23: 0000000000000000 x22: ffff0000cd426d40 x21: 00000000fffffff2
x20: 00000000fffffff2 x19: dfff800000000000 x18: 1fffe00034218b96
x17: ffff800016d04000 x16: ffff80000884b464 x15: ffff8000167e4500
x14: ffff0000cc752540 x13: 1ffff0000282e06b x12: 0000000000ff0100
x11: 0000000000000000 x10: 0000ffffffffffff x9 : 0000000000000000
x8 : 0000000000000000 x7 : ffff800008750ed4 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000001
x2 : 0000000000000008 x1 : 0000000000000001 x0 : 0000000000000000
Call trace:
store_status mm/migrate.c:1660 [inline]
do_pages_move mm/migrate.c:1862 [inline]
kernel_move_pages mm/migrate.c:2051 [inline]
__do_sys_move_pages mm/migrate.c:2065 [inline]
__se_sys_move_pages mm/migrate.c:2060 [inline]
__arm64_sys_move_pages+0xf54/0x19d4 mm/migrate.c:2060
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: d503229f 2a1903f4 2a1903e0 b8000935 (2a1403e1)
---[ end trace c0c5443719bc6fb4 ]---
----------------
Code disassembly (best guess):
0: d503229f csdb
4: 2a1903f4 mov w20, w25
8: 2a1903e0 mov w0, w25
c: b8000935 sttr w21, [x9]
* 10: 2a1403e1 mov w1, w20 <-- trapping instruction


---
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.
Reply all
Reply to author
Forward
0 new messages