linux-kernel - Re: 2.6.34.x longterm stable status

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 21 Jan 2014 10:58:48 -0500
From:	Paul Gortmaker <paul.gortmaker@...driver.com>
To:	"H. Peter Anvin" <hpa@...or.com>,
	Aaro Koskinen <aaro.koskinen@....fi>
CC:	<linux-kernel@...r.kernel.org>, <konstantin@...uxfoundation.org>
Subject: Re: 2.6.34.x longterm stable status

On 14-01-21 10:10 AM, H. Peter Anvin wrote:
> On 08/07/2013 09:07 PM, Paul Gortmaker wrote:
>>>
>>> - Shouldn't the EOL status be mentioned in the www.kernel.org front page?
>>
>> It will be marked EOL at kernel.org when it is EOL.  Those that care
>> about it being EOL would have seen the message about it becoming EOL in
>> the previous 2.6.34.x release annoucement.
>>
> 
> Maybe it is time to check in on this?

Yes, Konstantin just ping'd me recently on this, and the final update will
be out for review within a week;  with a focus on just clear CVE like
fixes and hence a relatively smaller queue size (i.e. nothing like 200
patches etc.)

If you think it best to mark it EOL in advance of that last release,
rather than waiting for it to appear, I don't see that as a problem.

Paul.
--

> 
> I just noticed that this is now over a year since the last 2.6.34
> release, which lags the last 2.6.32 release by about five months.  I am
> asking because someone just queried me privately about the status of
> 2.6.34.  I'm worrying if people think that security patches are still
> being backported if in fact they aren't.
> 
> 	-hpa
> 
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/