Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1617869

Re: [PATCH 02/24] Add the ability to lock down access to the running kernel image

From David Howells <dhowells@redhat.com>
Newsgroups linux.kernel
Subject Re: [PATCH 02/24] Add the ability to lock down access to the running kernel image
Date 2017-04-06 12:50 +0200
Message-ID <ttd9g-7m3-17@gated-at.bofh.it> (permalink)
References <ttbKa-6Cm-27@gated-at.bofh.it> <tsWL8-5w8-5@gated-at.bofh.it> <tsWL9-5w8-43@gated-at.bofh.it> <ttbKa-6Cm-27@gated-at.bofh.it>
Organization Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903

Show all headers | View raw

James Morris <jmorris@namei.org> wrote:

> > +static __read_mostly bool kernel_locked_down;
> 
> How about marking this __ro_after_init if ALLOW_LOCKDOWN_LIFT is not 
> configured?

I guess lock_kernel_down() would need to be __init also in that case.

Also, the implementation of lift_kernel_lockdown() should be conditional on
CONFIG_ALLOW_LOCKDOWN_LIFT.

David

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

[PATCH 02/24] Add the ability to lock down access to the running  kernel image David Howells <dhowells@redhat.com> - 2017-04-05 19:20 +0200
  Re: [PATCH 02/24] Add the ability to lock down access to the running  kernel image James Morris <jmorris@namei.org> - 2017-04-06 11:20 +0200
    Re: [PATCH 02/24] Add the ability to lock down access to the running kernel image David Howells <dhowells@redhat.com> - 2017-04-06 12:50 +0200
      Re: [PATCH 02/24] Add the ability to lock down access to the running  kernel image James Morris <jmorris@namei.org> - 2017-04-07 00:00 +0200

csiph-web