From: Martin KaFai Lau <martin.lau@linux.dev>
To: ast@kernel.org, yonghong.song@linux.dev
Cc: daniel@iogearbox.net, davem@davemloft.net, eddyz87@gmail.com,
haoluo@google.com, hawk@kernel.org, john.fastabend@gmail.com,
jolsa@kernel.org, kpsingh@kernel.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
sdf@google.com, song@kernel.org, syzkaller-bugs@googlegroups.com,
andrii@kernel.org, alexei.starovoitov@gmail.com,
bpf@vger.kernel.org,
syzbot <syzbot+1a3cf6f08d68868f9db3@syzkaller.appspotmail.com>
Subject: Re: [syzbot] [bpf?] [net?] KMSAN: uninit-value in dev_map_lookup_elem
Date: Thu, 28 Mar 2024 11:23:07 -0700 [thread overview]
Message-ID: <16b32b53-5a01-43e8-93db-64778378fa09@linux.dev> (raw)
In-Reply-To: <000000000000c8d6b00614b599a2@google.com>
On 3/28/24 3:01 AM, syzbot wrote:
> Killed
> make[2]: *** [scripts/Makefile.vmlinux_o:62: vmlinux.o] Error 137
> make[2]: *** Deleting file 'vmlinux.o'
> make[1]: *** [/syzkaller/jobs/linux/kernel/Makefile:1141: vmlinux_o] Error 2
> make: *** [Makefile:240: __sub-make] Error 2
My second syzbot test attempt passed the build stage and passed the reproducer
also. https://lore.kernel.org/all/000000000000b7bdd80614bc433f@google.com/
Not sure what caused the syzbot build error in the first attempt but should be
unrelated to the fix. I will post the patch.
next prev parent reply other threads:[~2024-03-28 18:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 9:36 [syzbot] [bpf?] [net?] KMSAN: uninit-value in dev_map_lookup_elem syzbot
2024-03-27 0:53 ` Martin KaFai Lau
2024-03-27 1:07 ` Alexei Starovoitov
2024-03-27 4:47 ` Yonghong Song
2024-03-27 18:46 ` Martin KaFai Lau
2024-03-28 10:01 ` syzbot
2024-03-28 18:23 ` Martin KaFai Lau [this message]
2024-03-27 22:18 ` [syzbot] " syzbot
2024-03-27 23:41 ` syzbot
[not found] <2f61db11-f3f1-4574-b510-dce42763863f@linux.dev>
2024-03-28 17:58 ` syzbot
[not found] <1921e7e8-3c43-4f3c-9709-874b37ea9c81@linux.dev>
2024-03-28 19:12 ` 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=16b32b53-5a01-43e8-93db-64778378fa09@linux.dev \
--to=martin.lau@linux.dev \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=syzbot+1a3cf6f08d68868f9db3@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yonghong.song@linux.dev \
/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.