From: Pavel Skripkin <paskripkin@gmail.com>
To: syzbot <syzbot+8f5f07bb9d6935e2f8d9@syzkaller.appspotmail.com>,
andrew@lunn.ch, davem@davemloft.net, glider@google.com,
kuba@kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, linux@rempel-privat.de,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] KMSAN: uninit-value in asix_check_host_enable
Date: Wed, 23 Feb 2022 14:01:33 +0300 [thread overview]
Message-ID: <2c775ec8-6fcb-cdeb-9b7c-35822c74bbde@gmail.com> (raw)
In-Reply-To: <00000000000024a1f805d8ac1da3@google.com>
On 2/23/22 12:30, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 724946410067 x86: kmsan: enable KMSAN builds for x86
> git tree: https://github.com/google/kmsan.git master
> console output: https://syzkaller.appspot.com/x/log.txt?x=11c85246700000
> kernel config: https://syzkaller.appspot.com/x/.config?x=76f99026248b24e4
> dashboard link: https://syzkaller.appspot.com/bug?extid=8f5f07bb9d6935e2f8d9
> compiler: clang version 14.0.0 (/usr/local/google/src/llvm-git-monorepo 2b554920f11c8b763cd9ed9003f4e19b919b8e1f), GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11674fe2700000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1497324c700000
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+8f5f07bb9d6935e2f8d9@syzkaller.appspotmail.com
>
Should be fixed by [1], but it's only in next for now.
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=920a9fa27e7805499cfe78491b36fed2322c02ec
With regards,
Pavel Skripkin
next prev parent reply other threads:[~2022-02-23 11:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 9:30 [syzbot] KMSAN: uninit-value in asix_check_host_enable syzbot
2022-02-23 11:01 ` Pavel Skripkin [this message]
2022-03-07 9:05 ` Dmitry Vyukov
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=2c775ec8-6fcb-cdeb-9b7c-35822c74bbde@gmail.com \
--to=paskripkin@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=glider@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=netdev@vger.kernel.org \
--cc=syzbot+8f5f07bb9d6935e2f8d9@syzkaller.appspotmail.com \
--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.