From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Vegard Nossum <vegard.nossum@oracle.com>
Cc: corbet@lwn.net, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
security@kernel.org, linux@leemhuis.info,
Kees Cook <keescook@chromium.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Sasha Levin <sashal@kernel.org>, Lee Jones <lee@kernel.org>
Subject: Re: [PATCH v5] Documentation: Document the Linux Kernel CVE process
Date: Tue, 20 Feb 2024 11:07:38 +0100 [thread overview]
Message-ID: <2024022042-raisin-catalyst-2fae@gregkh> (raw)
In-Reply-To: <1a26d598-0063-447a-a79b-16315d2899ca@oracle.com>
On Tue, Feb 20, 2024 at 11:03:17AM +0100, Vegard Nossum wrote:
>
> On 17/02/2024 13:55, Greg Kroah-Hartman wrote:
> > +A list of all assigned CVEs for the Linux kernel can be found in the
> > +archives of the linux-cve mailing list, as seen on
> > +https://lore.kernel.org/linux-cve-announce/. To get notice of the
> > +assigned CVEs, please `subscribe
> > +<https://subspace.kernel.org/subscribing.html>`_ to that mailing list.
>
> Is the list open to discussion as well? (e.g. impact, analysis, etc.)
It's read-only, sorry.
> Or is this meant to be purely as a log of assignments?
Yes.
> What sort of content is (not) welcome? Should this be mentioned in the doc?
As it's not able to be posted to, not much to mention :)
If you wish to discuss something about it, follow the reply-to that is
set for a message there.
thanks,
greg k-h
prev parent reply other threads:[~2024-02-20 10:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 12:55 [PATCH v5] Documentation: Document the Linux Kernel CVE process Greg Kroah-Hartman
2024-02-20 10:03 ` Vegard Nossum
2024-02-20 10:07 ` Greg Kroah-Hartman [this message]
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=2024022042-raisin-catalyst-2fae@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=keescook@chromium.org \
--cc=konstantin@linuxfoundation.org \
--cc=krzk@kernel.org \
--cc=lee@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=lukas.bulwahn@gmail.com \
--cc=sashal@kernel.org \
--cc=security@kernel.org \
--cc=vegard.nossum@oracle.com \
--cc=workflows@vger.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 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.