From: syzbot <syzbot+38a0cbd267eff2d286ff@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, mmpgouride@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] [bcachefs?] WARNING in lock_list_lru_of_memcg
Date: Tue, 18 Feb 2025 12:25:02 -0800 [thread overview]
Message-ID: <67b4ec9e.050a0220.14d86d.000e.GAE@google.com> (raw)
In-Reply-To: <180B5E33-351D-4A3F-8948-02AF10DBA3D8@gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
general protection fault in call_rcu
Oops: general protection fault, probably for non-canonical address 0xef11a50f048e916c: 0000 [#1] PREEMPT SMP KASAN NOPTI
KASAN: maybe wild-memory-access in range [0x788d487824748b60-0x788d487824748b67]
CPU: 0 UID: 0 PID: 5968 Comm: modprobe Not tainted 6.14.0-rc3-syzkaller-g6537cfb395f3-dirty #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:lookup_object lib/debugobjects.c:423 [inline]
RIP: 0010:lookup_object_or_alloc lib/debugobjects.c:662 [inline]
RIP: 0010:debug_object_activate+0x1bd/0x580 lib/debugobjects.c:820
Code: 89 df e8 06 d5 2c fd 48 89 5c 24 30 4c 8b 3b 45 31 e4 eb 06 4d 8b 3f 41 ff c4 4d 85 ff 74 40 49 8d 5f 18 48 89 d8 48 c1 e8 03 <42> 80 3c 30 00 74 08 48 89 df e8 d4 d4 2c fd 48 8b 44 24 10 48 39
RSP: 0018:ffffc9000d09f2c0 EFLAGS: 00010006
RAX: 0f11a90f048e916c RBX: 788d487824748b60 RCX: 0000000000000001
RDX: dffffc0000000000 RSI: 0000000000000004 RDI: ffffc9000d09f1a0
RBP: ffffc9000d09f3d0 R08: 0000000000000003 R09: fffff52001a13e34
R10: dffffc0000000000 R11: fffff52001a13e34 R12: 0000000000000001
R13: 1ffff92001a13e60 R14: dffffc0000000000 R15: 788d487824748b48
FS: 0000000000000000(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055f7221a9008 CR3: 0000000053bc0000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
debug_rcu_head_queue kernel/rcu/rcu.h:224 [inline]
__call_rcu_common kernel/rcu/tree.c:3050 [inline]
call_rcu+0x97/0xac0 kernel/rcu/tree.c:3172
remove_vma mm/vma.c:419 [inline]
vms_complete_munmap_vmas+0x65b/0x8f0 mm/vma.c:1202
do_vmi_align_munmap+0x5ef/0x6f0 mm/vma.c:1445
do_vmi_munmap+0x24e/0x2d0 mm/vma.c:1493
__vm_munmap+0x372/0x510 mm/vma.c:2951
elf_map fs/binfmt_elf.c:389 [inline]
elf_load+0x2d6/0x700 fs/binfmt_elf.c:414
load_elf_interp+0x440/0xac0 fs/binfmt_elf.c:681
load_elf_binary+0x1a87/0x2820 fs/binfmt_elf.c:1241
search_binary_handler fs/exec.c:1775 [inline]
exec_binprm fs/exec.c:1807 [inline]
bprm_execve+0x979/0x1430 fs/exec.c:1859
kernel_execve+0x931/0xa50 fs/exec.c:2026
call_usermodehelper_exec_async+0x237/0x380 kernel/umh.c:109
ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:148
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:lookup_object lib/debugobjects.c:423 [inline]
RIP: 0010:lookup_object_or_alloc lib/debugobjects.c:662 [inline]
RIP: 0010:debug_object_activate+0x1bd/0x580 lib/debugobjects.c:820
Code: 89 df e8 06 d5 2c fd 48 89 5c 24 30 4c 8b 3b 45 31 e4 eb 06 4d 8b 3f 41 ff c4 4d 85 ff 74 40 49 8d 5f 18 48 89 d8 48 c1 e8 03 <42> 80 3c 30 00 74 08 48 89 df e8 d4 d4 2c fd 48 8b 44 24 10 48 39
RSP: 0018:ffffc9000d09f2c0 EFLAGS: 00010006
RAX: 0f11a90f048e916c RBX: 788d487824748b60 RCX: 0000000000000001
RDX: dffffc0000000000 RSI: 0000000000000004 RDI: ffffc9000d09f1a0
RBP: ffffc9000d09f3d0 R08: 0000000000000003 R09: fffff52001a13e34
R10: dffffc0000000000 R11: fffff52001a13e34 R12: 0000000000000001
R13: 1ffff92001a13e60 R14: dffffc0000000000 R15: 788d487824748b48
FS: 0000000000000000(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055f7221a9008 CR3: 0000000053bc0000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 89 df mov %ebx,%edi
2: e8 06 d5 2c fd call 0xfd2cd50d
7: 48 89 5c 24 30 mov %rbx,0x30(%rsp)
c: 4c 8b 3b mov (%rbx),%r15
f: 45 31 e4 xor %r12d,%r12d
12: eb 06 jmp 0x1a
14: 4d 8b 3f mov (%r15),%r15
17: 41 ff c4 inc %r12d
1a: 4d 85 ff test %r15,%r15
1d: 74 40 je 0x5f
1f: 49 8d 5f 18 lea 0x18(%r15),%rbx
23: 48 89 d8 mov %rbx,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 80 3c 30 00 cmpb $0x0,(%rax,%r14,1) <-- trapping instruction
2f: 74 08 je 0x39
31: 48 89 df mov %rbx,%rdi
34: e8 d4 d4 2c fd call 0xfd2cd50d
39: 48 8b 44 24 10 mov 0x10(%rsp),%rax
3e: 48 rex.W
3f: 39 .byte 0x39
Tested on:
commit: 6537cfb3 Merge tag 'sound-6.14-rc4' of git://git.kerne..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13732498580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b7bde34acd8f53b1
dashboard link: https://syzkaller.appspot.com/bug?extid=38a0cbd267eff2d286ff
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=10f8e5b0580000
next parent reply other threads:[~2025-02-18 20:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <180B5E33-351D-4A3F-8948-02AF10DBA3D8@gmail.com>
2025-02-18 20:25 ` syzbot [this message]
[not found] <984ABB17-1380-4581-B8AD-5E233B167856@gmail.com>
2025-02-19 16:37 ` [syzbot] [mm?] [bcachefs?] WARNING in lock_list_lru_of_memcg syzbot
[not found] <B2F37A7F-BE18-495F-9350-6D7D47198FFD@gmail.com>
2025-02-18 17:38 ` syzbot
[not found] <7ADD7E39-E7DC-4A40-8236-CD5C90112C96@gmail.com>
2025-02-18 17:12 ` syzbot
2024-12-14 3:56 [syzbot] [mm?] " syzbot
2025-02-14 18:11 ` [syzbot] [mm?] [bcachefs?] " syzbot
2025-02-14 23:23 ` Andrew Morton
2025-02-16 16:13 ` Kairui Song
2025-02-17 17:12 ` Kairui Song
2025-02-17 18:09 ` Alan Huang
2025-02-18 11:40 ` Kairui Song
2025-02-18 12:16 ` Alan Huang
2025-02-18 17:47 ` Kairui Song
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=67b4ec9e.050a0220.14d86d.000e.GAE@google.com \
--to=syzbot+38a0cbd267eff2d286ff@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmpgouride@gmail.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.