[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <32418.1510095411@warthog.procyon.org.uk>
Date: Tue, 07 Nov 2017 22:56:51 +0000
From: David Howells <dhowells@...hat.com>
To: Thiago Jung Bauermann <bauerman@...ux.vnet.ibm.com>
Cc: dhowells@...hat.com, linux-security-module@...r.kernel.org,
gnomes@...rguk.ukuu.org.uk, linux-efi@...r.kernel.org,
matthew.garrett@...ula.com, gregkh@...uxfoundation.org,
linux-kernel@...r.kernel.org, jforbes@...hat.com
Subject: Re: [PATCH 02/27] Add a SysRq option to lift kernel lockdown
Thiago Jung Bauermann <bauerman@...ux.vnet.ibm.com> wrote:
> On non-x86 platforms (tested on powerpc) this fails to build with:
>
> security/lock_down.c: In function ‘lockdown_lift_sysrq’:
> security/lock_down.c:100:40: error: ‘LOCKDOWN_LIFT_KEY’ undeclared (first use in this function)
> lockdown_lift_sysrq_op.help_msg[5] = LOCKDOWN_LIFT_KEY;
> ^~~~~~~~~~~~~~~~~
> security/lock_down.c:100:40: note: each undeclared identifier is reported only once for each function it appears in
I've added an arch dependency in the Kconfig file in my local branch. I'll
try to get it pushed again.
David
Powered by blists - more mailing lists