linux-kernel - Re: [syzbot] [bcachefs?] WARNING in rhashtable_init

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <05DB907D-8EF0-4E16-A133-3E32A8F8FD1C@gmail.com>
Date: Mon, 26 May 2025 18:41:09 +0800
From: Alan Huang <mmpgouride@...il.com>
To: syzbot <syzbot+bcc38a9556d0324c2ec2@...kaller.appspotmail.com>
Cc: kent.overstreet@...ux.dev,
 linux-bcachefs@...r.kernel.org,
 linux-kernel@...r.kernel.org,
 syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [bcachefs?] WARNING in rhashtable_init_noprof

On May 26, 2025, at 16:50, syzbot <syzbot+bcc38a9556d0324c2ec2@...kaller.appspotmail.com> wrote:
> 
> Hello,
> 
> syzbot found the following issue on:
> 
> HEAD commit:    176e917e010c Add linux-next specific files for 20250523
> git tree:       linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=13d555f4580000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=e7902c752bef748
> dashboard link: https://syzkaller.appspot.com/bug?extid=bcc38a9556d0324c2ec2
> compiler:       Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=145948e8580000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=13d6a170580000
> 
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/5f7692c642fa/disk-176e917e.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/057a442d42d0/vmlinux-176e917e.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/8f8ebdb4dd96/bzImage-176e917e.xz
> mounted in repro: https://storage.googleapis.com/syzbot-assets/d3d310848021/mount_0.gz
> 
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+bcc38a9556d0324c2ec2@...kaller.appspotmail.com
> 
> ODEBUG: object ffffc9000469fb90 is on stack ffffc90004698000, but NOT annotated.
> ------------[ cut here ]------------
> WARNING: CPU: 1 PID: 5924 at lib/debugobjects.c:655 debug_object_is_on_stack lib/debugobjects.c:655 [inline]
> WARNING: CPU: 1 PID: 5924 at lib/debugobjects.c:655 lookup_object_or_alloc lib/debugobjects.c:688 [inline]
> WARNING: CPU: 1 PID: 5924 at lib/debugobjects.c:655 __debug_object_init+0x2c9/0x3c0 lib/debugobjects.c:743
> Modules linked in:
> CPU: 1 UID: 0 PID: 5924 Comm: bch-copygc/loop Not tainted 6.15.0-rc7-next-20250523-syzkaller #0 PREEMPT(full) 
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
> RIP: 0010:debug_object_is_on_stack lib/debugobjects.c:655 [inline]
> RIP: 0010:lookup_object_or_alloc lib/debugobjects.c:688 [inline]
> RIP: 0010:__debug_object_init+0x2c9/0x3c0 lib/debugobjects.c:743
> Code: cc cc cc 41 ff c7 44 89 3d a4 18 14 15 48 c7 c1 80 9b e2 8b 48 c7 c7 e0 9b e2 8b 84 c0 48 0f 45 f9 48 89 de e8 48 2b 61 fc 90 <0f> 0b 90 e9 c0 fe ff ff e8 3a 1c 00 00 8b 05 1c 9c c6 09 3b 05 1a
> RSP: 0018:ffffc9000469f6e0 EFLAGS: 00010046
> RAX: 0000000000000050 RBX: ffffc9000469fb90 RCX: 0aa01120dfd08500
> RDX: 0000000000000000 RSI: 0000000080000001 RDI: 0000000000000000
> RBP: ffff88802f5c9e20 R08: ffffc9000469f3c7 R09: 1ffff920008d3e78
> R10: dffffc0000000000 R11: fffff520008d3e79 R12: 0000000000000040
> R13: ffff8880771e5d20 R14: dffffc0000000000 R15: 0000000000000001
> FS:  0000000000000000(0000) GS:ffff888125d56000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007f1c5ee80000 CR3: 0000000077540000 CR4: 00000000003526f0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> Call Trace:
> <TASK>
> rhashtable_init_noprof+0x7c0/0xbb0 lib/rhashtable.c:1085
> bch2_copygc_thread+0x116/0xdc0 fs/bcachefs/movinggc.c:355
> kthread+0x711/0x8a0 kernel/kthread.c:464
> ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148
> ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
> </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 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.
> 
> 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
> 


#syz test: https://github.com/alanskind/bcachefs 9b38df1f0d770aef29fd6aea023b28b053e14ecf