Received-SPF: pass (google.com: domain of linux-kernel+bounces-65578-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) client-ip=2604:1380:40f1:3f00::1;
Message-ID: <768355d0-df1e-48dd-b7fd-9ed34f7a4b7c@infradead.org>
Date: Wed, 14 Feb 2024 08:44:17 -0800
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PATCH] Documentation: Document the Linux Kernel CVE process
Content-Language: en-US
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: corbet@lwn.net, workflows@vger.kernel.org, linux-doc@vger.kernel.org,
 linux-kernel@vger.kernel.org, security@kernel.org,
 Sasha Levin <sashal@kernel.org>, Lee Jones <lee@kernel.org>
References: <2024021314-unwelcome-shrill-690e@gregkh>
 <60d67476-5c56-4fa4-93cf-1eb8f5aa5953@infradead.org>
 <2024021450-giddy-garland-e499@gregkh>
From: Randy Dunlap <rdunlap@infradead.org>
In-Reply-To: <2024021450-giddy-garland-e499@gregkh>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


On 2/13/24 23:15, Greg Kroah-Hartman wrote:
> On Tue, Feb 13, 2024 at 11:56:42AM -0800, Randy Dunlap wrote:
>>> +As part of the normal stable release process, kernel changes that are
>>> +potentially security issues are identified by the developers responsible
>>> +for CVE number assignments and have CVE numbers automatically assigned
>>> +to them.  These assignments are published on the linux-cve mailing list
>>
>>                                                     linux-cve-announce mailing list
> 
> Ah, good catch, you can see the "old" name for the list here, this is
> due to this document being an older version, a symptom of "write it on
> my workstation, sync to laptop, travel with laptop for 3+ weeks and make
> changes based on meetings with CVE and others and then forget to sync
> from laptop when arriving home".
> 
> Ugh :(
> 
> Thanks so much for the grammer fixes, they are much appreciated.  I'll
> apply them and send out the latest version in a bit.
> 
>>> +No CVEs will be assigned for unfixed security issues in the Linux
>>> +kernel, assignment will only happen after a fix is available as it can
>>
>>    kernel;
>>
>>> +be properly tracked that way by the git commit id of the original fix.
> 
> One of my goals in life is to never use a ';' in a sentence, and after
> writing 2 books without them, I thought I achieve that pretty well as I
> never seem to remember when they are to be used or not.  But I'll trust
> you on this and use it here.

For some reason kernel documentation has a plethora of run-on sentences. :(

Guess we need doclint.

-- 
#Randy