From: Greg KH <gregkh@linuxfoundation.org>
To: Jiacheng Xu <578001344xu@gmail.com>
Cc: linux-kernel@vger.kernel.org, axboe@kernel.dk,
asml.silence@gmail.co, io-uring@vger.kernel.org,
security@kernel.org
Subject: Re: KASAN: null-ptr-deref Write in io_file_get_normal
Date: Tue, 16 Aug 2022 18:21:15 +0200 [thread overview]
Message-ID: <YvvD+wB64nBSpM3M@kroah.com> (raw)
In-Reply-To: <CAO4S-mdVW5GkODk0+vbQexNAAJZopwzFJ9ACvRCJ989fQ4A6Ow@mail.gmail.com>
On Wed, Aug 17, 2022 at 12:10:09AM +0800, Jiacheng Xu wrote:
> Hello,
>
> When using modified Syzkaller to fuzz the Linux kernel-5.15.58, the
> following crash was triggered.
As you sent this to public lists, there's no need to also cc:
security@k.o as there's nothing we can do about this.
Also, random syzbot submissions are best sent with a fix for them,
otherwise it might be a while before they will be looked at.
good luck!
greg k-h
next prev parent reply other threads:[~2022-08-16 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 16:10 KASAN: null-ptr-deref Write in io_file_get_normal Jiacheng Xu
2022-08-16 16:21 ` Greg KH [this message]
2022-08-16 16:57 ` Jens Axboe
2022-08-17 6:49 ` Greg KH
2022-08-17 14:22 ` Jens Axboe
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=YvvD+wB64nBSpM3M@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=578001344xu@gmail.com \
--cc=asml.silence@gmail.co \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=security@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).