From: syzbot <syzbot+34ad5fab48f7bf510349@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, ryasuoka@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] KMSAN: kernel-infoleak in __skb_datagram_iter (2)
Date: Mon, 19 Feb 2024 18:56:02 -0800 [thread overview]
Message-ID: <000000000000c5436c0611c759aa@google.com> (raw)
In-Reply-To: <ZdQRnIUGz-j1ubag@zeus>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to checkout kernel repo git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git on commit 5bd7ef53ffe5: failed to run ["git" "fetch" "--force" "--tags" "f569e972c8e9057ee9c286220c83a480ebf30cc5" "5bd7ef53ffe5"]: exit status 128
fatal: couldn't find remote ref 5bd7ef53ffe5
Tested on:
commit: [unknown
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 5bd7ef53ffe5
kernel config: https://syzkaller.appspot.com/x/.config?x=f3f069371247b697
dashboard link: https://syzkaller.appspot.com/bug?extid=34ad5fab48f7bf510349
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=17c8b658180000
next parent reply other threads:[~2024-02-20 2:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ZdQRnIUGz-j1ubag@zeus>
2024-02-20 2:56 ` syzbot [this message]
[not found] <ZdSUXJYRA8jatpIP@zeus>
2024-02-20 12:25 ` [syzbot] [net?] KMSAN: kernel-infoleak in __skb_datagram_iter (2) syzbot
[not found] <20240220.161605.1886801832131178688.syoshida@redhat.com>
2024-02-20 7:47 ` syzbot
[not found] <ZdQvap_8BIiIq_GB@zeus>
2024-02-20 5:27 ` syzbot
[not found] <CAHpthZpJeO1JGpOS3h_7n-wu28pEZuxo-SVB=x=OJKXpZ71Brg@mail.gmail.com>
2024-02-17 14:55 ` syzbot
[not found] <CAHpthZoG-4eO91UNScaiL1GUcoTZRDMQDzTZ0RvhGZdRZHHGLw@mail.gmail.com>
2024-02-17 12:58 ` syzbot
[not found] <CAHpthZr+VHsntmc5QRrL+viRKDu4sWJcX2Yf+oauEv9FghyB0A@mail.gmail.com>
2024-02-15 9:51 ` syzbot
2024-02-02 13:26 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=000000000000c5436c0611c759aa@google.com \
--to=syzbot+34ad5fab48f7bf510349@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ryasuoka@redhat.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