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 11:37:45 +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 10:31:49AM +0000, Jari Ruusu wrote:
> On Friday, February 19, 2021 10:22 AM, Greg Kroah-Hartman <gregkh@...uxfoundation.org> wrote:
> > 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.
> 
> But in-tree iwlwifi worked fine on 4.9.y and 4.14.y , and then got broken
> in later 4.14.y versions.

Did you report that breakage to us and the developers of the driver?
Sounds like a regression that people would love to hear about and get
fixed.

> I tried later versions of 4.19.y in an attempt to
> fix the breakage. Basically you are are saying that I should have NOT
> attempted to upgrage 4.9.y -> 4.14.y -> 4.19.y

Without anyone reporting a problem, how can anyone know to fix it?

thanks,

greg k-h