All of lore.kernel.org
 help / color / mirror / Atom feed
* [syzbot] [kernfs?] linux-next test error: BUG: key ADDR has not been registered!
@ 2024-06-18  9:36 syzbot
  0 siblings, 0 replies; only message in thread
From: syzbot @ 2024-06-18  9:36 UTC (permalink / raw)
  To: gregkh, linux-kernel, linux-next, sfr, syzkaller-bugs, tj

Hello,

syzbot found the following issue on:

HEAD commit:    76db4c64526c Add linux-next specific files for 20240617
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15e7ed0e980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=40a62461e8f6102
dashboard link: https://syzkaller.appspot.com/bug?extid=b2c37bfe1276a38db24f
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c821f6b56371/disk-76db4c64.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/efb2d2cbe799/vmlinux-76db4c64.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7be14777af71/bzImage-76db4c64.xz

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

cgroup: Unknown subsys name 'net'
BUG: key ffff88801b2e00d8 has not been registered!
------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(1)
WARNING: CPU: 0 PID: 5091 at kernel/locking/lockdep.c:4945 lockdep_init_map_type+0x4e3/0x910 kernel/locking/lockdep.c:4945
Modules linked in:
CPU: 0 PID: 5091 Comm: syz-executor Not tainted 6.10.0-rc4-next-20240617-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
RIP: 0010:lockdep_init_map_type+0x4e3/0x910 kernel/locking/lockdep.c:4945
Code: 00 00 83 3d 0e ee 3f 0e 00 75 23 90 48 c7 c7 c0 bf ca 8b 48 c7 c6 60 c2 ca 8b e8 98 12 e6 ff 48 ba 00 00 00 00 00 fc ff df 90 <0f> 0b 90 90 90 e9 0d ff ff ff 48 c7 c7 00 c2 ca 8b 4c 89 fe e8 d4
RSP: 0018:ffffc9000392f560 EFLAGS: 00010246
RAX: fd5a9d02d6690300 RBX: ffff88802b44f2fa RCX: ffff888027300000
RDX: dffffc0000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc9000392f630 R08: ffffffff81552402 R09: fffffbfff1c39afc
R10: dffffc0000000000 R11: fffffbfff1c39afc R12: ffff88802b44f2d8
R13: 1ffff92000725eb0 R14: 0000000000000000 R15: ffff88801b2e00d8
FS:  000055557db2c480(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055f3fa310918 CR3: 000000001f034000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 lockdep_init_map_waits include/linux/lockdep.h:135 [inline]
 lockdep_init_map_wait include/linux/lockdep.h:142 [inline]
 lockdep_init_map include/linux/lockdep.h:148 [inline]
 __kernfs_create_file+0x112/0x2e0 fs/kernfs/file.c:1046
 cgroup_add_file kernel/cgroup/cgroup.c:4216 [inline]
 cgroup_addrm_files+0xab8/0xe50 kernel/cgroup/cgroup.c:4270
 css_populate_dir+0x120/0x3b0 kernel/cgroup/cgroup.c:1761
 cgroup_apply_control_enable+0x621/0xaf0 kernel/cgroup/cgroup.c:3240
 cgroup_apply_control+0x97/0x800 kernel/cgroup/cgroup.c:3314
 rebind_subsystems+0x10a0/0x1500 kernel/cgroup/cgroup.c:1882
 cgroup_setup_root+0x3d3/0xb30 kernel/cgroup/cgroup.c:2132
 cgroup1_root_to_use kernel/cgroup/cgroup-v1.c:1224 [inline]
 cgroup1_get_tree+0x582/0x8c0 kernel/cgroup/cgroup-v1.c:1244
 vfs_get_tree+0x90/0x2a0 fs/super.c:1789
 do_new_mount+0x2be/0xb40 fs/namespace.c:3379
 do_mount fs/namespace.c:3719 [inline]
 __do_sys_mount fs/namespace.c:3925 [inline]
 __se_sys_mount+0x2d6/0x3c0 fs/namespace.c:3902
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f7e4547e62a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 09 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffcd9331ab8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffcd9331c70 RCX: 00007f7e4547e62a
RDX: 00007f7e454e51a6 RSI: 00007f7e454daa7e RDI: 00007f7e454d99b9
RBP: 00007f7e454daa7e R08: 00007f7e454dac2a R09: 006f6972705f7465
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f7e454d99b9
R13: 00007f7e454e51a6 R14: 00007ffcd9331c88 R15: 00007ffcd9331ac0
 </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@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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2024-06-18  9:36 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-06-18  9:36 [syzbot] [kernfs?] linux-next test error: BUG: key ADDR has not been registered! syzbot

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.