linux-kernel - Re: [PATCH 4.14 00/54] 4.14.23-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:   Mon, 26 Feb 2018 13:45:19 -0800
From:   Tony Lindgren <tony@...mide.com>
To:     Guenter Roeck <linux@...ck-us.net>
Cc:     Dan Murphy <dmurphy@...com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        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.14 00/54] 4.14.23-stable review

* Guenter Roeck <linux@...ck-us.net> [180226 21:20]:
> On Mon, Feb 26, 2018 at 02:58:24PM -0600, Dan Murphy wrote:
> > Tony L/Greg
> > 
> > On 02/26/2018 02:21 PM, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 4.14.23 release.
> > > There are 54 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 Feb 28 20:21:22 UTC 2018.
> > > Anything received after that time might be too late.
> > > 
> > 
> > We have a build issue on 4.14.22 and can be re-created with this rc as well.
> > 
> > arch/arm/mach-omap2/omap-secure.o: In function `omap3_save_secure_ram':
> > omap-secure.c:(.text+0xe4): undefined reference to `save_secure_ram_context'
> > make: *** [vmlinux] Error 1
> > 
> > The issue was introduced with the back port of
> > 
> > b59a1da647f163d0bf035f823a908b45c357643a ARM: OMAP2+: Fix SRAM virt to phys translation for save_secure_ram_context
> > 
> Looks like you may have CONFIG_PM disabled, is that correct ?
> Is there a default configuration that we can use to reproduce
> the problem ?

It should be fixed with this commit in mainline kernel:

863204cfdae9 ("ARM: omap2: hide omap3_save_secure_ram on non-OMAP3 builds")

Regards,

Tony