WARNING: ODEBUG bug in __init_work

5 lượt xem
Chuyển tới thư đầu tiên chưa đọc

syzbot

chưa đọc,
22:41:15 31 thg 10, 202031/10/20
đến syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 2b791501 Linux 4.14.203
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=143a1c8a500000
kernel config: https://syzkaller.appspot.com/x/.config?x=e52bb6f2a595a463
dashboard link: https://syzkaller.appspot.com/bug?extid=d242986ca1b1f12543f1
compiler: gcc (GCC) 10.1.0-syz 20200507

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

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

UDF-fs: warning (device loop4): udf_load_vrs: No anchor found
UDF-fs: Scanning with blocksize 1024 failed
ODEBUG: init active (active state 0) object type: work_struct hint: ieee80211_iface_work+0x0/0x770 include/linux/compiler.h:183
------------[ cut here ]------------
WARNING: CPU: 1 PID: 6990 at lib/debugobjects.c:287 debug_print_object.cold+0xa7/0xdb lib/debugobjects.c:287
Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 6990 Comm: syz-executor.3 Not tainted 4.14.203-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x283 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
__warn.cold+0x20/0x4b kernel/panic.c:547
report_bug+0x208/0x249 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:964
RIP: 0010:debug_print_object.cold+0xa7/0xdb lib/debugobjects.c:287
RSP: 0000:ffff8880b1a474b8 EFLAGS: 00010082
RAX: 0000000000000062 RBX: 0000000000000003 RCX: 0000000000000000
RDX: 0000000000040000 RSI: ffffffff8145dae0 RDI: ffffed1016348e8d
RBP: ffffffff878937e0 R08: 0000000000000062 R09: 0000000000000000
R10: 0000000000000000 R11: ffff88809d9b0280 R12: ffffffff86d216c0
R13: 0000000000000000 R14: ffffffff8c052148 R15: 00000000000b7340
__debug_object_init+0x447/0x7a0 lib/debugobjects.c:367
__init_work+0x3f/0x50 kernel/workqueue.c:506
ieee80211_setup_sdata+0x329/0xf40 net/mac80211/iface.c:1437
ieee80211_runtime_change_iftype net/mac80211/iface.c:1577 [inline]
ieee80211_if_change_type+0x3e8/0x470 net/mac80211/iface.c:1596
ieee80211_change_iface+0x26/0x1e0 net/mac80211/cfg.c:156
rdev_change_virtual_intf net/wireless/rdev-ops.h:69 [inline]
cfg80211_change_iface+0x246/0x13d0 net/wireless/util.c:1048
nl80211_set_interface+0x588/0x760 net/wireless/nl80211.c:2929
genl_family_rcv_msg+0x572/0xb20 net/netlink/genetlink.c:600
genl_rcv_msg+0xaf/0x140 net/netlink/genetlink.c:625
netlink_rcv_skb+0x125/0x390 net/netlink/af_netlink.c:2433
genl_rcv+0x24/0x40 net/netlink/genetlink.c:636
netlink_unicast_kernel net/netlink/af_netlink.c:1287 [inline]
netlink_unicast+0x437/0x610 net/netlink/af_netlink.c:1313
netlink_sendmsg+0x62e/0xb80 net/netlink/af_netlink.c:1878
sock_sendmsg_nosec net/socket.c:646 [inline]
sock_sendmsg+0xb5/0x100 net/socket.c:656
___sys_sendmsg+0x6c8/0x800 net/socket.c:2062
__sys_sendmsg+0xa3/0x120 net/socket.c:2096
SYSC_sendmsg net/socket.c:2107 [inline]
SyS_sendmsg+0x27/0x40 net/socket.c:2103
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x45deb9
RSP: 002b:00007f6e86878c78 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 000000000002bf00 RCX: 000000000045deb9
RDX: 0000000000000000 RSI: 0000000020000340 RDI: 0000000000000003
RBP: 000000000118bf60 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118bf2c
R13: 00007fffdc2d371f R14: 00007f6e868799c0 R15: 000000000118bf2c

======================================================


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

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

syzbot

chưa đọc,
16:06:13 27 thg 3, 202127/3/21
đến syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Trả lời tất cả
Trả lời tác giả
Chuyển tiếp
0 tin nhắn mới