From: Greg KH <gregkh@linuxfoundation.org>
To: Sabyrzhan Tasbolatov <snovitoll@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alexander Potapenko <glider@google.com>,
Aleksandr Nogikh <nogikh@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>
Subject: Re: [RFC] syzkaller/docs: reporting kernel security bugs guide
Date: Mon, 11 Nov 2024 15:42:30 +0100 [thread overview]
Message-ID: <2024111129-hence-resigned-b2e7@gregkh> (raw)
In-Reply-To: <2024111124-hardly-jaundice-08c4@gregkh>
On Mon, Nov 11, 2024 at 03:37:27PM +0100, Greg KH wrote:
> On Mon, Nov 11, 2024 at 06:24:36PM +0500, Sabyrzhan Tasbolatov wrote:
> > Hello,
> >
> > Greg,
> > Could you please confirm that the updated version of
> > reporting Linux kernel security bugs guide is correct
> > since kernel.org is CNA as of February 13, 2024 and
> > with linux-cve-announce reference?
> >
> > The updated doc and drawn diagram is available
> > in this PR of syzkaller project:
> > https://github.com/google/syzkaller/pull/5461
>
> I can't read this mess:
> https://github.com/google/syzkaller/pull/5461/commits/35b45ef3c4600fd62f5d05a17fc6855fc0b5e402
>
> So I have no idea, sorry.
Ah, the graph is at the bottom of the page, kind of messy...
Anyway, as I have stated numerous times, I DO NOT RECOMMEND EVER
CONTACTING the linux-distros mailing list for lots of various reasons.
You do so at your own risk and liability (i.e. doing so imparts a number
of requirements on you!) So be VERY VERY VERY careful to ever tell
anyone to do so as the side affects can be very bad in some cases (i.e.
they "blackmail" you to release information even if you don't have a
fix.)
good luck!
greg k-h
next prev parent reply other threads:[~2024-11-11 14:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 13:24 [RFC] syzkaller/docs: reporting kernel security bugs guide Sabyrzhan Tasbolatov
2024-11-11 14:37 ` Greg KH
2024-11-11 14:42 ` Greg KH [this message]
2024-11-11 15:36 ` Sabyrzhan Tasbolatov
2024-11-11 18:54 ` Greg KH
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=2024111129-hence-resigned-b2e7@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andreyknvl@gmail.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nogikh@google.com \
--cc=snovitoll@gmail.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.