linux-kernel - Re: 5.10 LTS Kernel: 2 or 6 years?

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:   Fri, 19 Feb 2021 09:22:17 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Jari Ruusu <jariruusu@...tonmail.com>
Cc:     Willy Tarreau <w@....eu>,
        Jari Ruusu <jariruusu@...rs.sourceforge.net>,
        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?

On Fri, Feb 19, 2021 at 07:10:35AM +0000, Jari Ruusu wrote:
> On Thursday, February 18, 2021 7:44 PM, Greg Kroah-Hartman <gregkh@...uxfoundation.org> wrote:
> > > It was the other way around. Fine working in-tree driver got
> > > broken by backported "fixes". I did mention bit-rot.
> >
> > It did? Please let us stable maintainers know about, we will always
> > gladly revert problems patches. What commits caused the problem?
> 
> I don't have a list of commits for you. It took me long time to
> figure out that it was iwlwifi that was causing those problems.
> 
> In-tree iwlwifi on 4.19.y kernels needs professional quality
> locking audit and backporting of necessary fixes from upstream
> Intel out-of-tree version.

That's not the goal of stable kernel releases/trees.  If the driver
version that is in 4.19.y does not work for you on release 4.19.0, odds
of that "changing" in later stable releases is slim to none.

Especially without any specific bug reports or emails to the developers
to tell them what is broken and not working for you.

If however, you wish to stick with an out-of-tree driver, wonderful,
that's your choice.  But don't claim that somehow the stable kernel
process is broken because of that, as it has nothing to do with this
type of thing.

Best of luck!

greg k-h