WARNING in hci_sock_sendmsg

8 vistas
Ir al primer mensaje no leído

syzbot

no leída,
10 dic 2022, 11:47:37 a.m.10/12/22
para syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15e5276d880000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=6ec061e44103c2c4e0d8
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/98c0bdb4abb3/disk-3f8a27f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ea228ff02669/vmlinux-3f8a27f9.xz

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

AppArmor: change_hat: Invalid input '0'
WARNING: CPU: 0 PID: 2022 at kernel/workqueue.c:1384 __queue_work+0xc8d/0x1100 kernel/workqueue.c:1384
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 2022 Comm: syz-executor.4 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:__queue_work+0xc8d/0x1100 kernel/workqueue.c:1384
Code: 03 38 d0 7c 09 84 d2 74 05 e8 0f 3a 5a 00 8b 5b 24 31 ff 83 e3 20 89 de e8 10 5f 24 00 85 db 0f 85 c2 00 00 00 e8 93 5d 24 00 <0f> 0b e9 5d f9 ff ff e8 87 5d 24 00 4c 8d 75 60 41 83 cd 02 e9 02
RSP: 0018:ffff88809d9e7a30 EFLAGS: 00010016
RAX: 0000000000040000 RBX: 0000000000000000 RCX: ffffc90008619000
RDX: 000000000000023a RSI: ffffffff813e27dd RDI: 0000000000000005
RBP: 0000000000010000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff8880833068a8
R13: ffff8880a9a61d40 R14: 0000000000000000 R15: 0000000000000008
queue_work_on+0x17e/0x1f0 kernel/workqueue.c:1489
queue_work include/linux/workqueue.h:512 [inline]
hci_sock_sendmsg+0x135b/0x20f0 net/bluetooth/hci_sock.c:1819
sock_sendmsg_nosec net/socket.c:651 [inline]
sock_sendmsg+0xc3/0x120 net/socket.c:661
sock_write_iter+0x287/0x3c0 net/socket.c:966
call_write_iter include/linux/fs.h:1821 [inline]
new_sync_write fs/read_write.c:474 [inline]
__vfs_write+0x51b/0x770 fs/read_write.c:487
vfs_write+0x1f3/0x540 fs/read_write.c:549
ksys_write+0x12b/0x2a0 fs/read_write.c:599
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7fbfe2fea0d9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 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 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fbfe155c168 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fbfe3109f80 RCX: 00007fbfe2fea0d9
RDX: 0000000000000009 RSI: 0000000020000040 RDI: 0000000000000004
RBP: 00007fbfe3045ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffe668d98af R14: 00007fbfe155c300 R15: 0000000000022000
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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

no leída,
9 abr 2023, 12:47:25 p.m.9/4/23
para syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Responder a todos
Responder al autor
Reenviar
0 mensajes nuevos