cgroups.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aristeu Rozanski <aris-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Serge Hallyn <serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	Rami Rosen <ramirose-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] devcg: remove parent_cgroup.
Date: Tue, 16 Apr 2013 17:10:10 -0400	[thread overview]
Message-ID: <20130416211010.GQ24899@redhat.com> (raw)
In-Reply-To: <20130416210725.GA21536@sergelap>

On Tue, Apr 16, 2013 at 04:07:25PM -0500, Serge Hallyn wrote:
> Quoting Aristeu Rozanski (aris-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org):
> > 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-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > > ---
> > >  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
> 
> Not seeing the patches this is based on in Linus' tree yet, but given
> the context above I don't see how it could not be right :)

they're on Tejun's tree

-- 
Aristeu

  reply	other threads:[~2013-04-16 21:10 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
     [not found] ` <1366143895-21535-1-git-send-email-ramirose-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-04-16 20:37   ` Aristeu Rozanski
     [not found]     ` <20130416203700.GP24899-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-04-16 21:07       ` Serge Hallyn
2013-04-16 21:10         ` Aristeu Rozanski [this message]
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=20130416211010.GQ24899@redhat.com \
    --to=aris-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ramirose-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org \
    --cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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;
as well as URLs for NNTP newsgroup(s).