From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-ot1-f78.google.com (mail-ot1-f78.google.com [209.85.210.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 3D5BE3890E3 for ; Mon, 20 Apr 2026 21:36:22 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.210.78 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776720983; cv=none; b=jt9MFdQwjf9yEPwWx5oE76oDsEJ72ipDt1vaHCgfF1WBQHnm7KrpR55+CnK628o5NMO3MTLPP0IJzWBCom/IKxcyS/4FvxhzRLggBDVni5TDDK80+fPKAiswthAmsH5m/mtzR6qFR67qXx1AxwUkC7nTdUg2Eg9IO+TvCPKDxsY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776720983; c=relaxed/simple; bh=VLoYccwTLdVIkJHlE1OlBC/3dt7+kpmyFxlp84CWzBQ=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=BEuMK8S5e1QBG1O/QE4scvvrS++cMDSco5+SLum1VwTX0bBGCzXG0ZHNC39RmTEVEr1BGcevtAdVIzq1ZE8/QeY3dzNQ/YCCKyUa5Skbblwmd6+U3Pv1D740PrXWtzVQL4DMd6Lr+fLwbmnHYRnmbbaNyn6YM+4/tVy54eyfB6o= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.210.78 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-ot1-f78.google.com with SMTP id 46e09a7af769-7dbd4fe0e15so8162255a34.3 for ; Mon, 20 Apr 2026 14:36:22 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1776720981; x=1777325781; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=ptLfAn3MhmEj6CBoEOsP94Qs16PUR2cMjXJj5E5I4cY=; b=MBzboO64K3gt8SF15OLi+X68saJD7mjTALxS3fE/GonXuG/l8ZdYM5wbuP5ybW7zhZ tZLsvfVtH1cGHBDMk/u99XGSuxo/beSwqdBeub4Hi15YmcGKa6Ei99AUT7Uf4GnmTI7c 3z/qtuexgos5gDQEUBUbMCqx4fM9YmiQSa/Zz3rMjoNRbUeGSlpfeUqfUvhXHkCimQYd LpcsVlzj3kGk6kNj/jv0xxpnUHmFPhOv4owE6hcyn+ID+NFV3UI7QJmh1/TePG7iTbOT HrEp1TlfbFNi0Xp0BRV98ggWsyCBZ141nSb096rWEPlHcoME1b5FYCBB+gxbXeeUVq2q OBUw== X-Forwarded-Encrypted: i=1; AFNElJ+LBlO6kDxityoiqZ7Lrut5xxmP6rT6gMy6DnkqjLddgALiL7DlWKJgNV1JSAz9BNLdLUcYwxCqyxTm/vA=@vger.kernel.org X-Gm-Message-State: AOJu0YyOL+dn+7fucXMAagXAZS9byJXg8vGyJrvI59IM+/Uh52KqUF3D edzFBlJPHIptaxywII8zQZCtzKvqC2LKyJ0M5JinE1Ab4GymNUFMgbm82uDEcxES6AN6tznNskk WyapMvxRBSlm+GPO40Ah7heJUYmWmVEWoXAMVTE5aapGqsk6rmeMCxxFp7Tg= Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6820:162c:b0:689:ceb5:6f38 with SMTP id 006d021491bc7-69462de1bdfmr8077832eaf.5.1776720981320; Mon, 20 Apr 2026 14:36:21 -0700 (PDT) Date: Mon, 20 Apr 2026 14:36:21 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <69e69c55.050a0220.24bfd3.002a.GAE@google.com> Subject: [syzbot] [mm?] BUG: sleeping function called from invalid context in __zap_vma_range From: syzbot To: Liam.Howlett@oracle.com, akpm@linux-foundation.org, jannh@google.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, ljs@kernel.org, pfalcato@suse.de, syzkaller-bugs@googlegroups.com, vbabka@kernel.org Content-Type: text/plain; charset="UTF-8" Hello, syzbot found the following issue on: HEAD commit: c1f49dea2b8f Merge tag 'mm-hotfixes-stable-2026-04-19-00-1.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=142514ce580000 kernel config: https://syzkaller.appspot.com/x/.config?x=6a29a582d8ced859 dashboard link: https://syzkaller.appspot.com/bug?extid=4cc5bc01fb4a179c4ffa compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-c1f49dea.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/402c79548d6e/vmlinux-c1f49dea.xz kernel image: https://storage.googleapis.com/syzbot-assets/1bc39526d7f4/bzImage-c1f49dea.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+4cc5bc01fb4a179c4ffa@syzkaller.appspotmail.com BUG: sleeping function called from invalid context at mm/memory.c:2007 in_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 5913, name: cmp preempt_count: 0, expected: 0 RCU nest depth: 1, expected: 0 2 locks held by cmp/5913: #0: ffff88801b8cc078 (&mm->mmap_lock){++++}-{4:4}, at: mmap_read_lock include/linux/mmap_lock.h:592 [inline] #0: ffff88801b8cc078 (&mm->mmap_lock){++++}-{4:4}, at: exit_mmap+0x124/0xa10 mm/mmap.c:1284 #1: ffffffff8e7e5460 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:300 [inline] #1: ffffffff8e7e5460 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:838 [inline] #1: ffffffff8e7e5460 (rcu_read_lock){....}-{1:3}, at: __pte_offset_map+0x2f/0x310 mm/pgtable-generic.c:290 CPU: 3 UID: 0 PID: 5913 Comm: cmp Not tainted syzkaller #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x100/0x190 lib/dump_stack.c:120 __might_resched.cold+0x1ec/0x232 kernel/sched/core.c:9162 zap_pmd_range mm/memory.c:2007 [inline] zap_pud_range mm/memory.c:2032 [inline] zap_p4d_range mm/memory.c:2053 [inline] __zap_vma_range+0x184b/0x4bf0 mm/memory.c:2093 unmap_vmas+0x299/0x5f0 mm/memory.c:2162 exit_mmap+0x1ef/0xa10 mm/mmap.c:1300 __mmput+0x12a/0x410 kernel/fork.c:1178 mmput+0x67/0x80 kernel/fork.c:1201 exit_mm kernel/exit.c:581 [inline] do_exit+0x833/0x2a60 kernel/exit.c:963 do_group_exit+0xd5/0x2a0 kernel/exit.c:1117 __do_sys_exit_group kernel/exit.c:1128 [inline] __se_sys_exit_group kernel/exit.c:1126 [inline] __x64_sys_exit_group+0x3e/0x50 kernel/exit.c:1126 x64_sys_call+0x102c/0x1530 arch/x86/include/generated/asm/syscalls_64.h:232 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x10b/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fedcf5c96c5 Code: Unable to access opcode bytes at 0x7fedcf5c969b. RSP: 002b:00007ffd9f5f73c8 EFLAGS: 00000202 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 00007fedcf6cafe8 RCX: 00007fedcf5c96c5 RDX: 00000000000000e7 RSI: ffffffffffffff88 RDI: 0000000000000000 RBP: 0000000000000001 R08: 00007ffd9f5f7358 R09: 0000000000000000 R10: 00007ffd9f5f71f0 R11: 0000000000000202 R12: 0000000000000000 R13: 0000000000000000 R14: 00007fedcf6c9680 R15: 00007fedcf6cb000 ============================= [ BUG: Invalid wait context ] syzkaller #0 Tainted: G W ----------------------------- cmp/5913 is trying to lock: ffff88801b8cc078 (&mm->mmap_lock){++++}-{4:4}, at: mmap_write_lock include/linux/mmap_lock.h:536 [inline] ffff88801b8cc078 (&mm->mmap_lock){++++}-{4:4}, at: exit_mmap+0x22c/0xa10 mm/mmap.c:1308 other info that might help us debug this: context-{5:5} 1 lock held by cmp/5913: #0: ffffffff8e7e5460 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:300 [inline] #0: ffffffff8e7e5460 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:838 [inline] #0: ffffffff8e7e5460 (rcu_read_lock){....}-{1:3}, at: __pte_offset_map+0x2f/0x310 mm/pgtable-generic.c:290 stack backtrace: CPU: 3 UID: 0 PID: 5913 Comm: cmp Tainted: G W syzkaller #0 PREEMPT(full) Tainted: [W]=WARN Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x100/0x190 lib/dump_stack.c:120 print_lock_invalid_wait_context kernel/locking/lockdep.c:4830 [inline] check_wait_context kernel/locking/lockdep.c:4902 [inline] __lock_acquire+0xfa4/0x2630 kernel/locking/lockdep.c:5187 lock_acquire kernel/locking/lockdep.c:5868 [inline] lock_acquire+0x1b1/0x370 kernel/locking/lockdep.c:5825 down_write+0x8b/0x1f0 kernel/locking/rwsem.c:1625 mmap_write_lock include/linux/mmap_lock.h:536 [inline] exit_mmap+0x22c/0xa10 mm/mmap.c:1308 __mmput+0x12a/0x410 kernel/fork.c:1178 mmput+0x67/0x80 kernel/fork.c:1201 exit_mm kernel/exit.c:581 [inline] do_exit+0x833/0x2a60 kernel/exit.c:963 do_group_exit+0xd5/0x2a0 kernel/exit.c:1117 __do_sys_exit_group kernel/exit.c:1128 [inline] __se_sys_exit_group kernel/exit.c:1126 [inline] __x64_sys_exit_group+0x3e/0x50 kernel/exit.c:1126 x64_sys_call+0x102c/0x1530 arch/x86/include/generated/asm/syscalls_64.h:232 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x10b/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fedcf5c96c5 Code: Unable to access opcode bytes at 0x7fedcf5c969b. RSP: 002b:00007ffd9f5f73c8 EFLAGS: 00000202 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 00007fedcf6cafe8 RCX: 00007fedcf5c96c5 RDX: 00000000000000e7 RSI: ffffffffffffff88 RDI: 0000000000000000 RBP: 0000000000000001 R08: 00007ffd9f5f7358 R09: 0000000000000000 R10: 00007ffd9f5f71f0 R11: 0000000000000202 R12: 0000000000000000 R13: 0000000000000000 R14: 00007fedcf6c9680 R15: 00007fedcf6cb000 --- 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