From: Christian Brauner <christian.brauner@ubuntu.com>
To: Stefan Berger <stefanb@linux.ibm.com>
Cc: linux-integrity@vger.kernel.org, zohar@linux.ibm.com,
serge@hallyn.com, containers@lists.linux.dev,
dmitry.kasatkin@gmail.com, ebiederm@xmission.com,
krzysztof.struczynski@huawei.com, roberto.sassu@huawei.com,
mpeters@redhat.com, lhinds@redhat.com, lsturman@redhat.com,
puiterwi@redhat.com, jejb@linux.ibm.com, jamjoom@us.ibm.com,
linux-kernel@vger.kernel.org, paul@paul-moore.com,
rgb@redhat.com, linux-security-module@vger.kernel.org,
jmorris@namei.org
Subject: Re: [PATCH v5 15/16] ima: Move dentries into ima_namespace
Date: Thu, 9 Dec 2021 15:37:49 +0100 [thread overview]
Message-ID: <20211209143749.wk4agkynfqdzftbl@wittgenstein> (raw)
In-Reply-To: <20211209143428.ip6bwry5hqtee5vy@wittgenstein>
On Thu, Dec 09, 2021 at 03:34:28PM +0100, Christian Brauner wrote:
> On Wed, Dec 08, 2021 at 05:18:17PM -0500, Stefan Berger wrote:
> > Move the dentries into the ima_namespace for reuse by virtualized
> > SecurityFS. Implement function freeing the dentries in order of
> > files and symlinks before directories.
> >
> > Signed-off-by: Stefan Berger <stefanb@linux.ibm.com>
> > ---
>
> This doesn't work as implemented, I think.
>
> What I would have preferred and what I tried to explain in the earlier
> review was:
> Keep the dentry stashing global since it is only needed for init_ima_ns.
> Then struct ima_namespace becomes way smaller and simpler.
> If you do that then it makes sense to remove the additional dget() in
> securityfs_create_dentry() for non-init_ima_ns.
> Then you can rely on auto-cleanup in .kill_sb() or on
> ima_securityfs_init() failure and you only need to call
> ima_fs_ns_free_dentries() if ns != init_ima_ns.
>
> IIuc, it seems you're currently doing one dput() too many since you're
> calling securityfs_remove() in the error path for non-init_ima_ns which
> relies on the previous increased dget() which we removed.
If you really want to move the dentry stashing into struct ima_namespace
even though it's really unnecessary then you may as well not care about
the auto-cleanup and keep that additional ima_fs_ns_free_dentries(ns)
call in .kill_sb(). But I really think not dragging dentry stashing into
struct ima_namespace is the correct way to go about this.
>
> > include/linux/ima.h | 13 ++++++
> > security/integrity/ima/ima_fs.c | 72 ++++++++++++++++++---------------
> > 2 files changed, 52 insertions(+), 33 deletions(-)
> >
> > diff --git a/include/linux/ima.h b/include/linux/ima.h
> > index 3aaf6e806db4..4dd64e318b15 100644
> > --- a/include/linux/ima.h
> > +++ b/include/linux/ima.h
> > @@ -220,6 +220,17 @@ struct ima_h_table {
> > struct hlist_head queue[IMA_MEASURE_HTABLE_SIZE];
> > };
> >
> > +enum {
> > + IMAFS_DENTRY_DIR = 0,
> > + IMAFS_DENTRY_SYMLINK,
> > + IMAFS_DENTRY_BINARY_RUNTIME_MEASUREMENTS,
> > + IMAFS_DENTRY_ASCII_RUNTIME_MEASUREMENTS,
> > + IMAFS_DENTRY_RUNTIME_MEASUREMENTS_COUNT,
> > + IMAFS_DENTRY_VIOLATIONS,
> > + IMAFS_DENTRY_IMA_POLICY,
> > + IMAFS_DENTRY_LAST
> > +};
> > +
> > struct ima_namespace {
> > struct kref kref;
> > struct user_namespace *user_ns;
> > @@ -266,6 +277,8 @@ struct ima_namespace {
> > struct mutex ima_write_mutex;
> > unsigned long ima_fs_flags;
> > int valid_policy;
> > +
> > + struct dentry *dentry[IMAFS_DENTRY_LAST];
> > };
> >
> > extern struct ima_namespace init_ima_ns;
> > diff --git a/security/integrity/ima/ima_fs.c b/security/integrity/ima/ima_fs.c
> > index a749a3e79304..3810d11fb463 100644
> > --- a/security/integrity/ima/ima_fs.c
> > +++ b/security/integrity/ima/ima_fs.c
> > @@ -360,14 +360,6 @@ static ssize_t ima_write_policy(struct file *file, const char __user *buf,
> > return result;
> > }
> >
> > -static struct dentry *ima_dir;
> > -static struct dentry *ima_symlink;
> > -static struct dentry *binary_runtime_measurements;
> > -static struct dentry *ascii_runtime_measurements;
> > -static struct dentry *runtime_measurements_count;
> > -static struct dentry *violations;
> > -static struct dentry *ima_policy;
> > -
> > enum ima_fs_flags {
> > IMA_FS_BUSY,
> > };
> > @@ -437,8 +429,8 @@ static int ima_release_policy(struct inode *inode, struct file *file)
> >
> > ima_update_policy(ns);
> > #if !defined(CONFIG_IMA_WRITE_POLICY) && !defined(CONFIG_IMA_READ_POLICY)
> > - securityfs_remove(ima_policy);
> > - ima_policy = NULL;
> > + securityfs_remove(ns->dentry[IMAFS_DENTRY_IMA_POLICY]);
> > + ns->dentry[IMAFS_DENTRY_IMA_POLICY] = NULL;
> > #elif defined(CONFIG_IMA_WRITE_POLICY)
> > clear_bit(IMA_FS_BUSY, &ns->ima_fs_flags);
> > #elif defined(CONFIG_IMA_READ_POLICY)
> > @@ -455,58 +447,72 @@ static const struct file_operations ima_measure_policy_ops = {
> > .llseek = generic_file_llseek,
> > };
> >
> > -int __init ima_fs_init(void)
> > +static void ima_fs_ns_free_dentries(struct ima_namespace *ns)
> > {
> > - ima_dir = securityfs_create_dir("ima", integrity_dir);
> > - if (IS_ERR(ima_dir))
> > + int i;
> > +
> > + for (i = IMAFS_DENTRY_LAST - 1; i >= 0; i--)
> > + securityfs_remove(ns->dentry[i]);
> > +
> > + memset(ns->dentry, 0, sizeof(ns->dentry));
> > +}
> > +
> > +static int __init ima_securityfs_init(struct user_namespace *user_ns)
> > +{
> > + struct ima_namespace *ns = user_ns->ima_ns;
> > + struct dentry *ima_dir;
> > +
> > + ns->dentry[IMAFS_DENTRY_DIR] = securityfs_create_dir("ima", integrity_dir);
> > + if (IS_ERR(ns->dentry[IMAFS_DENTRY_DIR]))
> > return -1;
> > + ima_dir = ns->dentry[IMAFS_DENTRY_DIR];
> >
> > - ima_symlink = securityfs_create_symlink("ima", NULL, "integrity/ima",
> > - NULL);
> > - if (IS_ERR(ima_symlink))
> > + ns->dentry[IMAFS_DENTRY_SYMLINK] =
> > + securityfs_create_symlink("ima", NULL, "integrity/ima", NULL);
> > + if (IS_ERR(ns->dentry[IMAFS_DENTRY_SYMLINK]))
> > goto out;
> >
> > - binary_runtime_measurements =
> > + ns->dentry[IMAFS_DENTRY_BINARY_RUNTIME_MEASUREMENTS] =
> > securityfs_create_file("binary_runtime_measurements",
> > S_IRUSR | S_IRGRP, ima_dir, NULL,
> > &ima_measurements_ops);
> > - if (IS_ERR(binary_runtime_measurements))
> > + if (IS_ERR(ns->dentry[IMAFS_DENTRY_BINARY_RUNTIME_MEASUREMENTS]))
> > goto out;
> >
> > - ascii_runtime_measurements =
> > + ns->dentry[IMAFS_DENTRY_ASCII_RUNTIME_MEASUREMENTS] =
> > securityfs_create_file("ascii_runtime_measurements",
> > S_IRUSR | S_IRGRP, ima_dir, NULL,
> > &ima_ascii_measurements_ops);
> > - if (IS_ERR(ascii_runtime_measurements))
> > + if (IS_ERR(ns->dentry[IMAFS_DENTRY_ASCII_RUNTIME_MEASUREMENTS]))
> > goto out;
> >
> > - runtime_measurements_count =
> > + ns->dentry[IMAFS_DENTRY_RUNTIME_MEASUREMENTS_COUNT] =
> > securityfs_create_file("runtime_measurements_count",
> > S_IRUSR | S_IRGRP, ima_dir, NULL,
> > &ima_measurements_count_ops);
> > - if (IS_ERR(runtime_measurements_count))
> > + if (IS_ERR(ns->dentry[IMAFS_DENTRY_RUNTIME_MEASUREMENTS_COUNT]))
> > goto out;
> >
> > - violations =
> > + ns->dentry[IMAFS_DENTRY_VIOLATIONS] =
> > securityfs_create_file("violations", S_IRUSR | S_IRGRP,
> > ima_dir, NULL, &ima_htable_violations_ops);
> > - if (IS_ERR(violations))
> > + if (IS_ERR(ns->dentry[IMAFS_DENTRY_VIOLATIONS]))
> > goto out;
> >
> > - ima_policy = securityfs_create_file("policy", POLICY_FILE_FLAGS,
> > + ns->dentry[IMAFS_DENTRY_IMA_POLICY] =
> > + securityfs_create_file("policy", POLICY_FILE_FLAGS,
> > ima_dir, NULL,
> > &ima_measure_policy_ops);
> > - if (IS_ERR(ima_policy))
> > + if (IS_ERR(ns->dentry[IMAFS_DENTRY_IMA_POLICY]))
> > goto out;
> >
> > return 0;
> > out:
> > - securityfs_remove(violations);
> > - securityfs_remove(runtime_measurements_count);
> > - securityfs_remove(ascii_runtime_measurements);
> > - securityfs_remove(binary_runtime_measurements);
> > - securityfs_remove(ima_symlink);
> > - securityfs_remove(ima_dir);
> > - securityfs_remove(ima_policy);
> > + ima_fs_ns_free_dentries(ns);
> > return -1;
> > }
> > +
> > +int __init ima_fs_init(void)
> > +{
> > + return ima_securityfs_init(&init_user_ns);
> > +}
> > --
> > 2.31.1
> >
> >
>
next prev parent reply other threads:[~2021-12-09 14:38 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 22:18 [PATCH v5 00/16] ima: Namespace IMA with audit support in IMA-ns Stefan Berger
2021-12-08 22:18 ` [PATCH v5 01/16] ima: Add IMA namespace support Stefan Berger
2021-12-08 22:18 ` [PATCH v5 02/16] ima: Define ns_status for storing namespaced iint data Stefan Berger
2021-12-08 22:18 ` [PATCH v5 03/16] ima: Namespace audit status flags Stefan Berger
2021-12-08 22:18 ` [PATCH v5 04/16] ima: Move delayed work queue and variables into ima_namespace Stefan Berger
2021-12-09 13:11 ` Christian Brauner
2021-12-09 15:09 ` Stefan Berger
2021-12-08 22:18 ` [PATCH v5 05/16] ima: Move IMA's keys queue related " Stefan Berger
2021-12-08 22:18 ` [PATCH v5 06/16] ima: Move policy " Stefan Berger
2021-12-08 22:18 ` [PATCH v5 07/16] ima: Move ima_htable " Stefan Berger
2021-12-08 22:18 ` [PATCH v5 08/16] ima: Move measurement list related variables " Stefan Berger
2021-12-08 22:18 ` [PATCH v5 09/16] ima: Only accept AUDIT rules for IMA non-init_ima_ns namespaces for now Stefan Berger
2021-12-08 22:18 ` [PATCH v5 10/16] ima: Implement hierarchical processing of file accesses Stefan Berger
2021-12-08 22:18 ` [PATCH v5 11/16] securityfs: Only use simple_pin_fs/simple_release_fs for init_user_ns Stefan Berger
2021-12-08 22:18 ` [PATCH v5 12/16] securityfs: Extend securityfs with namespacing support Stefan Berger
2021-12-08 22:18 ` [PATCH v5 13/16] ima: Move some IMA policy and filesystem related variables into ima_namespace Stefan Berger
2021-12-09 19:11 ` Christian Brauner
2021-12-09 20:42 ` Stefan Berger
2021-12-10 0:57 ` Stefan Berger
2021-12-10 11:32 ` Christian Brauner
2021-12-10 13:57 ` Stefan Berger
2021-12-10 14:21 ` James Bottomley
2021-12-11 9:50 ` Christian Brauner
2021-12-11 10:45 ` Christian Brauner
2021-12-13 15:33 ` Stefan Berger
2021-12-13 15:50 ` Christian Brauner
2021-12-13 16:03 ` Christian Brauner
2021-12-13 16:25 ` Stefan Berger
2021-12-13 16:37 ` Christian Brauner
2021-12-13 16:40 ` Christian Brauner
2021-12-10 20:08 ` Stefan Berger
2021-12-11 8:46 ` Christian Brauner
2021-12-08 22:18 ` [PATCH v5 14/16] ima: Use mac_admin_ns_capable() to check corresponding capability Stefan Berger
2021-12-09 7:22 ` Denis Semakin
2021-12-09 13:23 ` James Bottomley
2021-12-09 8:09 ` Denis Semakin
2021-12-11 15:02 ` Serge E. Hallyn
2021-12-11 15:38 ` Stefan Berger
2021-12-11 16:00 ` James Bottomley
2021-12-08 22:18 ` [PATCH v5 15/16] ima: Move dentries into ima_namespace Stefan Berger
2021-12-09 14:34 ` Christian Brauner
2021-12-09 14:37 ` Christian Brauner [this message]
2021-12-09 14:41 ` Christian Brauner
2021-12-09 15:00 ` Stefan Berger
2021-12-09 15:47 ` Christian Brauner
2021-12-09 15:30 ` James Bottomley
2021-12-09 19:38 ` James Bottomley
2021-12-09 20:13 ` Stefan Berger
2021-12-10 11:49 ` Christian Brauner
2021-12-10 12:09 ` Mimi Zohar
2021-12-10 12:40 ` Stefan Berger
2021-12-10 13:02 ` Mimi Zohar
2021-12-10 14:17 ` Stefan Berger
2021-12-10 14:26 ` James Bottomley
2021-12-10 15:26 ` Mimi Zohar
2021-12-10 15:32 ` Stefan Berger
2021-12-10 15:48 ` Mimi Zohar
2021-12-10 16:40 ` Stefan Berger
2021-12-10 12:40 ` James Bottomley
2021-12-10 12:54 ` Mimi Zohar
2021-12-12 14:13 ` James Bottomley
2021-12-13 11:25 ` Christian Brauner
2021-12-08 22:18 ` [PATCH v5 16/16] ima: Setup securityfs for IMA namespace Stefan Berger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211209143749.wk4agkynfqdzftbl@wittgenstein \
--to=christian.brauner@ubuntu.com \
--cc=containers@lists.linux.dev \
--cc=dmitry.kasatkin@gmail.com \
--cc=ebiederm@xmission.com \
--cc=jamjoom@us.ibm.com \
--cc=jejb@linux.ibm.com \
--cc=jmorris@namei.org \
--cc=krzysztof.struczynski@huawei.com \
--cc=lhinds@redhat.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=lsturman@redhat.com \
--cc=mpeters@redhat.com \
--cc=paul@paul-moore.com \
--cc=puiterwi@redhat.com \
--cc=rgb@redhat.com \
--cc=roberto.sassu@huawei.com \
--cc=serge@hallyn.com \
--cc=stefanb@linux.ibm.com \
--cc=zohar@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).