lkml.org 
[lkml]   [2018]   [Sep]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectWARNING in sysfs_remove_group (2)
From
Hello,

syzbot found the following crash on:

HEAD commit: 234b69e3e089 ocfs2: fix ocfs2 read block panic
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15ee0d11400000
kernel config: https://syzkaller.appspot.com/x/.config?x=5fa12be50bca08d8
dashboard link: https://syzkaller.appspot.com/bug?extid=34cbd0f790e5ab87f63b
compiler: gcc (GCC) 8.0.1 20180413 (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+34cbd0f790e5ab87f63b@syzkaller.appspotmail.com

kobject_add_internal failed for rfkill10 (error: -2 parent: hci1)
------------[ cut here ]------------
sysfs group 'power' not found for kobject 'hci1'
WARNING: CPU: 1 PID: 11200 at fs/sysfs/group.c:255
sysfs_remove_group+0x15b/0x1b0 fs/sysfs/group.c:253
Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 11200 Comm: syz-executor3 Not tainted 4.19.0-rc4+ #25
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+0x1c4/0x2b4 lib/dump_stack.c:113
kobject: 'loop2' (00000000c60b67bc): kobject_uevent_env
panic+0x238/0x4e7 kernel/panic.c:184
kobject: 'loop2' (00000000c60b67bc): fill_kobj_path: path
= '/devices/virtual/block/loop2'
__warn.cold.8+0x163/0x1ba kernel/panic.c:536
report_bug+0x254/0x2d0 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:178 [inline]
do_error_trap+0x1fc/0x4d0 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:993
RIP: 0010:sysfs_remove_group+0x15b/0x1b0 fs/sysfs/group.c:253
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 20 5d 18 88 e8 a5 07 50 ff <0f> 0b eb 92 e8
ec 81 c9 ff e9 d0 fe ff ff 48 89 df e8 df 81 c9 ff
RSP: 0018:ffff88019993f550 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffffffff885f83c0 RCX: ffffc90005079000
RDX: 000000000001f3e2 RSI: ffffffff8164fd15 RDI: 0000000000000005
RBP: ffff88019993f578 R08: ffff880195688140 R09: ffffed003b5e4fe8
R10: ffffed003b5e4fe8 R11: ffff8801daf27f47 R12: 0000000000000000
R13: ffff8801d2636990 R14: ffffffff885f8960 R15: 0000000000000000
dpm_sysfs_remove+0x58/0x60 drivers/base/power/sysfs.c:734
device_del+0x118/0xb70 drivers/base/core.c:2054
hci_unregister_dev+0x3c2/0xbf0 net/bluetooth/hci_core.c:3290
vhci_release+0x76/0xf0 drivers/bluetooth/hci_vhci.c:354
__fput+0x385/0xa30 fs/file_table.c:278
____fput+0x15/0x20 fs/file_table.c:309
task_work_run+0x1e8/0x2a0 kernel/task_work.c:113
get_signal+0x155e/0x1980 kernel/signal.c:2343
do_signal+0x9c/0x21e0 arch/x86/kernel/signal.c:816
exit_to_usermode_loop+0x2e5/0x380 arch/x86/entry/common.c:162
prepare_exit_to_usermode arch/x86/entry/common.c:197 [inline]
syscall_return_slowpath arch/x86/entry/common.c:268 [inline]
do_syscall_64+0x6be/0x820 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
kobject: 'loop0' (0000000011f4c275): kobject_uevent_env
RIP: 0033:0x457679
kobject: 'loop0' (0000000011f4c275): fill_kobj_path: path
= '/devices/virtual/block/loop0'
Code: 1d b4 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 eb b3 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fa1ca1b9c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: 0000000000000002 RBX: 00007fa1ca1ba6d4 RCX: 0000000000457679
RDX: 0000000000000002 RSI: 00000000200000c0 RDI: 0000000000000006
RBP: 000000000072bf00 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 00000000004d8628 R14: 00000000004c51dd R15: 0000000000000000
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 syzkaller@googlegroups.com.

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

\
 
 \ /
  Last update: 2018-09-21 10:58    [W:0.083 / U:0.400 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site