linux-kernel - Re: [PATCH 5.4 00/46] 5.4.2-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] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 4 Dec 2019 18:13:22 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Amol Grover <frextrite@...il.com>
Cc:     linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
        akpm@...ux-foundation.org, linux@...ck-us.net, shuah@...nel.org,
        patches@...nelci.org, ben.hutchings@...ethink.co.uk,
        lkft-triage@...ts.linaro.org, stable@...r.kernel.org
Subject: Re: [PATCH 5.4 00/46] 5.4.2-stable review

On Wed, Dec 04, 2019 at 06:53:18PM +0530, Amol Grover wrote:
> On Tue, Dec 03, 2019 at 11:35:20PM +0100, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.4.2 release.
> > There are 46 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.
> > 
> > Responses should be made by Thu, 05 Dec 2019 21:20:36 +0000.
> > Anything received after that time might be too late.
> > 
> > The whole patch series can be found in one patch at:
> > 	https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.4.2-rc1.gz
> > or in the git tree and branch at:
> > 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.4.y
> > and the diffstat can be found below.
> > 
> > thanks,
> > 
> > greg k-h
> > 
> > -------------
> > Pseudo-Shortlog of commits:
> > 
> > Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> >     Linux 5.4.2-rc1
> > 
> > Hans de Goede <hdegoede@...hat.com>
> >     platform/x86: hp-wmi: Fix ACPI errors caused by passing 0 as input size
> > 
> > Hans de Goede <hdegoede@...hat.com>
> >     platform/x86: hp-wmi: Fix ACPI errors caused by too small buffer
> > 
> > Candle Sun <candle.sun@...soc.com>
> >     HID: core: check whether Usage Page item is after Usage ID items
> > 
> > Herbert Xu <herbert@...dor.apana.org.au>
> >     crypto: talitos - Fix build error by selecting LIB_DES
> > 
> > Joel Stanley <joel@....id.au>
> >     Revert "jffs2: Fix possible null-pointer dereferences in jffs2_add_frag_to_fragtree()"
> > 
> > Theodore Ts'o <tytso@....edu>
> >     ext4: add more paranoia checking in ext4_expand_extra_isize handling
> > 
> > Heiner Kallweit <hkallweit1@...il.com>
> >     r8169: fix resume on cable plug-in
> > 
> > Heiner Kallweit <hkallweit1@...il.com>
> >     r8169: fix jumbo configuration for RTL8168evl
> > 
> > Thadeu Lima de Souza Cascardo <cascardo@...onical.com>
> >     selftests: pmtu: use -oneline for ip route list cache
> > 
> > John Rutherford <john.rutherford@...tech.com.au>
> >     tipc: fix link name length check
> > 
> > Jakub Kicinski <jakub.kicinski@...ronome.com>
> >     selftests: bpf: correct perror strings
> > 
> > Jakub Kicinski <jakub.kicinski@...ronome.com>
> >     selftests: bpf: test_sockmap: handle file creation failures gracefully
> > 
> > Jakub Kicinski <jakub.kicinski@...ronome.com>
> >     net/tls: use sg_next() to walk sg entries
> > 
> > Jakub Kicinski <jakub.kicinski@...ronome.com>
> >     net/tls: remove the dead inplace_crypto code
> > 
> > Jakub Kicinski <jakub.kicinski@...ronome.com>
> >     selftests/tls: add a test for fragmented messages
> > 
> 
> Hi,
> I'm not sure if this is relevant but I tested out the latest revision
> of tools/testing/selftests/net/tls (run as sudo) with 5.3.9, 5.3.13,
> and 5.4.1, and all of them resulted in Oops. I'm not sure that it
> happens only on my PC but the old version worked fine on all 3 kernels.
> 
> More information available in this thread:
> https://lore.kernel.org/stable/20191203171817.GA24581@workstation-portable/

Any specific commit cause this issue?  Should I drop one/any of these?

thanks,

greg k-h