[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <1209594649.29759.43.camel@localhost.localdomain>
Date: Wed, 30 Apr 2008 15:30:49 -0700
From: Matt Helsley <matthltc@...ibm.com>
To: Linux-Kernel <linux-kernel@...r.kernel.org>
Cc: Cedric Le Goater <clg@...ibm.com>, Paul Menage <menage@...gle.com>,
Oren Laadan <orenl@...columbia.edu>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Pavel Machek <pavel@....cz>,
linux-pm@...ts.linux-foundation.org,
Linux Containers <containers@...ts.linux-foundation.org>
Subject: Re: [RFC][PATCH 3/5] Container Freezer: Implement freezer cgroup
subsystem
On Wed, 2008-04-30 at 14:28 -0700, Matt Helsley wrote:
> On Wed, 2008-04-23 at 23:47 -0700, Matt Helsley wrote:
>
> <snip>
> > + cgroup_lock();
> > +
> > + if (cgroup_is_removed(cgroup)) {
> > + retval = -ENODEV;
> > + goto unlock;
> > + }
>
> I think this was copy/paste'd from cgroup_common_file_write() which
> modifies the cgroup hierarchy. However this function does not modify the
> cgroup hierarchy and we're not getting the cgroup from the task. So I
> don't think cgroup_lock()/unlock() are needed here. Paul, do you agree?
Oops! I didn't track the call chain correctly. Sorry for the noise...
Cheers,
-Matt Helsley
--
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