From: syzbot <syzbot+c70d87ac1d001f29a058@syzkaller.appspotmail.com>
To: christophe.jaillet@wanadoo.fr, code@siddh.me,
dhowells@redhat.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] KASAN: use-after-free Read in post_one_notification
Date: Sat, 23 Jul 2022 06:21:09 -0700 [thread overview]
Message-ID: <000000000000e8a18905e478d258@google.com> (raw)
In-Reply-To: <20220723132000.195982-1-code@siddh.me>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to checkout kernel repo git@github.com:siddhpant/linux.git/post_one_notification: failed to run ["git" "fetch" "--force" "219a8dc7158a7de03b74c244ef07dcd062b9b3f7" "post_one_notification"]: 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:siddhpant/linux.git post_one_notification
dashboard link: https://syzkaller.appspot.com/bug?extid=c70d87ac1d001f29a058
compiler:
Note: no patches were applied.
next prev parent reply other threads:[~2022-07-23 13:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 13:25 [syzbot] KASAN: use-after-free Read in post_one_notification syzbot
2022-03-21 15:40 ` David Howells
2022-03-22 7:52 ` Dmitry Vyukov
2022-07-23 13:20 ` Siddh Raman Pant
2022-07-23 13:21 ` syzbot [this message]
2022-07-23 13:22 ` Siddh Raman Pant
2022-07-23 13:42 ` syzbot
2022-07-24 3:41 ` Siddh Raman Pant
2022-07-24 4:01 ` syzbot
2022-07-28 15:30 ` Siddh Raman Pant
2022-07-28 15:50 ` syzbot
[not found] <20220723142031.2316-1-hdanton@sina.com>
2022-07-23 14:39 ` syzbot
[not found] <20220801103533.972-1-hdanton@sina.com>
2022-08-01 10:54 ` syzbot
2022-08-02 22:27 ` Eric Biggers
2022-08-03 4:04 ` Siddh Raman Pant
2022-08-03 4:09 ` Eric Biggers
2022-08-03 5:17 ` Siddh Raman Pant
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=000000000000e8a18905e478d258@google.com \
--to=syzbot+c70d87ac1d001f29a058@syzkaller.appspotmail.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=code@siddh.me \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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.