From: Aristeu Rozanski <aris@redhat.com>
To: Rami Rosen <ramirose@gmail.com>
Cc: tj@kernel.org, lizefan@huawei.com, cgroups@vger.kernel.org,
containers@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, serge.hallyn@canonical.com
Subject: Re: [PATCH] devcg: remove parent_cgroup.
Date: Tue, 16 Apr 2013 16:37:00 -0400 [thread overview]
Message-ID: <20130416203700.GP24899@redhat.com> (raw)
In-Reply-To: <1366143895-21535-1-git-send-email-ramirose@gmail.com>
On Tue, Apr 16, 2013 at 11:24:55PM +0300, Rami Rosen wrote:
> In devcgroup_css_alloc(), there is no longer need for parent_cgroup.
> bd2953ebbb("devcg: propagate local changes down the hierarchy") made
> the variable parent_cgroup redundant. This patch removes parent_cgroup
> from devcgroup_css_alloc().
>
> Signed-off-by: Rami Rosen <ramirose@gmail.com>
> ---
> security/device_cgroup.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/security/device_cgroup.c b/security/device_cgroup.c
> index 994aecc..dd0dc57 100644
> --- a/security/device_cgroup.c
> +++ b/security/device_cgroup.c
> @@ -236,7 +236,6 @@ static void devcgroup_offline(struct cgroup *cgroup)
> static struct cgroup_subsys_state *devcgroup_css_alloc(struct cgroup *cgroup)
> {
> struct dev_cgroup *dev_cgroup;
> - struct cgroup *parent_cgroup;
>
> dev_cgroup = kzalloc(sizeof(*dev_cgroup), GFP_KERNEL);
> if (!dev_cgroup)
> @@ -244,7 +243,6 @@ static struct cgroup_subsys_state *devcgroup_css_alloc(struct cgroup *cgroup)
> INIT_LIST_HEAD(&dev_cgroup->exceptions);
> INIT_LIST_HEAD(&dev_cgroup->propagate_pending);
> dev_cgroup->behavior = DEVCG_DEFAULT_NONE;
> - parent_cgroup = cgroup->parent;
>
> return &dev_cgroup->css;
> }
oops
ACK
--
Aristeu
next prev parent reply other threads:[~2013-04-16 20:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 20:24 [PATCH] devcg: remove parent_cgroup Rami Rosen
2013-04-16 20:37 ` Aristeu Rozanski [this message]
2013-04-16 21:07 ` Serge Hallyn
2013-04-16 21:10 ` Aristeu Rozanski
2013-04-18 18: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=20130416203700.GP24899@redhat.com \
--to=aris@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=ramirose@gmail.com \
--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