From: syzbot <syzbot+6ea290ba76d8c1eb1ac2@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] KMSAN: uninit-value in hci_rx_work
Date: Mon, 07 Oct 2024 06:01:03 -0700 [thread overview]
Message-ID: <6703db8f.050a0220.49194.0508.GAE@google.com> (raw)
In-Reply-To: <tencent_E4F3C6420991AEE0AEEB4C80A7CB06CE5206@qq.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
KMSAN: uninit-value in hci_rx_work
=====================================================
BUG: KMSAN: uninit-value in hci_acldata_packet net/bluetooth/hci_core.c:3796 [inline]
BUG: KMSAN: uninit-value in hci_rx_work+0x1092/0x11f0 net/bluetooth/hci_core.c:4030
hci_acldata_packet net/bluetooth/hci_core.c:3796 [inline]
hci_rx_work+0x1092/0x11f0 net/bluetooth/hci_core.c:4030
process_one_work kernel/workqueue.c:3229 [inline]
process_scheduled_works+0xae0/0x1c40 kernel/workqueue.c:3310
worker_thread+0xea7/0x14f0 kernel/workqueue.c:3391
kthread+0x3e2/0x540 kernel/kthread.c:389
ret_from_fork+0x6d/0x90 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
Uninit was created at:
slab_post_alloc_hook mm/slub.c:4091 [inline]
slab_alloc_node mm/slub.c:4134 [inline]
kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4186
kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587
__alloc_skb+0x363/0x7b0 net/core/skbuff.c:678
alloc_skb include/linux/skbuff.h:1322 [inline]
bt_skb_alloc include/net/bluetooth/bluetooth.h:493 [inline]
vhci_get_user drivers/bluetooth/hci_vhci.c:487 [inline]
vhci_write+0x122/0x960 drivers/bluetooth/hci_vhci.c:608
new_sync_write fs/read_write.c:590 [inline]
vfs_write+0xb28/0x1540 fs/read_write.c:683
ksys_write+0x24f/0x4c0 fs/read_write.c:736
__do_sys_write fs/read_write.c:748 [inline]
__se_sys_write fs/read_write.c:745 [inline]
__x64_sys_write+0x93/0xe0 fs/read_write.c:745
x64_sys_call+0x306a/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:2
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
CPU: 0 UID: 0 PID: 4561 Comm: kworker/u9:1 Tainted: G W 6.12.0-rc2-syzkaller-g8cf0b93919e1-dirty #0
Tainted: [W]=WARN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Workqueue: hci0 hci_rx_work
=====================================================
Tested on:
commit: 8cf0b939 Linux 6.12-rc2
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=121adb80580000
kernel config: https://syzkaller.appspot.com/x/.config?x=981fe2ff8a1e457a
dashboard link: https://syzkaller.appspot.com/bug?extid=6ea290ba76d8c1eb1ac2
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=150fc707980000
next prev parent reply other threads:[~2024-10-07 13:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 21:07 [syzbot] [bluetooth?] KMSAN: uninit-value in hci_rx_work syzbot
2024-10-07 10:05 ` syzbot
2024-10-07 10:53 ` Edward Adam Davis
2024-10-07 13:01 ` syzbot [this message]
2024-10-08 3:40 ` Edward Adam Davis
2024-10-08 4:29 ` syzbot
2024-10-08 9:30 ` Edward Adam Davis
2024-10-08 10:03 ` syzbot
2024-10-08 10:47 ` [PATCH] Bluetooth: hci_core: remove acl hdr handle error message Edward Adam Davis
2024-10-08 14:12 ` Luiz Augusto von Dentz
2024-10-08 14:30 ` Luiz Augusto von Dentz
2024-10-08 14:58 ` [syzbot] [bluetooth?] KMSAN: uninit-value in hci_rx_work syzbot
2024-10-09 1:07 ` [PATCH] Bluetooth: hci_core: remove acl hdr handle error message Edward Adam Davis
2024-10-09 1:36 ` [syzbot] [bluetooth?] KMSAN: uninit-value in hci_rx_work syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6703db8f.050a0220.49194.0508.GAE@google.com \
--to=syzbot+6ea290ba76d8c1eb1ac2@syzkaller.appspotmail.com \
--cc=eadavis@qq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox