linux-kernel - Re: [PATCH 5.17 000/772] 5.17.14-rc1 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]

Message-ID: <YqGqYd89cM+IB74e@kroah.com>
Date:   Thu, 9 Jun 2022 10:08:01 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Ron Economos <re@...z.net>
Cc:     linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
        linux@...ck-us.net, shuah@...nel.org, patches@...nelci.org,
        lkft-triage@...ts.linaro.org, pavel@...x.de, jonathanh@...dia.com,
        f.fainelli@...il.com, sudipm.mukherjee@...il.com,
        slade@...dewatkins.com
Subject: Re: [PATCH 5.17 000/772] 5.17.14-rc1 review

On Wed, Jun 08, 2022 at 04:23:04PM -0700, Ron Economos wrote:
> On 6/7/22 9:53 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.17.14 release.
> > There are 772 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, 09 Jun 2022 16:48:02 +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.17.14-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.17.y
> > and the diffstat can be found below.
> > 
> > thanks,
> > 
> > greg k-h
> > 
> Regression on RISC-V RV64 (HiFive Unmatched).
> 
> An Oops occurs when an NFS file system is mounted.
> 
> [   98.244615] FS-Cache: Loaded
> [   99.311566] NFS: Registering the id_resolver key type
> [   99.311621] Key type id_resolver registered
> [   99.311626] Key type id_legacy registered
> [   99.469053] Unable to handle kernel access to user memory without uaccess
> routines at virtual address 0000000000000000
> [   99.479039] Oops [#1]
> [   99.481246] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs
> lockd grace fscache netfs nvme_fabrics sunrpc binfmt_misc nls_iso8859_1
> da9063_onkey lm90 at24 uio_pdrv_genirq uio sch_fq_codel dm_multipath
> scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_devintf ipmi_msghandler drm
> backlight ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress
> raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx
> xor raid6_pq libcrc32c raid1 raid0 multipath linear rtc_da9063
> da9063_regulator mscc macsec nvme macb xhci_pci nvme_core xhci_pci_renesas
> i2c_ocores phylink
> [   99.532427] CPU: 2 PID: 889 Comm: mount.nfs Not tainted 5.17.13 #1
> [   99.538572] Hardware name: SiFive HiFive Unmatched A00 (DT)
> [   99.544133] epc : nfs_fattr_init+0x1e/0x48 [nfs]
> [   99.549059]  ra : _nfs41_proc_get_locations+0xb4/0x128 [nfsv4]
> [   99.555877] epc : ffffffff02332e76 ra : ffffffff023c076c sp :
> ffffffc894793960
> [   99.563084]  gp : ffffffff81a2ed00 tp : ffffffd896180000 t0 :
> ffffffd887720000
> [   99.570294]  t1 : ffffffff81a9c110 t2 : ffffffff81003c04 s0 :
> ffffffc894793970
> [   99.577503]  s1 : ffffffd887700000 a0 : 0000000000000000 a1 :
> ffffffd883de3d80
> [   99.584721]  a2 : ffffffd887700000 a3 : ffffffc704608a00 a4 :
> ffffffff0236aa28
> [   99.591924]  a5 : ffffffff02410cf8 a6 : ffffffff0240fc00 a7 :
> 0000000000000006
> [   99.599134]  s2 : ffffffd885df6000 s3 : ffffffc8947939c8 s4 :
> ffffffc894793998
> [   99.606343]  s5 : ffffffd881a9f000 s6 : ffffffc704608a00 s7 :
> ffffffff021c7db8
> [   99.613552]  s8 : ffffffff0240fd50 s9 : 0000000000000cc0 s10:
> 0000003fd7d2e260
> [   99.620762]  s11: 0000000000016700 t3 : 0000000000000020 t4 :
> 0000000000000001
> [   99.627971]  t5 : ffffffdbffdde088 t6 : ffffffdbffdde0a8
> [   99.633266] status: 0000000200000120 badaddr: 0000000000000000 cause:
> 000000000000000f
> [   99.641236] ---[ end trace 0000000000000000 ]---
> 
> Manually bisected to this commit:
> 
> NFSv4: Fix free of uninitialized nfs4_label on referral lookup.
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?h=linux-5.17.y&id=9a4a2efee41c4aca43988c43e16d44656f3c2132
> 

That's odd you see this here on 5.17, but NOT on 5.18 with the same
commit merged there.  I'll drop this from 5.17 and as this will probably
be the last (or next to last) 5.17 kernel release, not worry too much
about it.

thanks,

greg k-h