From: Sasha Levin <sasha.levin-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
trinity-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH cgroup/for-3.11] cgroup: grab cgroup_mutex in drop_parsed_module_refcounts()
Date: Wed, 26 Jun 2013 14:51:36 -0400 [thread overview]
Message-ID: <51CB3838.10400@oracle.com> (raw)
In-Reply-To: <20130626175008.GF4405-9pTldWuhBndy/B6EtB590w@public.gmane.org>
On 06/26/2013 01:50 PM, Tejun Heo wrote:
> On Tue, Jun 25, 2013 at 06:05:21PM -0700, Tejun Heo wrote:
>> This isn't strictly necessary as all subsystems specified in
>> @subsys_mask are guaranteed to be pinned; however, it does spuriously
>> trigger lockdep warning. Let's grab cgroup_mutex around it.
>>
>> Signed-off-by: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
>
> Applied both patches to cgroup/for-3.11.
FWIW, for both patches,
Tested-by: Sasha Levin <sasha.levin-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Thanks,
Sasha
WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sasha.levin@oracle.com>
To: Tejun Heo <tj@kernel.org>
Cc: lizefan@huawei.com, LKML <linux-kernel@vger.kernel.org>,
cgroups@vger.kernel.org, trinity@vger.kernel.org
Subject: Re: [PATCH cgroup/for-3.11] cgroup: grab cgroup_mutex in drop_parsed_module_refcounts()
Date: Wed, 26 Jun 2013 14:51:36 -0400 [thread overview]
Message-ID: <51CB3838.10400@oracle.com> (raw)
In-Reply-To: <20130626175008.GF4405@mtj.dyndns.org>
On 06/26/2013 01:50 PM, Tejun Heo wrote:
> On Tue, Jun 25, 2013 at 06:05:21PM -0700, Tejun Heo wrote:
>> This isn't strictly necessary as all subsystems specified in
>> @subsys_mask are guaranteed to be pinned; however, it does spuriously
>> trigger lockdep warning. Let's grab cgroup_mutex around it.
>>
>> Signed-off-by: Tejun Heo <tj@kernel.org>
>
> Applied both patches to cgroup/for-3.11.
FWIW, for both patches,
Tested-by: Sasha Levin <sasha.levin@oracle.com>
Thanks,
Sasha
next prev parent reply other threads:[~2013-06-26 18:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 17:20 cgroup: kernel BUG at kernel/cgroup.c:1038! Sasha Levin
[not found] ` <51C9D17B.5090208-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2013-06-26 1:04 ` [PATCH cgroup/for-3.11] cgroup: fix cgroupfs_root early destruction path Tejun Heo
2013-06-26 1:04 ` Tejun Heo
2013-06-26 1:05 ` [PATCH cgroup/for-3.11] cgroup: grab cgroup_mutex in drop_parsed_module_refcounts() Tejun Heo
2013-06-26 9:12 ` Li Zefan
2013-06-26 9:12 ` Li Zefan
[not found] ` <20130626010521.GE30407-9pTldWuhBndy/B6EtB590w@public.gmane.org>
2013-06-26 17:50 ` Tejun Heo
2013-06-26 17:50 ` Tejun Heo
[not found] ` <20130626175008.GF4405-9pTldWuhBndy/B6EtB590w@public.gmane.org>
2013-06-26 18:51 ` Sasha Levin [this message]
2013-06-26 18:51 ` Sasha Levin
[not found] ` <20130626010454.GD30407-9pTldWuhBndy/B6EtB590w@public.gmane.org>
2013-06-26 9:14 ` [PATCH cgroup/for-3.11] cgroup: fix cgroupfs_root early destruction path Li Zefan
2013-06-26 9:14 ` Li Zefan
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=51CB3838.10400@oracle.com \
--to=sasha.levin-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=trinity-u79uwXL29TY76Z2rM5mHXA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.