From: Aristeu Rozanski <aris-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] device_cgroup: lock assert fails in dev_exception_clean()
Date: Wed, 23 Jan 2013 11:38:50 -0500 [thread overview]
Message-ID: <20130123163849.GH17632@redhat.com> (raw)
In-Reply-To: <20130123163640.GB2373-9pTldWuhBndy/B6EtB590w@public.gmane.org>
Hi Tejun,
On Wed, Jan 23, 2013 at 08:36:40AM -0800, Tejun Heo wrote:
> On Wed, Jan 23, 2013 at 09:29:39AM -0500, Aristeu Rozanski wrote:
> > Hi Jerry,
> > On Tue, Jan 22, 2013 at 09:31:41PM -0700, Jerry Snitselaar wrote:
> > > The original patch I sent to James and lkml got pulled in to linus. Is
> > > the correct thing to do here put the list cleanup code back in
> > > devcgroup_css_free and drop the call to dev_exception_clean along with
> > > change my patch made like this?
> >
> > I think this is what was suggested (not tested):
>
> Yeap.
on a slightly subject, hierarchy support is still desired for device
cgroups? I got the patchset ready by the time ebiederman submitted
userns patches and like it was discussed before device_cgroup would be
made obsolete once userns was out.
--
Aristeu
next prev parent reply other threads:[~2013-01-23 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1358460018-14717-1-git-send-email-jerry.snitselaar@oracle.com>
[not found] ` <1358460018-14717-2-git-send-email-jerry.snitselaar@oracle.com>
[not found] ` <20130117220642.GE16568@mtj.dyndns.org>
[not found] ` <20130117220642.GE16568-9pTldWuhBndy/B6EtB590w@public.gmane.org>
2013-01-17 23:13 ` [PATCH] device_cgroup: lock assert fails in dev_exception_clean() Jerry Snitselaar
[not found] ` <20130117231341.GA14588-w8wXvOoPVbZpWwPY5x2yo1aTQe2KTcn/@public.gmane.org>
2013-01-23 4:31 ` Jerry Snitselaar
[not found] ` <20130123043140.GA5913-w8wXvOoPVbZpWwPY5x2yo1aTQe2KTcn/@public.gmane.org>
2013-01-23 14:29 ` Aristeu Rozanski
[not found] ` <20130123142939.GC17632-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-01-23 16:36 ` Tejun Heo
[not found] ` <20130123163640.GB2373-9pTldWuhBndy/B6EtB590w@public.gmane.org>
2013-01-23 16:38 ` Aristeu Rozanski [this message]
[not found] ` <20130123163849.GH17632-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-01-23 16:41 ` 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=20130123163849.GH17632@redhat.com \
--to=aris-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@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