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 568CB1AB6F1 for ; Fri, 24 Apr 2026 00:23:32 +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=1776990213; cv=none; b=oMRMt68XfPJlInPy8NPdkEw3N3VwJhTv8l8qablah62xLAPaGSbxfj6AbkdYuanCxDsszZRlIRIZcb/9m2Vki1BxTANtnysraQtAtiIVh7l9A50Ai9XDC/fRiyGTM47+p0tDxJSYEE0oKVRRYibJeOq7EaGCJOOj+gs5Mp/jJ08= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776990213; c=relaxed/simple; bh=vEwbdsspNXmncNrveE0dNCfmDazlvquLSyf0I9zQMkM=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=hDwkL+4WAvwA8ktAxE8kC6U2goW/be68ziyfdeR1pXBGAUB8boFq12e8aoAQfQXb+hSTHZ+b0CknmFYgqIJZGAFr3aFo2ZqC6zfXJxImpgQWwhxb/n0Xet8BAvdPZSHuwh8Yv3GR+kS5TRplBDZD6ZnQ9HLnfs9ZlMwSFu+T4/s= 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-7dbe0e914adso11178769a34.2 for ; Thu, 23 Apr 2026 17:23:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1776990211; x=1777595011; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=CWIVnShUDLsum8iUvvALRfGhmvCAHleL8NwdfLyFyxE=; b=MJJk/iQpHtFQemfXmrQyXiyWTJ0CmSQsnxp+3XAx+IGSjbzWiWwXzRbq8tBGGFdaEv xmPm0lEN4L17+YfP2ly52nDjpzpiLRPYcXSQJOy/hSkb6Z1x6E3KW6fiqcxjnmDraL8V WfB8krMn5fXh57sJ8ptZ7BZv6W62TXmvQZBejooJ0rBNi/otcH5hcybrtHKOPT+dIT5t keXMblNctg58PQmWPP9ZVRt+Zjby/4pt9TTCjtEnYhPdrtF+zmwAeWk34za/RVGLc86o 1bFUmfs2e4y8PEbowNW5W5ygTIL9r2FvbCBHFd6cJUEg8TAS5CyhhKPohJCp+k0AkyaG jZRA== X-Forwarded-Encrypted: i=1; AFNElJ+0Y7MRP7DeZiW5ei8v/T8sPu/o5WdvLs5yiRnJ8fiF6/MSMc/NRu3pyI94Tga73HX+J9zZaO1Pa2lZ5Qo=@vger.kernel.org X-Gm-Message-State: AOJu0YxBhGY6cL7Ti+YwsQBQyRVI40saweXuFvjsHTQaEgm5bVN3uNe1 hF/81ScO/RpuT+Z+v2pHpCHRJEytBazpbnViQKElNm7IsGcFxKUjRHJ4vry2I2YNYZHNjdw0WmX diNo2HIr0Tu9mxK110U3jyt43TflKJJn9SaXa0otSfI9tYxF0YucRfWm11Mc= 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:5104:b0:686:48b7:d81d with SMTP id 006d021491bc7-69462e39623mr11432744eaf.15.1776990211364; Thu, 23 Apr 2026 17:23:31 -0700 (PDT) Date: Thu, 23 Apr 2026 17:23:31 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <69eab803.a00a0220.17a17.004b.GAE@google.com> Subject: [syzbot] [mm?] BUG: sleeping function called from invalid context in shmem_undo_range From: syzbot To: akpm@linux-foundation.org, baolin.wang@linux.alibaba.com, hughd@google.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Hello, syzbot found the following issue on: HEAD commit: 2a4c0c11c019 Merge tag 's390-7.1-1' of git://git.kernel.or.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=109c12d2580000 kernel config: https://syzkaller.appspot.com/x/.config?x=24c8da4692f901cb dashboard link: https://syzkaller.appspot.com/bug?extid=9722a25de70a85ff48a1 compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44 userspace arch: i386 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-2a4c0c11.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/acfb852f3eb2/vmlinux-2a4c0c11.xz kernel image: https://storage.googleapis.com/syzbot-assets/d8166ea5d3da/bzImage-2a4c0c11.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+9722a25de70a85ff48a1@syzkaller.appspotmail.com BUG: sleeping function called from invalid context at mm/shmem.c:1150 in_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 5904, name: rm preempt_count: 0, expected: 0 RCU nest depth: 1, expected: 0 2 locks held by rm/5904: #0: ffff88802b0d0410 (sb_writers#5){.+.+}-{0:0}, at: filename_unlinkat+0x1ad/0x730 fs/namei.c:5545 #1: ffffffff8e7e5260 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire.constprop.0+0x7/0x30 include/linux/rcupdate.h:300 CPU: 1 UID: 0 PID: 5904 Comm: rm 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 shmem_undo_range+0x447/0x1570 mm/shmem.c:1150 shmem_truncate_range mm/shmem.c:1277 [inline] shmem_evict_inode+0x3f3/0xc40 mm/shmem.c:1407 evict+0x3c2/0xad0 fs/inode.c:841 iput_final fs/inode.c:1960 [inline] iput.part.0+0x605/0xf50 fs/inode.c:2009 iput+0x35/0x40 fs/inode.c:1975 filename_unlinkat+0x466/0x730 fs/namei.c:5572 __do_sys_unlink fs/namei.c:5603 [inline] __se_sys_unlink fs/namei.c:5600 [inline] __x64_sys_unlink+0x46/0x70 fs/namei.c:5600 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:0x7eff00dbe937 Code: 00 00 e9 a9 fd ff ff 66 2e 0f 1f 84 00 00 00 00 00 66 90 b8 5f 00 00 00 0f 05 c3 0f 1f 84 00 00 00 00 00 b8 57 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 8b 15 91 b4 0d 00 f7 d8 64 89 02 b8 RSP: 002b:00007ffef2c377b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000057 RAX: ffffffffffffffda RBX: 00007ffef2c37dd7 RCX: 00007eff00dbe937 RDX: 00007ffef2c377c8 RSI: 00007ffef2c37dd7 RDI: 00007ffef2c37dd7 RBP: 0000000000000008 R08: 00007ffef2c37dc0 R09: 0000000000000000 R10: 0000000000000100 R11: 0000000000000246 R12: 0000000000000000 R13: 00007eff00f4e9cc R14: 00007eff00faa000 R15: 000055fe0234bd98 ================================================ WARNING: lock held when returning to user space! syzkaller #0 Tainted: G W ------------------------------------------------ rm/5904 is leaving the kernel with locks still held! 1 lock held by rm/5904: #0: ffffffff8e7e5260 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire.constprop.0+0x7/0x30 include/linux/rcupdate.h:300 ------------[ cut here ]------------ Voluntary context switch within RCU read-side critical section! WARNING: kernel/rcu/tree_plugin.h:332 at rcu_note_context_switch+0x859/0x19c0 kernel/rcu/tree_plugin.h:332, CPU#1: rm/5904 Modules linked in: CPU: 1 UID: 0 PID: 5904 Comm: rm 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 RIP: 0010:rcu_note_context_switch+0x859/0x19c0 kernel/rcu/tree_plugin.h:332 Code: c1 ea 03 80 3c 02 00 0f 85 9b 0b 00 00 48 8b 53 28 b9 01 00 00 00 4c 89 ef e8 a3 cf fe ff e9 1d f9 ff ff 48 8d 3d b7 5e f1 0e <67> 48 0f b9 3a e9 99 f8 ff ff 48 b8 00 00 00 00 00 fc ff df 48 8d RSP: 0000:ffffc9000407fcf0 EFLAGS: 00010002 RAX: 0000000000000001 RBX: ffff88802b33c3c0 RCX: ffffffff81ee0fc1 RDX: 0000000000000000 RSI: ffffffff8c1c1000 RDI: ffffffff90dfe2a0 RBP: ffff8880267b2500 R08: 0000000000000000 R09: fffffbfff21b89ca R10: ffffffff90dc4e57 R11: ffffffff94142590 R12: 0000000000000000 R13: ffff8880267b29c4 R14: ffff88802b33b380 R15: ffffffff90dc81c4 FS: 00007eff00c00c80(0000) GS:ffff8880971e2000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007eff00da0850 CR3: 000000004cf7d000 CR4: 0000000000352ef0 Call Trace: __schedule+0x276/0x6820 kernel/sched/core.c:7043 __schedule_loop kernel/sched/core.c:7267 [inline] schedule+0xdd/0x390 kernel/sched/core.c:7282 __exit_to_user_mode_loop kernel/entry/common.c:54 [inline] exit_to_user_mode_loop kernel/entry/common.c:98 [inline] __exit_to_user_mode_prepare include/linux/irq-entry-common.h:207 [inline] irqentry_exit_to_user_mode_prepare include/linux/irq-entry-common.h:252 [inline] irqentry_exit_to_user_mode include/linux/irq-entry-common.h:323 [inline] irqentry_exit+0x359/0x790 kernel/entry/common.c:162 asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:697 RIP: 0033:0x7eff00dbe937 Code: 00 00 e9 a9 fd ff ff 66 2e 0f 1f 84 00 00 00 00 00 66 90 b8 5f 00 00 00 0f 05 c3 0f 1f 84 00 00 00 00 00 b8 57 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 8b 15 91 b4 0d 00 f7 d8 64 89 02 b8 RSP: 002b:00007ffef2c377b8 EFLAGS: 00000246 RAX: 0000000000000000 RBX: 00007ffef2c37dd7 RCX: 00007eff00dbe937 RDX: 00007ffef2c377c8 RSI: 00007ffef2c37dd7 RDI: 00007ffef2c37dd7 RBP: 0000000000000008 R08: 00007ffef2c37dc0 R09: 0000000000000000 R10: 0000000000000100 R11: 0000000000000246 R12: 0000000000000000 R13: 00007eff00f4e9cc R14: 00007eff00faa000 R15: 000055fe0234bd98 ---------------- Code disassembly (best guess): 0: c1 ea 03 shr $0x3,%edx 3: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1) 7: 0f 85 9b 0b 00 00 jne 0xba8 d: 48 8b 53 28 mov 0x28(%rbx),%rdx 11: b9 01 00 00 00 mov $0x1,%ecx 16: 4c 89 ef mov %r13,%rdi 19: e8 a3 cf fe ff call 0xfffecfc1 1e: e9 1d f9 ff ff jmp 0xfffff940 23: 48 8d 3d b7 5e f1 0e lea 0xef15eb7(%rip),%rdi # 0xef15ee1 * 2a: 67 48 0f b9 3a ud1 (%edx),%rdi <-- trapping instruction 2f: e9 99 f8 ff ff jmp 0xfffff8cd 34: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax 3b: fc ff df 3e: 48 rex.W 3f: 8d .byte 0x8d --- 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