mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Jerry Snitselaar <jerry.snitselaar@oracle.com>
Cc: linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
	serge.hallyn@canonical.com, aris@redhat.com,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] device_cgroup: don't grab mutex in rcu callback
Date: Thu, 14 Feb 2013 08:48:30 -0800	[thread overview]
Message-ID: <20130214164830.GI9057@htj.dyndns.org> (raw)
In-Reply-To: <1360860363-2879-1-git-send-email-jerry.snitselaar@oracle.com>

(cc'ing Andrew)

Andrew, can you please pick up this one?

 http://article.gmane.org/gmane.linux.kernel.cgroups/6158/raw

Thank you.

On Thu, Feb 14, 2013 at 09:46:03AM -0700, Jerry Snitselaar wrote:
> commit 103a197 "security/device_cgroup: lock assert fails in
> dev_exception_clean()" grabs devcgroup_mutex to fix assert failure,
> but mutex can't be grabbed in rcu callback. Since there shouldn't be
> any other references when css_free is called, mutex isn't needed for
> list cleanup in devcgroup_css_free().
> 
> Signed-off-by: Jerry Snitselaar <jerry.snitselaar@oracle.com>
> Acked-by: Tejun Heo <tj@kernel.org>
> Acked-by: Aristeu Rozanski <aris@redhat.com>
> ---
>  security/device_cgroup.c | 21 ++++++++++++---------
>  1 file changed, 12 insertions(+), 9 deletions(-)
> 
> diff --git a/security/device_cgroup.c b/security/device_cgroup.c
> index d794abc..1c69e38 100644
> --- a/security/device_cgroup.c
> +++ b/security/device_cgroup.c
> @@ -159,6 +159,16 @@ static void dev_exception_rm(struct dev_cgroup *dev_cgroup,
>  	}
>  }
>  
> +static void __dev_exception_clean(struct dev_cgroup *dev_cgroup)
> +{
> +	struct dev_exception_item *ex, *tmp;
> +
> +	list_for_each_entry_safe(ex, tmp, &dev_cgroup->exceptions, list) {
> +		list_del_rcu(&ex->list);
> +		kfree_rcu(ex, rcu);
> +	}
> +}
> +
>  /**
>   * dev_exception_clean - frees all entries of the exception list
>   * @dev_cgroup: dev_cgroup with the exception list to be cleaned
> @@ -167,14 +177,9 @@ static void dev_exception_rm(struct dev_cgroup *dev_cgroup,
>   */
>  static void dev_exception_clean(struct dev_cgroup *dev_cgroup)
>  {
> -	struct dev_exception_item *ex, *tmp;
> -
>  	lockdep_assert_held(&devcgroup_mutex);
>  
> -	list_for_each_entry_safe(ex, tmp, &dev_cgroup->exceptions, list) {
> -		list_del_rcu(&ex->list);
> -		kfree_rcu(ex, rcu);
> -	}
> +	__dev_exception_clean(dev_cgroup);
>  }
>  
>  /*
> @@ -215,9 +220,7 @@ static void devcgroup_css_free(struct cgroup *cgroup)
>  	struct dev_cgroup *dev_cgroup;
>  
>  	dev_cgroup = cgroup_to_devcgroup(cgroup);
> -	mutex_lock(&devcgroup_mutex);
> -	dev_exception_clean(dev_cgroup);
> -	mutex_unlock(&devcgroup_mutex);
> +	__dev_exception_clean(dev_cgroup);
>  	kfree(dev_cgroup);
>  }
>  
> -- 
> 1.8.1.1.293.gfe73786
> 

-- 
tejun

  reply	other threads:[~2013-02-14 16:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-14 16:46 Jerry Snitselaar
2013-02-14 16:48 ` Tejun Heo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-01-23 18:00 Jerry Snitselaar

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=20130214164830.GI9057@htj.dyndns.org \
    --to=tj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=aris@redhat.com \
    --cc=cgroups@vger.kernel.org \
    --cc=jerry.snitselaar@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=serge.hallyn@canonical.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

all inboxes | Powered by JetHome®