linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Bristot de Oliveira <daolivei@redhat.com>
To: Daniel Bristot de Oliveira <daolivei@redhat.com>,
	Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org, Rik van Riel <riel@redhat.com>,
	"Luis Claudio R. Goncalves" <lgoncalv@redhat.com>,
	Li Zefan <lizefan@huawei.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Juri Lelli <juri.lelli@arm.com>,
	cgroups@vger.kernel.org
Subject: Re: [PATCH v2] cgroup: disable irqs while holding css_set_lock
Date: Thu, 16 Jun 2016 18:48:56 -0300	[thread overview]
Message-ID: <38469b61-7cc5-5fec-4de3-0e9a616dfe95@redhat.com> (raw)
In-Reply-To: <6f15f27f-3757-5413-4292-1386e95bc278@redhat.com>

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?

-- Daniel

  reply	other threads:[~2016-06-16 21:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-07 18:51 [PATCH v2] cgroup: disable irqs while holding css_set_lock Daniel Bristot de Oliveira
2016-06-07 19:30 ` Tejun Heo
2016-06-07 20:05   ` Daniel Bristot de Oliveira
2016-06-16 21:48     ` Daniel Bristot de Oliveira [this message]
2016-06-16 22:03       ` Tejun Heo
2016-06-16 22:14         ` Tejun Heo
2016-06-17  0:12           ` Daniel Bristot de Oliveira
2016-06-17  5:36             ` Tejun Heo
2016-06-17 19:59               ` Daniel Bristot de Oliveira
2016-06-22 20:00                 ` Daniel Bristot de Oliveira

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=38469b61-7cc5-5fec-4de3-0e9a616dfe95@redhat.com \
    --to=daolivei@redhat.com \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=juri.lelli@arm.com \
    --cc=lgoncalv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=riel@redhat.com \
    --cc=tj@kernel.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).