From: Greg KH <greg@kroah.com>
To: esploit <esploit@protonmail.ch>
Cc: "dgilbert@interlog.com" <dgilbert@interlog.com>,
"jejb@linux.ibm.com" <jejb@linux.ibm.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"security@kernel.org" <security@kernel.org>
Subject: Re: PROBLEM: syzkaller found / pool corruption-overwrite / page in user-area or NULL
Date: Thu, 10 Jan 2019 20:27:36 +0100 [thread overview]
Message-ID: <20190110192736.GA27348@kroah.com> (raw)
In-Reply-To: <FTiTvUZRA5yMupEMxO6bakUBM0kgENu3iSyKzomSMpfDWnMJ-AQbx4X3GRTNzNE2ZxaMAEU3nfYARed4mpJV-xC6lBR6PR5hsWKwbvAs5II=@protonmail.ch>
On Thu, Jan 10, 2019 at 07:05:26PM +0000, esploit wrote:
> Hi, I've been getting more into Kernel stuff lately and forged ahead
> with some syzkaller bug finding.
for syzkaller stuff, no need to cc: the security mailing list. Just
work with the respective subsystem maintainers and developers (like you
properly cc:ed) and all should be fine.
thanks!
greg k-h
next parent reply other threads:[~2019-01-10 19:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <FTiTvUZRA5yMupEMxO6bakUBM0kgENu3iSyKzomSMpfDWnMJ-AQbx4X3GRTNzNE2ZxaMAEU3nfYARed4mpJV-xC6lBR6PR5hsWKwbvAs5II=@protonmail.ch>
2019-01-10 19:27 ` Greg KH [this message]
2019-01-10 19:12 PROBLEM: syzkaller found / pool corruption-overwrite / page in user-area or NULL Esme
2019-01-10 19:58 ` James Bottomley
2019-01-10 20:39 ` Qian Cai
2019-01-10 20:44 ` Qian Cai
2019-01-10 20:47 ` Esme
2019-01-10 21:03 ` Qian Cai
2019-01-10 21:35 ` Esme
2019-01-10 22:33 ` Qian Cai
2019-01-10 22:58 ` Esme
2019-01-11 1:30 ` Qian Cai
2019-01-11 3:15 ` Esme
2019-01-11 4:52 ` Qian Cai
2019-01-11 5:01 ` Esme
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=20190110192736.GA27348@kroah.com \
--to=greg@kroah.com \
--cc=dgilbert@interlog.com \
--cc=esploit@protonmail.ch \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--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