From: syzbot <syzbot+c33bff5d5da1391df027@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
wojciech.gladysz@infogain.com
Subject: Re: [syzbot] [net?] [bpf?] KMSAN: uninit-value in sock_hash_delete_elem
Date: Sat, 15 Jun 2024 00:42:03 -0700 [thread overview]
Message-ID: <0000000000003e95b0061ae8ded7@google.com> (raw)
In-Reply-To: <20240614120103.27422-1-wojciech.gladysz@infogain.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+c33bff5d5da1391df027@syzkaller.appspotmail.com
Tested on:
commit: e478cf26 Merge branch 'bpf-fix-a-couple-of-test-failur..
git tree: https://linux.googlesource.com/linux/kernel/git/torvalds/linux
console output: https://syzkaller.appspot.com/x/log.txt?x=140ab12e980000
kernel config: https://syzkaller.appspot.com/x/.config?x=e2599baf258ef795
dashboard link: https://syzkaller.appspot.com/bug?extid=c33bff5d5da1391df027
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=168670b6980000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2024-06-15 7:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240614120103.27422-1-wojciech.gladysz@infogain.com>
2024-06-15 7:42 ` syzbot [this message]
[not found] <20240614120407.28400-1-wojciech.gladysz@infogain.com>
2024-06-15 15:12 ` [syzbot] [net?] [bpf?] KMSAN: uninit-value in sock_hash_delete_elem syzbot
[not found] <PN2PR01MB489118B0901BB49F1880F759FCC82@PN2PR01MB4891.INDPRD01.PROD.OUTLOOK.COM>
2024-06-20 6:15 ` syzbot
[not found] <PN2PR01MB4891F4EFEAE9CD9E25BBAA6DFCC82@PN2PR01MB4891.INDPRD01.PROD.OUTLOOK.COM>
2024-06-20 6:16 ` syzbot
[not found] <PN2PR01MB489157F204C812E350B53303FCC82@PN2PR01MB4891.INDPRD01.PROD.OUTLOOK.COM>
2024-06-20 8:02 ` syzbot
[not found] <20240701100153.10990-1-wojciech.gladysz@infogain.com>
2024-07-01 12:06 ` 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=0000000000003e95b0061ae8ded7@google.com \
--to=syzbot+c33bff5d5da1391df027@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wojciech.gladysz@infogain.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