Messages in this thread | | | Date | Wed, 16 Feb 2022 15:25:49 -0500 | Subject | Re: [PATCH v10 05/27] ima: Define ima_namespace struct and start moving variables into it | From | Stefan Berger <> |
| |
On 2/16/22 09:41, Mimi Zohar wrote: > On Tue, 2022-02-01 at 15:37 -0500, Stefan Berger wrote: >> Define the ima_namespace structure and the ima_namespace variable >> init_ima_ns for the host's IMA namespace. Implement basic functions for >> namespacing support. > Implement the basic functions - ima_ns_init() and ima_init_namespace() > - for namespacing support. > >> Move variables related to the IMA policy into the ima_namespace. This way >> the IMA policy of an IMA namespace can be set and displayed using a >> front-end like securityfs. >> Implement ima_ns_from_file() to get the IMA namespace via the user >> namespace of the securityfs superblock that a file belongs to. > Currently, ima_ns_from_file() doesn't exist in this patch. Ah, left-over from previous version. Remove. > >> To get the current ima_namespace use &init_ima_ns when a function >> that is related to a policy rule is called. > In preparation for IMA namespacing, update the existing functions to > pass the ima_namespace struct. For now, ... > >> >> Signed-off-by: Stefan Berger <stefanb@linux.ibm.com> >> Acked-by: Christian Brauner <brauner@kernel.org> > After addressing the one inline comment, Done. > Reviewed-by: Mimi Zohar <zohar@linux.ibm.com>
Thanks.
| |