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] [day] [month] [year] [list]
Date:   Wed, 19 Jan 2022 19:03:55 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Pavel Machek <pavel@...x.de>
Cc:     linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
        akpm@...ux-foundation.org, linux@...ck-us.net, shuah@...nel.org,
        patches@...nelci.org, lkft-triage@...ts.linaro.org,
        jonathanh@...dia.com, f.fainelli@...il.com, stable@...r.kernel.org
Subject: Re: 4.4 series end of line was Re: [PATCH 4.4 00/17] 4.4.297-rc1
 review

On Wed, Jan 19, 2022 at 02:49:43PM +0100, Pavel Machek wrote:
> Hi!
> 
> > > > This is the start of the stable review cycle for the 4.4.297 release.
> > > > There are 17 patches in this series, all will be posted as a response
> > > > to this one.  If anyone has any issues with these being applied, please
> > > > let me know.
> > > 
> > > 4.4.X series is scheduled for EOL next month. Do you have any
> > > estimates if it will be more like Feb 2 or Feb 27?
> > 
> > I would bet on Feb 1 :)
> 
> Hmm. That does not leave us too much time.
> 
> FAQ states:
> 
> # Why are some longterm versions supported longer than others?  The
> # "projected EOL" dates are not set in stone. Each new longterm kernel
> # usually starts with only a 2-year projected EOL that can be extended
> # further if there is enough interest from the industry at large to
> # help support it for a longer period of time.
> 
> Is there anyone else interested in continued 4.4.X maintainence?

I do not know of any companies or interested parties that is interested
in this.  The ones that rely on 4.4.x right now are going to be dropping
support for it this month, if they haven't already from what I know.

So I have no resources to maintain this anymore, sorry, and I STRONGLY
recommend that everyone else just move off of it as well.

> CIP project will need to maintain 4.4.X-cip and 4.4.X-cip-rt for some
> more years.

That is up to them to do, I wish them well, I think it is a loosing game
and one that is going to cost more money than they realize.  Remember,
it costs more money and time the older the kernel is to keep it "alive".
It is cheaper and easier to use more modern kernels.

> Do you think it would make sense to maintain 4.4.X-stable as well?

Not at all.  It is barely alive as-is.  If you _HAVE_ to maintain it, I
recommend only doing it on a very narrow way (i.e. limited functionality
and hardware support).  That's the only possible way you will be able to
do this.

good luck!

greg k-h

Powered by blists - more mailing lists