From: syzbot <syzbot+c15aa445274af8674f41@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, sinquersw@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] WARNING in ip6_route_info_create
Date: Mon, 29 Jan 2024 14:07:04 -0800 [thread overview]
Message-ID: <000000000000b2c04006101cdd70@google.com> (raw)
In-Reply-To: <990fd3ca-fdb6-4e8e-96ae-b7e939060d7b@gmail.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to checkout kernel repo git@github.com:ThinkerYzu/linux.git/fix-gc-uaf: failed to run ["git" "fetch" "--force" "7f85d17015ba166311ead463ef566bfcdfcee3b7" "fix-gc-uaf"]: exit status 128
Host key verification failed.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Tested on:
commit: [unknown
git tree: git@github.com:ThinkerYzu/linux.git fix-gc-uaf
kernel config: https://syzkaller.appspot.com/x/.config?x=f8715b6ede5c4b90
dashboard link: https://syzkaller.appspot.com/bug?extid=c15aa445274af8674f41
compiler:
Note: no patches were applied.
next parent reply other threads:[~2024-01-29 22:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <990fd3ca-fdb6-4e8e-96ae-b7e939060d7b@gmail.com>
2024-01-29 22:07 ` syzbot [this message]
[not found] <2b51ae8f-141e-4663-9aea-85bd338bbb0a@gmail.com>
2024-01-30 23:55 ` [syzbot] [net?] WARNING in ip6_route_info_create syzbot
[not found] <d7b5e144-7d10-40cd-abd6-91578d29fb3f@gmail.com>
2024-01-29 23:38 ` syzbot
[not found] <3aef3775-1468-41e6-846d-35d740852889@gmail.com>
2024-01-29 22:36 ` syzbot
[not found] <a24c6301-3408-4bf6-9c56-99685e1c8e47@gmail.com>
2024-01-29 21:40 ` syzbot
[not found] <2527e5c5-f99c-4f1c-bd46-ed97060e8ca8@gmail.com>
2023-12-08 0:49 ` syzbot
[not found] <93835aea-7f9a-4026-ad45-c9d5ab62a3d3@gmail.com>
2023-12-08 0:08 ` syzbot
[not found] <41525f35-14b4-4179-8ec2-10a5c42cb9cd@gmail.com>
2023-12-07 23:43 ` syzbot
2023-12-07 18:17 syzbot
2023-12-07 18:19 ` Eric Dumazet
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=000000000000b2c04006101cdd70@google.com \
--to=syzbot+c15aa445274af8674f41@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sinquersw@gmail.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