From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: David Howells <dhowells@redhat.com>
Cc: torvalds@osdl.org, akpm@linux-foundation.org,
eric.dumazet@gmail.com, keyrings@linux-nfs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KEYS: Fix an RCU warning in the reading of user keys
Date: Wed, 21 Apr 2010 13:12:19 -0700 [thread overview]
Message-ID: <20100421201219.GJ2563@linux.vnet.ibm.com> (raw)
In-Reply-To: <20100421163634.14538.74339.stgit@warthog.procyon.org.uk>
On Wed, Apr 21, 2010 at 05:36:35PM +0100, David Howells wrote:
> Fix an RCU warning in the reading of user keys:
>
> ===================================================
> [ INFO: suspicious rcu_dereference_check() usage. ]
> ---------------------------------------------------
> security/keys/user_defined.c:202 invoked rcu_dereference_check() without protection!
>
> other info that might help us debug this:
>
>
> rcu_scheduler_active = 1, debug_locks = 0
> 1 lock held by keyctl/3637:
> #0: (&key->sem){+++++.}, at: [<ffffffff811a80ae>] keyctl_read_key+0x9c/0xcf
>
> stack backtrace:
> Pid: 3637, comm: keyctl Not tainted 2.6.34-rc5-cachefs #18
> Call Trace:
> [<ffffffff81051f6c>] lockdep_rcu_dereference+0xaa/0xb2
> [<ffffffff811aa55f>] user_read+0x47/0x91
> [<ffffffff811a80be>] keyctl_read_key+0xac/0xcf
> [<ffffffff811a8a06>] sys_keyctl+0x75/0xb7
> [<ffffffff81001eeb>] system_call_fastpath+0x16/0x1b
Queued for 2.6.34, thank you David!
Thanx, Paul
> Signed-off-by: David Howells <dhowells@redhat.com>
> ---
>
> security/keys/user_defined.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/security/keys/user_defined.c b/security/keys/user_defined.c
> index 7c687d5..e9aa079 100644
> --- a/security/keys/user_defined.c
> +++ b/security/keys/user_defined.c
> @@ -199,7 +199,8 @@ long user_read(const struct key *key, char __user *buffer, size_t buflen)
> struct user_key_payload *upayload;
> long ret;
>
> - upayload = rcu_dereference(key->payload.data);
> + upayload = rcu_dereference_protected(
> + key->payload.data, rwsem_is_locked(&((struct key *)key)->sem));
> ret = upayload->datalen;
>
> /* we can return the data as is */
>
prev parent reply other threads:[~2010-04-21 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 16:36 [PATCH] KEYS: Fix an RCU warning in the reading of user keys David Howells
2010-04-21 20:12 ` Paul E. McKenney [this message]
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=20100421201219.GJ2563@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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.