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:   Thu, 18 Feb 2021 13:51:31 +0100
From:   Pavel Machek <pavel@...x.de>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Scott Branden <scott.branden@...adcom.com>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        LKML <linux-kernel@...r.kernel.org>,
        BCM Kernel Feedback <bcm-kernel-feedback-list@...adcom.com>
Subject: Re: 5.10 LTS Kernel: 2 or 6 years?

Hi!

> Why would you backport new features to an old kernel?  That's not what
> they are there for.

For CIP project, this is one of advantages for "supported" boards, as
we'll backport patches improving their support as long as those
patches are mainline.

> > If the CIP project has committed to 10 years you would think they would be in contact
> > with you to add their support to the 5.10 LTS effort.
> 
> They are doing testing right now, see the announcements where they test
> each stable -rc release.  But they have not talked to me about 5.10
> yet, Their model is that they will, somehow in a way that is yet to be
> determined, take over maintaining these releases _after_ I drop them.
> But they are only going to do so for a very specific hardware platform
> or two, so anyone using anything other than their specific boards, is
> going to be out of luck.

I'd say this is a bit inaccurate :-). We care about different boards
at armv7, armv8 and x86-64 architectures, which actually means we care
about quite big part of the kernel already. Rough estimate is that 50%
of patches in stable touch our configurations, I could collect better
statistics.

As you said, I'm not sure everything is fully determined at this
point, but... we'll certainly try to support community effort for 4.4,
4.19 and 5.10 maintainance for as long as possible.

It is well possible that we'll continue to maintain even
configurations we can't test (we don't have s390 to test on) on
best-effort basis (to help community and because applying a patch may
be easier than determining if someone in CIP community depends on it).

> Which makes sense, scoping support like this to those that actually care
> about a specific hardware platform is much easier than the work that I
> and Sasha do in support it for all platforms.  So if you are interested
> in 10 years, please work with CIP to get your platform into that list.

And yes, this is very good suggestion.

Best regards,
								Pavel
PS: Again, I'm speaking for myself.
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

Download attachment "signature.asc" of type "application/pgp-signature" (196 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ