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: Wed, 19 Jun 2024 23:16:03 -0700 [thread overview]
Message-ID: <000000000000dcb17f061b4c3fff@google.com> (raw)
In-Reply-To: <PN2PR01MB4891F4EFEAE9CD9E25BBAA6DFCC82@PN2PR01MB4891.INDPRD01.PROD.OUTLOOK.COM>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to checkout kernel repo https://linux.googlesource.com/linux/kernel/git/torvalds/linux on commit 0daa6e5ed1ccdeb65e07d4884961a8bb288a0f54: failed to run ["git" "checkout" "0daa6e5ed1ccdeb65e07d4884961a8bb288a0f54"]: exit status 128
fatal: Cannot switch branch to a non-commit '0daa6e5ed1ccdeb65e07d4884961a8bb288a0f54'
Tested on:
commit: [unknown
git tree: https://linux.googlesource.com/linux/kernel/git/torvalds/linux 0daa6e5ed1ccdeb65e07d4884961a8bb288a0f54
kernel config: https://syzkaller.appspot.com/x/.config?x=13e7da432565d94c
dashboard link: https://syzkaller.appspot.com/bug?extid=c33bff5d5da1391df027
compiler:
Note: no patches were applied.
next parent reply other threads:[~2024-06-20 6:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <PN2PR01MB4891F4EFEAE9CD9E25BBAA6DFCC82@PN2PR01MB4891.INDPRD01.PROD.OUTLOOK.COM>
2024-06-20 6:16 ` syzbot [this message]
[not found] <20240701100153.10990-1-wojciech.gladysz@infogain.com>
2024-07-01 12:06 ` [syzbot] [net?] [bpf?] KMSAN: uninit-value in sock_hash_delete_elem syzbot
[not found] <PN2PR01MB489157F204C812E350B53303FCC82@PN2PR01MB4891.INDPRD01.PROD.OUTLOOK.COM>
2024-06-20 8:02 ` syzbot
[not found] <PN2PR01MB489118B0901BB49F1880F759FCC82@PN2PR01MB4891.INDPRD01.PROD.OUTLOOK.COM>
2024-06-20 6:15 ` syzbot
[not found] <20240614120407.28400-1-wojciech.gladysz@infogain.com>
2024-06-15 15:12 ` syzbot
[not found] <20240614120103.27422-1-wojciech.gladysz@infogain.com>
2024-06-15 7:42 ` 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=000000000000dcb17f061b4c3fff@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 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.