WARNING in sysfs_remove_group

19 views
Skip to first unread message

syzbot

unread,
Sep 12, 2019, 2:21:08 PM9/12/19
to syzkaller...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: ee809c7e Linux 4.19.72
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=131f474e600000
kernel config: https://syzkaller.appspot.com/x/.config?x=ad6c5c98f4231da9
dashboard link: https://syzkaller.appspot.com/bug?extid=732ea7001c2737092f36
compiler: gcc (GCC) 9.0.0 20181231 (experimental)

Unfortunately, I don't have any reproducer for this crash yet.

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

sysfs group 'power' not found for kobject 'rfkill159'
WARNING: CPU: 1 PID: 10071 at fs/sysfs/group.c:253 sysfs_remove_group
fs/sysfs/group.c:253 [inline]
WARNING: CPU: 1 PID: 10071 at fs/sysfs/group.c:253
sysfs_remove_group+0x15b/0x1b0 fs/sysfs/group.c:244
Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 10071 Comm: syz-executor.5 Not tainted 4.19.72 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x172/0x1f0 lib/dump_stack.c:113
panic+0x263/0x507 kernel/panic.c:185
PM: Basic memory bitmaps created
__warn.cold+0x20/0x4a kernel/panic.c:540
report_bug+0x263/0x2b0 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x204/0x360 arch/x86/kernel/traps.c:296
do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:316
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1037
RIP: 0010:sysfs_remove_group fs/sysfs/group.c:253 [inline]
RIP: 0010:sysfs_remove_group+0x15b/0x1b0 fs/sysfs/group.c:244
Code: 48 89 d9 49 8b 55 00 48 b8 00 00 00 00 00 fc ff df 48 c1 e9 03 80 3c
01 00 75 41 48 8b 33 48 c7 c7 c0 4b 58 87 e8 13 a9 70 ff <0f> 0b eb 92 e8
4c b0 d3 ff e9 d0 fe ff ff 48 89 df e8 3f b0 d3 ff
RSP: 0018:ffff88805a0c7c30 EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffffffff879e2b00 RCX: 0000000000000000
RDX: 000000000000fa38 RSI: ffffffff8155cf16 RDI: ffffed100b418f78
RBP: ffff88805a0c7c58 R08: ffff88805e6b0080 R09: ffffed1015d25079
R10: ffffed1015d25078 R11: ffff8880ae9283c7 R12: 0000000000000000
R13: ffff88809a0f4970 R14: ffffffff879e30a0 R15: ffffffff84e3bc10
dpm_sysfs_remove+0x58/0x60 drivers/base/power/sysfs.c:734
device_del+0x132/0xb70 drivers/base/core.c:2082
rfkill_unregister+0xd1/0x2c0 net/rfkill/core.c:1093
hci_unregister_dev+0x287/0x820 net/bluetooth/hci_core.c:3288
vhci_release+0x76/0xf0 drivers/bluetooth/hci_vhci.c:354
__fput+0x2dd/0x8b0 fs/file_table.c:278
____fput+0x16/0x20 fs/file_table.c:309
task_work_run+0x145/0x1c0 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:193 [inline]
exit_to_usermode_loop+0x273/0x2c0 arch/x86/entry/common.c:167
prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline]
syscall_return_slowpath arch/x86/entry/common.c:271 [inline]
do_syscall_64+0x53d/0x620 arch/x86/entry/common.c:296
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x4598e9
Code: fd b7 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7
48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff
ff 0f 83 cb b7 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fd2b7a98c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000021
RAX: 0000000000000003 RBX: 0000000000000002 RCX: 00000000004598e9
RDX: 0000000000000000 RSI: 0000000000000003 RDI: 0000000000000005
RBP: 000000000075bf20 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fd2b7a996d4
R13: 00000000004bff35 R14: 00000000004d1ea8 R15: 00000000ffffffff
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
This bug 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 syzk...@googlegroups.com.

syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
Jan 10, 2020, 12:21:07 PM1/10/20
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages