From: Yonghong Song <yonghong.song@linux.dev>
To: Aleksandr Nogikh <nogikh@google.com>,
Alexander Potapenko <glider@google.com>
Cc: syzbot <syzbot+603bcd9b0bf1d94dbb9b@syzkaller.appspotmail.com>,
andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, eddyz87@gmail.com, haoluo@google.com,
john.fastabend@gmail.com, jolsa@kernel.org, kpsingh@kernel.org,
linux-kernel@vger.kernel.org, martin.lau@linux.dev,
sdf@google.com, song@kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bpf?] KMSAN: uninit-value in trie_delete_elem
Date: Tue, 2 Apr 2024 20:59:10 -0700 [thread overview]
Message-ID: <02d29315-13ee-45c1-984e-13c98e88247b@linux.dev> (raw)
In-Reply-To: <CANp29Y4WcXr7vd=cvdtxRWaPxOKzr97f9L+BXtm07AGGiW2j2A@mail.gmail.com>
On 4/1/24 11:36 PM, Aleksandr Nogikh wrote:
> Hi,
>
> On Mon, Apr 1, 2024 at 8:55 PM Yonghong Song <yonghong.song@linux.dev> wrote:
>>
>> On 3/26/24 12:00 PM, syzbot wrote:
>>> Hello,
>>>
>>> syzbot found the following issue on:
>>>
>>> =====================================================
>>> BUG: KMSAN: uninit-value in trie_delete_elem+0xc0/0xbe0 kernel/bpf/lpm_trie.c:448
>> Unrelated to the bug itself, with KMSAN is enabled, qemu cannot boot my vm
>> any more. Anything special I need to do in order to boot a KMSAN kernel?
>>
> Does the kernel print any specific errors to the serial console while
> booting? Or nothing at all?
In my case, nothing at all.
>
next prev parent reply other threads:[~2024-04-03 3:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 19:00 [syzbot] [bpf?] KMSAN: uninit-value in trie_delete_elem syzbot
2024-03-29 19:52 ` syzbot
2024-04-01 18:55 ` Yonghong Song
2024-04-02 6:36 ` Aleksandr Nogikh
2024-04-03 3:59 ` Yonghong Song [this message]
2024-04-03 8:47 ` Aleksandr Nogikh
2024-04-04 19:00 ` Yonghong Song
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=02d29315-13ee-45c1-984e-13c98e88247b@linux.dev \
--to=yonghong.song@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=glider@google.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=nogikh@google.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=syzbot+603bcd9b0bf1d94dbb9b@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox