From: Aristeu Rozanski <aris@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Tejun Heo <tj@kernel.org>,
Serge Hallyn <serge.hallyn@canonical.com>,
cgroups@vger.kernel.org
Subject: [PATCH 4/5] device_cgroup: make may_access() stronger
Date: Tue, 27 Nov 2012 14:35:05 -0500 [thread overview]
Message-ID: <20121127193502.817704289@napanee.usersys.redhat.com> (raw)
In-Reply-To: <20121127193501.255267751@napanee.usersys.redhat.com>
[-- Attachment #1: strengthen-may_access.patch --]
[-- Type: text/plain, Size: 2608 bytes --]
In order to revalidate local exceptions for the hierarchy change propagation,
make may_access() stronger.
Cc: Tejun Heo <tj@kernel.org>
Cc: Serge Hallyn <serge.hallyn@canonical.com>
Signed-off-by: Aristeu Rozanski <aris@redhat.com>
---
security/device_cgroup.c | 36 ++++++++++++++++++++++++------------
1 file changed, 24 insertions(+), 12 deletions(-)
Index: github/security/device_cgroup.c
===================================================================
--- github.orig/security/device_cgroup.c 2012-11-26 17:28:04.399150628 -0500
+++ github/security/device_cgroup.c 2012-11-27 11:57:55.932996663 -0500
@@ -352,13 +352,14 @@
* won't have more privileges than its parent or to
* verify if a certain access is allowed.
* @dev_cgroup: dev cgroup to be tested against
+ * @behavior: behavior of the exception
* @refex: new exception
*/
static int may_access(struct dev_cgroup *dev_cgroup,
struct dev_exception_item *refex)
{
struct dev_exception_item *ex;
- bool match = false;
+ int match = 0;
rcu_lockdep_assert(rcu_read_lock_held() ||
lockdep_is_held(&devcgroup_mutex),
@@ -375,22 +376,33 @@
continue;
if (refex->access & (~ex->access))
continue;
- match = true;
+ match = 1;
break;
}
/*
- * In two cases we'll consider this new exception valid:
- * - the dev cgroup has its default policy to allow + exception list:
- * the new exception should *not* match any of the exceptions
- * (behavior == DEVCG_DEFAULT_ALLOW, !match)
- * - the dev cgroup has its default policy to deny + exception list:
- * the new exception *should* match the exceptions
- * (behavior == DEVCG_DEFAULT_DENY, match)
+ * The only three possibilities are:
+ * devcg->behavior == ALLOW, rule behavior == ALLOW
+ * devcg->behavior == ALLOW, rule behavior == DENY
+ * devcg->behavior == DENY, rule behavior == DENY
+ * the remaining
+ * devcg->behavior == DENY, rule behavior == ALLOW
+ * won't be possible by hierarchy
+ *
+ * Since we want to simplify the code, here're the possibilites to
+ * make easier to understand:
+ *
+ * devcg behavior rule behavior match result
+ * allow allow 1 0
+ * allow allow 0 1
+ * allow deny 1 0
+ * allow deny 0 1
+ * deny deny 1 1
+ * deny deny 0 0
*/
- if ((dev_cgroup->behavior == DEVCG_DEFAULT_DENY) == match)
- return 1;
- return 0;
+ if (dev_cgroup->behavior == DEVCG_DEFAULT_ALLOW)
+ return !match;
+ return match;
}
/*
next prev parent reply other threads:[~2012-11-27 20:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 19:35 [PATCH 0/5] devcg: introduce proper hierarchy support Aristeu Rozanski
2012-11-27 19:35 ` [PATCH 1/5] device_cgroup: fix locking in devcgroup_destroy() Aristeu Rozanski
2012-11-29 19:06 ` Serge E. Hallyn
2012-12-03 17:29 ` Tejun Heo
2012-11-27 19:35 ` [PATCH 2/5] device_cgroup: prepare exception list handling functions for two lists Aristeu Rozanski
2012-11-29 19:07 ` Serge E. Hallyn
2012-12-03 17:31 ` Tejun Heo
2012-11-27 19:35 ` [PATCH 3/5] device_cgroup: keep track of local group settings Aristeu Rozanski
2012-11-29 19:29 ` Serge E. Hallyn
2012-11-29 19:59 ` Aristeu Rozanski
2012-11-29 20:26 ` Serge E. Hallyn
2012-11-29 22:31 ` Aristeu Rozanski
2012-12-03 18:01 ` Serge E. Hallyn
2012-12-03 19:06 ` Aristeu Rozanski
2012-12-06 4:31 ` Serge E. Hallyn
2012-11-29 20:11 ` Aristeu Rozanski
2012-11-27 19:35 ` Aristeu Rozanski [this message]
2012-12-03 17:44 ` [PATCH 4/5] device_cgroup: make may_access() stronger Tejun Heo
2012-12-03 19:01 ` Aristeu Rozanski
2012-11-27 19:35 ` [PATCH 5/5] device_cgroup: propagate local changes down the hierarchy Aristeu Rozanski
2012-12-03 18:01 ` Tejun Heo
2012-12-03 19:14 ` Aristeu Rozanski
2012-12-03 21:36 ` Tejun Heo
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=20121127193502.817704289@napanee.usersys.redhat.com \
--to=aris@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=serge.hallyn@canonical.com \
--cc=tj@kernel.org \
/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
all inboxes | Powered by JetHome®