From: Tejun Heo <tj@kernel.org>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: axboe@kernel.dk, linux-kernel@vger.kernel.org,
Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [PATCH] blk-cgroup: Call cgroup_path only under cgroup lock
Date: Mon, 12 Mar 2012 11:04:23 -0700 [thread overview]
Message-ID: <20120312180423.GC23255@google.com> (raw)
In-Reply-To: <1331582478-2259-1-git-send-email-levinsasha928@gmail.com>
Hello, Sasha.
On Mon, Mar 12, 2012 at 04:01:18PM -0400, Sasha Levin wrote:
> Since we can't keep rcu read lock during blkg_alloc(), we currently
> call cgroup_path() without any locks at all.
>
> This patch adds cgroup locking before calling cgroup_path.
>
> This also fixes a lockdep warning on boot.
>
> Signed-off-by: Sasha Levin <levinsasha928@gmail.com>
Which branch is this against? There's already pending stat update
patch from Vivek which fix this problem along with the percpu
allocation problem.
Thanks.
--
tejun
next prev parent reply other threads:[~2012-03-12 18:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 20:01 [PATCH] blk-cgroup: Call cgroup_path only under cgroup lock Sasha Levin
2012-03-12 18:04 ` Tejun Heo [this message]
2012-03-12 18:06 ` Sasha Levin
2012-03-12 18:12 ` 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=20120312180423.GC23255@google.com \
--to=tj@kernel.org \
--cc=axboe@kernel.dk \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@redhat.com \
/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