From: Serge Hallyn <serge.hallyn-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
To: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: "Serge E. Hallyn"
<serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
Aristeu Rozanski <aris-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH 1/2] device_cgroup: fix RCU usage
Date: Tue, 6 Nov 2012 11:48:41 -0600 [thread overview]
Message-ID: <20121106174841.GB28916@sergelap> (raw)
In-Reply-To: <20121106171737.GJ30069-9pTldWuhBndy/B6EtB590w@public.gmane.org>
Quoting Tejun Heo (tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org):
> dev_cgroup->exceptions is protected with devcgroup_mutex for writes
> and RCU for reads; however, RCU usage isn't correct.
>
> * dev_exception_clean() doesn't use RCU variant of list_del() and
> kfree(). The function can race with may_access() and may_access()
> may end up dereferencing already freed memory. Use list_del_rcu()
> and kfree_rcu() instead.
>
> * may_access() may be called only with RCU read locked but doesn't use
> RCU safe traversal over ->exceptions. Use list_for_each_entry_rcu().
>
> Signed-off-by: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
> Cc: stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> Cc: Aristeu Rozanski <aris-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> Cc: Li Zefan <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
> Cc: Serge E. Hallyn <serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>
Acked-by: Serge E. Hallyn <serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>
thanks,
-serge
> ---
> Oops, wrong patch. This is the correct one.
>
> Thanks.
>
> security/device_cgroup.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> --- a/security/device_cgroup.c
> +++ b/security/device_cgroup.c
> @@ -164,8 +164,8 @@ static void dev_exception_clean(struct d
> struct dev_exception_item *ex, *tmp;
>
> list_for_each_entry_safe(ex, tmp, &dev_cgroup->exceptions, list) {
> - list_del(&ex->list);
> - kfree(ex);
> + list_del_rcu(&ex->list);
> + kfree_rcu(ex, rcu);
> }
> }
>
> @@ -298,7 +298,7 @@ static int may_access(struct dev_cgroup
> struct dev_exception_item *ex;
> bool match = false;
>
> - list_for_each_entry(ex, &dev_cgroup->exceptions, list) {
> + list_for_each_entry_rcu(ex, &dev_cgroup->exceptions, list) {
> if ((refex->type & DEV_BLOCK) && !(ex->type & DEV_BLOCK))
> continue;
> if ((refex->type & DEV_CHAR) && !(ex->type & DEV_CHAR))
next prev parent reply other threads:[~2012-11-06 17:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 17:16 [PATCH 1/2] device_cgroup: add lockdep asserts Tejun Heo
[not found] ` <20121106171612.GH30069-9pTldWuhBndy/B6EtB590w@public.gmane.org>
2012-11-06 17:16 ` [PATCH 2/2] " Tejun Heo
2012-11-06 17:17 ` [PATCH 1/2] device_cgroup: fix RCU usage Tejun Heo
[not found] ` <20121106171737.GJ30069-9pTldWuhBndy/B6EtB590w@public.gmane.org>
2012-11-06 17:48 ` Serge Hallyn [this message]
2012-11-06 20:29 ` Tejun Heo
2012-11-06 17:40 ` [PATCH 1/2] device_cgroup: add lockdep asserts Serge Hallyn
2012-11-06 20:29 ` 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=20121106174841.GB28916@sergelap \
--to=serge.hallyn-z7wlfzj8ewms+fvcfc7uqw@public.gmane.org \
--cc=aris-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox