All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+b5ad66046b913bc04c6f@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] KMSAN: uninit-value in __llc_lookup_established
Date: Wed, 06 Dec 2023 00:01:03 -0800	[thread overview]
Message-ID: <000000000000af965b060bd2c08b@google.com> (raw)
In-Reply-To: <tencent_EE98A7D746C352F2464689936ED8AEF14C06@qq.com>

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
KMSAN: uninit-value in __llc_lookup_established

syz-executor.0 uses obsolete (PF_INET,SOCK_PACKET)
3sp: 4352, 1024, 4352
=====================================================
BUG: KMSAN: uninit-value in __llc_lookup_established+0xe9d/0xf90
 __llc_lookup_established+0xe9d/0xf90
 __llc_lookup net/llc/llc_conn.c:611 [inline]
 llc_conn_handler+0x4bd/0x1360 net/llc/llc_conn.c:791
 llc_rcv+0x105b/0x1520 net/llc/llc_input.c:208
 __netif_receive_skb_one_core net/core/dev.c:5527 [inline]
 __netif_receive_skb+0x1a6/0x5a0 net/core/dev.c:5641
 netif_receive_skb_internal net/core/dev.c:5727 [inline]
 netif_receive_skb+0x58/0x660 net/core/dev.c:5786
 tun_rx_batched+0x3ee/0x980 drivers/net/tun.c:1555
 tun_get_user+0x53af/0x66d0 drivers/net/tun.c:2002
 tun_chr_write_iter+0x3af/0x5d0 drivers/net/tun.c:2048
 call_write_iter include/linux/fs.h:2020 [inline]
 new_sync_write fs/read_write.c:491 [inline]
 vfs_write+0x8ef/0x1490 fs/read_write.c:584
 ksys_write+0x20f/0x4c0 fs/read_write.c:637
 __do_sys_write fs/read_write.c:649 [inline]
 __se_sys_write fs/read_write.c:646 [inline]
 __x64_sys_write+0x93/0xd0 fs/read_write.c:646
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x44/0x110 arch/x86/entry/common.c:82
 entry_SYSCALL_64_after_hwframe+0x63/0x6b

Local variable daddr created at:
 llc_conn_handler+0x53/0x1360 net/llc/llc_conn.c:783
 llc_rcv+0x105b/0x1520 net/llc/llc_input.c:208

CPU: 1 PID: 5474 Comm: syz-executor.0 Not tainted 6.6.0-syzkaller-14500-g1c41041124bd-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
=====================================================


Tested on:

commit:         1c410411 Merge tag 'i3c/for-6.7' of git://git.kernel.o..
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=148a49b4e80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=956549bd1d1e9efd
dashboard link: https://syzkaller.appspot.com/bug?extid=b5ad66046b913bc04c6f
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=16c0649ce80000


       reply	other threads:[~2023-12-06  8:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tencent_EE98A7D746C352F2464689936ED8AEF14C06@qq.com>
2023-12-06  8:01 ` syzbot [this message]
     [not found] <tencent_832FC96FC0960CE862ED52CF3079966C4C0A@qq.com>
2023-12-06 10:29 ` [syzbot] [net?] KMSAN: uninit-value in __llc_lookup_established syzbot
     [not found] <tencent_7D2FCFAD8DEEA5D60DCF9236DD9B5DAD9907@qq.com>
2023-12-06  9:24 ` syzbot
     [not found] <tencent_F966ECFECCAC7AC26D7C2C3D6F049664E80A@qq.com>
2023-12-06  8:23 ` syzbot
     [not found] <tencent_8F9E041BAF4BC41B1C2558BA38BBE233E808@qq.com>
2023-12-06  1:55 ` syzbot
2023-12-05 18:25 syzbot
2023-12-06  0:53 ` Kuniyuki Iwashima
2023-12-06  1:28   ` syzbot
2023-12-06  1:14 ` syzbot
2023-12-06  7:08 ` syzbot
2023-12-06  8:13 ` syzbot
2023-12-06  9:07 ` syzbot
2023-12-06 10:09 ` 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=000000000000af965b060bd2c08b@google.com \
    --to=syzbot+b5ad66046b913bc04c6f@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.