[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160616221434.GI3262@mtj.duckdns.org>
Date: Thu, 16 Jun 2016 18:14:34 -0400
From: Tejun Heo <tj@...nel.org>
To: Daniel Bristot de Oliveira <daolivei@...hat.com>
Cc: linux-kernel@...r.kernel.org, Rik van Riel <riel@...hat.com>,
"Luis Claudio R. Goncalves" <lgoncalv@...hat.com>,
Li Zefan <lizefan@...wei.com>,
Johannes Weiner <hannes@...xchg.org>,
Juri Lelli <juri.lelli@....com>, cgroups@...r.kernel.org
Subject: Re: [PATCH v2] cgroup: disable irqs while holding css_set_lock
On Thu, Jun 16, 2016 at 06:03:15PM -0400, Tejun Heo wrote:
> On Thu, Jun 16, 2016 at 06:48:56PM -0300, Daniel Bristot de Oliveira wrote:
> > On 06/07/2016 05:05 PM, Daniel Bristot de Oliveira wrote:
> > > On 06/07/2016 04:30 PM, Tejun Heo wrote:
> > >> Is this something in mainline? This forces all task free path to be
> > >> irq-safe, which *could* be fine but it's weird to make cgroup free
> > >> path irq-safe for something which isn't in mainline.
> > >
> > > you mean, mainline linux kernel? if so, yes it is. I was running the
> > > v4.7-rc2 from Linus, as is.... no external patches applied.
> > >
> >
> > is there any other question/objection about this patch?
>
> Nope, I was just on vacation. Applied to cgroup/for-4.7-fixes.
Except that the patch seems to use irqsave/restore instead of plain
irq ones in places. Care to update those?
Thanks!
--
tejun
Powered by blists - more mailing lists