Message-ID: <68552c8d.a00a0220.137b3.0040.GAE@google.com>
Date: Fri, 20 Jun 2025 02:40:29 -0700
From: syzbot <syzbot+d400c4dc8b94eed678bc@...kaller.appspotmail.com>
To: Liam.Howlett@...cle.com, akpm@...ux-foundation.org, jannh@...gle.com, 
	linux-kernel@...r.kernel.org, linux-mm@...ck.org, lorenzo.stoakes@...cle.com, 
	pfalcato@...e.de, syzkaller-bugs@...glegroups.com, vbabka@...e.cz
Subject: [syzbot] [mm?] WARNING: bad unlock balance in move_page_tables

Hello,

syzbot found the following issue on:

HEAD commit:    050f8ad7b58d Add linux-next specific files for 20250616
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1032490c580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=d2efc7740224b93a
dashboard link: https://syzkaller.appspot.com/bug?extid=d400c4dc8b94eed678bc
compiler:       Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/49faa18d2f53/disk-050f8ad7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7c6f9cd7fe5d/vmlinux-050f8ad7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/84a08d6403ee/bzImage-050f8ad7.xz

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

=====================================
WARNING: bad unlock balance detected!
6.16.0-rc2-next-20250616-syzkaller #0 Not tainted
-------------------------------------
syz.9.959/9941 is trying to release lock (&mapping->i_mmap_rwsem) at:
[<ffffffff821011d1>] i_mmap_unlock_write include/linux/fs.h:557 [inline]
[<ffffffff821011d1>] maybe_drop_rmap_locks mm/mremap.c:197 [inline]
[<ffffffff821011d1>] move_pgt_entry mm/mremap.c:686 [inline]
[<ffffffff821011d1>] move_page_tables+0xf51/0x2940 mm/mremap.c:1358
but there are no more locks to release!

other info that might help us debug this:
1 lock held by syz.9.959/9941:
 #0: ffff88807cafc260 (&mm->mmap_lock){++++}-{4:4}, at: mmap_write_lock_killable include/linux/mmap_lock.h:374 [inline]
 #0: ffff88807cafc260 (&mm->mmap_lock){++++}-{4:4}, at: do_mremap mm/mremap.c:2371 [inline]
 #0: ffff88807cafc260 (&mm->mmap_lock){++++}-{4:4}, at: __do_sys_mremap mm/mremap.c:2453 [inline]
 #0: ffff88807cafc260 (&mm->mmap_lock){++++}-{4:4}, at: __se_sys_mremap+0x3c0/0xc60 mm/mremap.c:2421

stack backtrace:
CPU: 1 UID: 0 PID: 9941 Comm: syz.9.959 Not tainted 6.16.0-rc2-next-20250616-syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
 print_unlock_imbalance_bug+0xdc/0xf0 kernel/locking/lockdep.c:5301
 __lock_release kernel/locking/lockdep.c:5540 [inline]
 lock_release+0x269/0x3e0 kernel/locking/lockdep.c:5892
 up_write+0x2d/0x420 kernel/locking/rwsem.c:1629
 i_mmap_unlock_write include/linux/fs.h:557 [inline]
 maybe_drop_rmap_locks mm/mremap.c:197 [inline]
 move_pgt_entry mm/mremap.c:686 [inline]
 move_page_tables+0xf51/0x2940 mm/mremap.c:1358
 copy_vma_and_data mm/mremap.c:1807 [inline]
 move_vma+0xd5e/0x2010 mm/mremap.c:1913
 mremap_to+0x7e7/0x8b0 mm/mremap.c:2106
 do_mremap mm/mremap.c:2396 [inline]
 __do_sys_mremap mm/mremap.c:2453 [inline]
 __se_sys_mremap+0x8f5/0xc60 mm/mremap.c:2421
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f4030f8e929
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:00007f4031dde038 EFLAGS: 00000246 ORIG_RAX: 0000000000000019
RAX: ffffffffffffffda RBX: 00007f40311b6240 RCX: 00007f4030f8e929
RDX: 0000000000200000 RSI: 0000000000600600 RDI: 0000200000000000
RBP: 00007f4031010b39 R08: 0000200000a00000 R09: 0000000000000000
R10: 0000000000000003 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007f40311b6240 R15: 00007ffc335a19c8
 </TASK>
------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff88807b05b2e0, owner = 0x0, curr 0xffff88802cc51e00, list empty
WARNING: kernel/locking/rwsem.c:1368 at __up_write kernel/locking/rwsem.c:1367 [inline], CPU#1: syz.9.959/9941
WARNING: kernel/locking/rwsem.c:1368 at up_write+0x3a2/0x420 kernel/locking/rwsem.c:1630, CPU#1: syz.9.959/9941
Modules linked in:
CPU: 1 UID: 0 PID: 9941 Comm: syz.9.959 Not tainted 6.16.0-rc2-next-20250616-syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:__up_write kernel/locking/rwsem.c:1367 [inline]
RIP: 0010:up_write+0x3a2/0x420 kernel/locking/rwsem.c:1630
Code: d0 48 c7 c7 60 ee 8a 8b 48 c7 c6 80 f0 8a 8b 48 8b 14 24 4c 89 f1 4d 89 e0 4c 8b 4c 24 08 41 52 e8 23 3b e6 ff 48 83 c4 08 90 <0f> 0b 90 90 e9 6d fd ff ff 48 c7 c1 34 81 a1 8f 80 e1 07 80 c1 03
RSP: 0018:ffffc90013b0f530 EFLAGS: 00010296
RAX: 3396a5242025d900 RBX: ffff88807b05b2e0 RCX: 0000000000080000
RDX: ffffc9000e491000 RSI: 0000000000031dc6 RDI: 0000000000031dc7
RBP: dffffc0000000000 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffffbfff1bfaa14 R12: 0000000000000000
R13: ffff88807b05b338 R14: ffff88807b05b2e0 R15: 1ffff1100f60b65d
FS:  00007f4031dde6c0(0000) GS:ffff888125d40000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f4031dddf98 CR3: 0000000057f30000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 i_mmap_unlock_write include/linux/fs.h:557 [inline]
 maybe_drop_rmap_locks mm/mremap.c:197 [inline]
 move_pgt_entry mm/mremap.c:686 [inline]
 move_page_tables+0xf51/0x2940 mm/mremap.c:1358
 copy_vma_and_data mm/mremap.c:1807 [inline]
 move_vma+0xd5e/0x2010 mm/mremap.c:1913
 mremap_to+0x7e7/0x8b0 mm/mremap.c:2106
 do_mremap mm/mremap.c:2396 [inline]
 __do_sys_mremap mm/mremap.c:2453 [inline]
 __se_sys_mremap+0x8f5/0xc60 mm/mremap.c:2421
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f4030f8e929
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:00007f4031dde038 EFLAGS: 00000246 ORIG_RAX: 0000000000000019
RAX: ffffffffffffffda RBX: 00007f40311b6240 RCX: 00007f4030f8e929
RDX: 0000000000200000 RSI: 0000000000600600 RDI: 0000200000000000
RBP: 00007f4031010b39 R08: 0000200000a00000 R09: 0000000000000000
R10: 0000000000000003 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007f40311b6240 R15: 00007ffc335a19c8
 </TASK>


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

Powered by blists - more mailing lists