linux-kernel - Re: [PATCH 5.4 00/37] 5.4.5-stable review

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] [day] [month] [year] [list]

Message-ID: <20191219084513.GB1027830@kroah.com>
Date:   Thu, 19 Dec 2019 09:45:13 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        "torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Guenter Roeck <linux@...ck-us.net>,
        Shuah Khan <shuah@...nel.org>, patches@...nelci.org,
        Ben Hutchings <ben.hutchings@...ethink.co.uk>,
        lkft-triage@...ts.linaro.org, stable <stable@...r.kernel.org>,
        Yoshiki Komachi <komachi.yoshiki@...il.com>
Subject: Re: [PATCH 5.4 00/37] 5.4.5-stable review

On Wed, Dec 18, 2019 at 10:02:53PM +0100, Geert Uytterhoeven wrote:
> Hi Greg,
> 
> On Tue, Dec 17, 2019 at 9:10 PM Greg Kroah-Hartman
> <gregkh@...uxfoundation.org> wrote:
> > This is the start of the stable review cycle for the 5.4.5 release.
> > There are 37 patches in this series, all will be posted as a response
> > to this one.  If anyone has any issues with these being applied, please
> > let me know.
> 
> > Yoshiki Komachi <komachi.yoshiki@...il.com>
> >     cls_flower: Fix the behavior using port ranges with hw-offload
> 
> Given I bisected a WARNING to this commit, it's probably safer to not
> backport it to stable yet.
> 
> So far no response to my report
> https://lore.kernel.org/lkml/CAMuHMdXKNMgAQHAE4f-0=srAZtDNUPB6Hmdm277XTgukrtiJ4Q@mail.gmail.com/
> 
> Given it's networking, it could be an endian issue, manifesting on big
> endian systems only.

If this gets reverted in Linus's tree, let me know the commit and I'll
do the same in the stable trees.

thanks,

greg k-h