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]
Message-ID: <YC6zq3u2jciI2gyZ@kroah.com>
Date:   Thu, 18 Feb 2021 19:36:27 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Willy Tarreau <w@....eu>
Cc:     Florian Fainelli <f.fainelli@...il.com>,
        Sasha Levin <sashal@...nel.org>,
        BCM Kernel Feedback <bcm-kernel-feedback-list@...adcom.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        Scott Branden <scott.branden@...adcom.com>
Subject: Re: 5.10 LTS Kernel: 2 or 6 years?

On Thu, Feb 18, 2021 at 07:20:50PM +0100, Willy Tarreau wrote:
> On Thu, Feb 18, 2021 at 06:53:56PM +0100, Greg Kroah-Hartman wrote:
> > On Thu, Feb 18, 2021 at 09:21:13AM -0800, Florian Fainelli wrote:
> > > As a company, we are most likely shooting ourselves in the foot by not
> > > having a point of coordination with the Linux Foundation and key people
> > > like you, Greg and other participants in the stable kernel.
> > 
> > What does the LF have to do with this?
> > 
> > We are here, on the mailing lists, working with everyone.  Just test the
> > -rc releases we make and let us know if they work or not for you, it's
> > not a lot of "coordination" needed at all.
> > 
> > Otherwise, if no one is saying that they are going to need these for 6
> > years and are willing to use it in their project (i.e. and test it),
> > there's no need for us to maintain it for that long, right?
> 
> Greg, please remember I expressed I really need them for slightly more than
> 3 years (say 3.5-4) :-) I'm fine with helping a bit more as time permits if
> this saves me from having to take over these kernels after you, like in the
> past, but I cannot engage on the regularity of my availability.

Ok, great!

That's one person/company saying they can help out (along with what CIP
has been stating.)

What about others?  Broadcom started this conversation, odd that they
don't seem to want to help out :)

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ