linux-kernel - Re: [PATCH 4.4 00/22] 4.4.111-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]

Message-ID: <20180109092339.GA30075@kroah.com>
Date:   Tue, 9 Jan 2018 10:23:39 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Guenter Roeck <linux@...ck-us.net>
Cc:     linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
        akpm@...ux-foundation.org, shuahkh@....samsung.com,
        patches@...nelci.org, ben.hutchings@...ethink.co.uk,
        lkft-triage@...ts.linaro.org, stable@...r.kernel.org
Subject: Re: [PATCH 4.4 00/22] 4.4.111-stable review

On Mon, Jan 08, 2018 at 03:29:07PM -0800, Guenter Roeck wrote:
> On Mon, Jan 08, 2018 at 01:59:27PM +0100, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.4.111 release.
> > There are 22 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 Wed Jan 10 12:59:14 UTC 2018.
> > Anything received after that time might be too late.
> > 
> 
> x86:64:allnoconfig still fails to build.
> 
> To reproduce:
>   make ARCH=x86_64 allnoconfig
>   make ARCH=x86_64 arch/x86/entry/vdso/vma.o
> 
> arch/x86/entry/vdso/vma.c: In function ‘map_vdso’:
> arch/x86/entry/vdso/vma.c:175:9: error:
> 	implicit declaration of function ‘pvclock_pvti_cpu0_va’

Ok, forcing ARCH=x86_64 shows this now for me, strange it did not
without it, which worries me...

Anyway, a simple <include> line seems to have solved this, let me push
that out now, I couldn't take the full patch you referenced as that
causes build errors.

thanks,

greg k-h