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:   Sat, 20 Feb 2021 18:06:00 +0100
From:   Willy Tarreau <w@....eu>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Jari Ruusu <jariruusu@...tonmail.com>,
        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 Sat, Feb 20, 2021 at 05:05:14PM +0100, Greg Kroah-Hartman wrote:
> On Sat, Feb 20, 2021 at 01:29:21PM +0000, Jari Ruusu wrote:
> > On Friday, February 19, 2021 5:23 PM, Jari Ruusu <jariruusu@...tonmail.com> wrote:
> > > My contribution here is trying to point you guys to right direction.
> > 
> > I have been able to narrow the beginning of the problem to these kernels:
> > 4.14.188 ... 4.14.202
> > 
> > Same "fix" that went info 4.14.y is also bugging 4.19.y kernels.
> 
> Great, any chance you can narrow this down to the commit itself?

What is strnage is that there was no iwlwifi driver change in this
interval. Only iwlegacy (don't know if this one was used instead).

Note, my laptop uses iwlwifi as well. I've met random issues with it
a year ago when I started to use wifi, such as wifi randomly freezing
during audio meetings, and automatically fixing itself after 1 minute.
I also found that a down-up cycle on the interface would fix it. It
happened less than once a day so it was not easy to diagnose, and given
how crappy all wifi chips are, I naturally attributed this to the
hardware. But since I upgraded to 5.4 months ago, I don't remember having
met that issue anymore, so it was likely related to the driver. All I can
say is that 4.19.68 was exhibiting this issue. I can't say for older ones
because I didn't use wifi before.

Just my two cents,
Willy