From: Tejun Heo <tj@kernel.org>
To: Aristeu Rozanski <aris@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Serge Hallyn <serge.hallyn@canonical.com>,
cgroups@vger.kernel.org
Subject: Re: [PATCH 4/5] device_cgroup: make may_access() stronger
Date: Mon, 3 Dec 2012 09:44:14 -0800 [thread overview]
Message-ID: <20121203174414.GI19802@htj.dyndns.org> (raw)
In-Reply-To: <20121127193502.817704289@napanee.usersys.redhat.com>
Hello,
On Tue, Nov 27, 2012 at 02:35:05PM -0500, Aristeu Rozanski wrote:
> @@ -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;
I kinda dislike this. This isn't a performanc critical path where we
must try our best to shave off a few condition checks. There's no
reason to encode the test like this. Please just spell the conditions
out in code rather than trying to build a magic series of equality
tests which somehow ends up spewing out the correct results.
Thanks.
--
tejun
next prev parent reply other threads:[~2012-12-03 17:44 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 ` [PATCH 4/5] device_cgroup: make may_access() stronger Aristeu Rozanski
2012-12-03 17:44 ` Tejun Heo [this message]
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=20121203174414.GI19802@htj.dyndns.org \
--to=tj@kernel.org \
--cc=aris@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=serge.hallyn@canonical.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).