From: syzbot <syzbot+1a3cf6f08d68868f9db3@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, martin.lau@linux.dev,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bpf?] [net?] KMSAN: uninit-value in dev_map_lookup_elem
Date: Thu, 28 Mar 2024 12:12:03 -0700 [thread overview]
Message-ID: <0000000000006576fd0614bd4cb6@google.com> (raw)
In-Reply-To: <1921e7e8-3c43-4f3c-9709-874b37ea9c81@linux.dev>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+1a3cf6f08d68868f9db3@syzkaller.appspotmail.com
Tested on:
commit: d8889e86 bpf: Mark bpf prog stack with kmsan_unposion_..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/martin.lau/bpf-next.git
console output: https://syzkaller.appspot.com/x/log.txt?x=155ac345180000
kernel config: https://syzkaller.appspot.com/x/.config?x=e6bd769cb793b98a
dashboard link: https://syzkaller.appspot.com/bug?extid=1a3cf6f08d68868f9db3
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2024-03-28 19:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1921e7e8-3c43-4f3c-9709-874b37ea9c81@linux.dev>
2024-03-28 19:12 ` syzbot [this message]
[not found] <2f61db11-f3f1-4574-b510-dce42763863f@linux.dev>
2024-03-28 17:58 ` [syzbot] [bpf?] [net?] KMSAN: uninit-value in dev_map_lookup_elem syzbot
2024-03-25 9:36 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
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=0000000000006576fd0614bd4cb6@google.com \
--to=syzbot+1a3cf6f08d68868f9db3@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--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.