[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130313135632.GA4417@redhat.com>
Date: Wed, 13 Mar 2013 09:56:32 -0400
From: Aristeu Rozanski <aris@...hat.com>
To: Tejun Heo <tj@...nel.org>
Cc: linux-kernel@...r.kernel.org, cgroups@...r.kernel.org,
"Serge E. Hallyn" <serge@...lyn.com>,
Serge Hallyn <serge.hallyn@...onical.com>
Subject: Re: [PATCH v5 4/4] devcg: propagate local changes down the hierarchy
Hi Tejun,
On Tue, Feb 19, 2013 at 04:20:16PM -0500, Aristeu Rozanski wrote:
> On Tue, Feb 19, 2013 at 09:12:08PM +0000, Serge E. Hallyn wrote:
> > Quoting Aristeu Rozanski (aris@...hat.com):
> > > + } else {
> > > + /*
> > > + * in the other possible cases:
> > > + * root's behavior: allow, devcg's: deny
> > > + * root's behavior: deny, devcg's: deny
> > > + * the exception will be removed
> > > + */
> >
> > Technically this case isn't needed, right? Will the dev_exception_rm()
> > also be done by revalidate_active_exceptions()? So it's safe (but
> > not necessary) to drop the else here. Though the comment is very
> > informative, and it might be worth keeping the code as is for clarity.
>
> that's correct, it'll end up being removed by
> revalidate_active_exceptions(). if others have no objection, I'll keep
> it
>
> Thanks for the reviews Serge, much appreciated
did you pick this series up for 3.10 or you want me to resubmit?
--
Aristeu
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists