From: Aristeu Rozanski <aris@redhat.com>
To: Wang Weiyang <wangweiyang2@huawei.com>
Cc: paul@paul-moore.com, jmorris@namei.org, serge@hallyn.com,
serge.hallyn@canonical.com, akpm@linux-foundation.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] device_cgroup: Roll back to original exceptions after copy failure
Date: Mon, 7 Nov 2022 13:56:30 -0500 [thread overview]
Message-ID: <20221107185630.dwcffktczjrayagn@redhat.com> (raw)
In-Reply-To: <20221025113101.41132-1-wangweiyang2@huawei.com>
On Tue, Oct 25, 2022 at 07:31:01PM +0800, Wang Weiyang wrote:
> When add the 'a *:* rwm' entry to devcgroup A's whitelist, at first A's
> exceptions will be cleaned and A's behavior is changed to
> DEVCG_DEFAULT_ALLOW. Then parent's exceptions will be copyed to A's
> whitelist. If copy failure occurs, just return leaving A to grant
> permissions to all devices. And A may grant more permissions than
> parent.
>
> Backup A's whitelist and recover original exceptions after copy
> failure.
>
> Fixes: 4cef7299b478 ("device_cgroup: add proper checking when changing default behavior")
> Signed-off-by: Wang Weiyang <wangweiyang2@huawei.com>
> ---
> security/device_cgroup.c | 33 +++++++++++++++++++++++++++++----
> 1 file changed, 29 insertions(+), 4 deletions(-)
>
> diff --git a/security/device_cgroup.c b/security/device_cgroup.c
> index a9f8c63a96d1..bef2b9285fb3 100644
> --- a/security/device_cgroup.c
> +++ b/security/device_cgroup.c
> @@ -82,6 +82,17 @@ static int dev_exceptions_copy(struct list_head *dest, struct list_head *orig)
> return -ENOMEM;
> }
>
> +static void dev_exceptions_move(struct list_head *dest, struct list_head *orig)
> +{
> + struct dev_exception_item *ex, *tmp;
> +
> + lockdep_assert_held(&devcgroup_mutex);
> +
> + list_for_each_entry_safe(ex, tmp, orig, list) {
> + list_move_tail(&ex->list, dest);
> + }
> +}
> +
> /*
> * called under devcgroup_mutex
> */
> @@ -604,11 +615,13 @@ static int devcgroup_update_access(struct dev_cgroup *devcgroup,
> int count, rc = 0;
> struct dev_exception_item ex;
> struct dev_cgroup *parent = css_to_devcgroup(devcgroup->css.parent);
> + struct dev_cgroup tmp_devcgrp;
>
> if (!capable(CAP_SYS_ADMIN))
> return -EPERM;
>
> memset(&ex, 0, sizeof(ex));
> + memset(&tmp_devcgrp, 0, sizeof(tmp_devcgrp));
> b = buffer;
>
> switch (*b) {
> @@ -620,15 +633,27 @@ static int devcgroup_update_access(struct dev_cgroup *devcgroup,
>
> if (!may_allow_all(parent))
> return -EPERM;
> - dev_exception_clean(devcgroup);
> - devcgroup->behavior = DEVCG_DEFAULT_ALLOW;
> - if (!parent)
> + if (!parent) {
> + devcgroup->behavior = DEVCG_DEFAULT_ALLOW;
> + dev_exception_clean(devcgroup);
> break;
> + }
>
> + INIT_LIST_HEAD(&tmp_devcgrp.exceptions);
> + rc = dev_exceptions_copy(&tmp_devcgrp.exceptions,
> + &devcgroup->exceptions);
> + if (rc)
> + return rc;
> + dev_exception_clean(devcgroup);
> rc = dev_exceptions_copy(&devcgroup->exceptions,
> &parent->exceptions);
> - if (rc)
> + if (rc) {
> + dev_exceptions_move(&devcgroup->exceptions,
> + &tmp_devcgrp.exceptions);
> return rc;
> + }
> + devcgroup->behavior = DEVCG_DEFAULT_ALLOW;
> + dev_exception_clean(&tmp_devcgrp);
> break;
> case DEVCG_DENY:
> if (css_has_online_children(&devcgroup->css))
Reviewed-by: Aristeu Rozanski <aris@redhat.com>
--
Aristeu
next prev parent reply other threads:[~2022-11-07 18:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 11:31 [PATCH] device_cgroup: Roll back to original exceptions after copy failure Wang Weiyang
2022-10-28 11:19 ` Paul Moore
2022-11-15 3:54 ` wangweiyang
2022-11-15 20:55 ` Paul Moore
2022-11-07 18:56 ` Aristeu Rozanski [this message]
2022-11-16 23:33 ` Paul Moore
2022-11-17 7:27 ` wangweiyang
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=20221107185630.dwcffktczjrayagn@redhat.com \
--to=aris@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=serge.hallyn@canonical.com \
--cc=serge@hallyn.com \
--cc=wangweiyang2@huawei.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).