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:   Thu, 4 Nov 2021 17:52:42 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Guenter Roeck <linux@...ck-us.net>
Cc:     Daniel Díaz <daniel.diaz@...aro.org>,
        linux-kernel@...r.kernel.org, shuah@...nel.org,
        f.fainelli@...il.com, patches@...nelci.org,
        lkft-triage@...ts.linaro.org, jonathanh@...dia.com,
        stable@...r.kernel.org, pavel@...x.de, akpm@...ux-foundation.org,
        torvalds@...ux-foundation.org
Subject: Re: [PATCH 5.10 00/16] 5.10.78-rc1 review

On Thu, Nov 04, 2021 at 09:46:49AM -0700, Guenter Roeck wrote:
> On 11/4/21 9:20 AM, Greg Kroah-Hartman wrote:
> > On Thu, Nov 04, 2021 at 09:53:57AM -0600, Daniel Díaz wrote:
> > > Hello!
> > > 
> > > On 11/4/21 8:12 AM, Greg Kroah-Hartman wrote:
> > > > This is the start of the stable review cycle for the 5.10.78 release.
> > > > There are 16 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 Sat, 06 Nov 2021 14:11:51 +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.10.78-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.10.y
> > > > and the diffstat can be found below.
> > > > 
> > > > thanks,
> > > > 
> > > > greg k-h
> > > 
> > > Regressions detected.
> > > 
> > > Build failures on all architectures and all toolchains (GCC 8, 9, 10, 11; Clang 10, 11, 12, 13, nightly):
> > > - arc
> > > - arm (32-bits)
> > > - arm (64-bits)
> > > - i386
> > > - mips
> > > - parisc
> > > - ppc
> > > - riscv
> > > - s390
> > > - sh
> > > - sparc
> > > - x86
> > > 
> > > Failures look like this:
> > > 
> > >    In file included from /builds/linux/include/linux/kernel.h:11,
> > >                     from /builds/linux/include/linux/list.h:9,
> > >                     from /builds/linux/include/linux/smp.h:12,
> > >                     from /builds/linux/include/linux/kernel_stat.h:5,
> > >                     from /builds/linux/mm/memory.c:42:
> > >    /builds/linux/mm/memory.c: In function 'finish_fault':
> > >    /builds/linux/mm/memory.c:3929:15: error: implicit declaration of function 'PageHasHWPoisoned'; did you mean 'PageHWPoison'? [-Werror=implicit-function-declaration]
> > >     3929 |  if (unlikely(PageHasHWPoisoned(page)))
> > >          |               ^~~~~~~~~~~~~~~~~
> > >    /builds/linux/include/linux/compiler.h:78:42: note: in definition of macro 'unlikely'
> > >       78 | # define unlikely(x) __builtin_expect(!!(x), 0)
> > >          |                                          ^
> > >    cc1: some warnings being treated as errors
> > > 
> > > and this:
> > > 
> > >    /builds/linux/mm/memory.c:3929:15: error: implicit declaration of function 'PageHasHWPoisoned' [-Werror,-Wimplicit-function-declaration]
> > >            if (unlikely(PageHasHWPoisoned(page)))
> > >                         ^
> > > 
> > >    /builds/linux/mm/page_alloc.c:1237:4: error: implicit declaration of function 'ClearPageHasHWPoisoned' [-Werror,-Wimplicit-function-declaration]
> > >                            ClearPageHasHWPoisoned(page);
> > >                            ^
> > >    /builds/linux/mm/page_alloc.c:1237:4: note: did you mean 'ClearPageHWPoison'?
> > > 
> > 
> > What configuration?  This builds for me on x86 here on allmodconfig.
> > 
> 
> defconfig, and anything with CONFIG_MEMORY_FAILURE=n or CONFIG_TRANSPARENT_HUGEPAGE=n.
> Fix needs upstream commit e66435936756d (presumably, I did not check).

Odd, no, I don't think that commit will help.

I'll go drop the offending commit now and push out a -rc2.

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ