From: Johannes Berg <johannes@sipsolutions.net>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-sparse <linux-sparse@vger.kernel.org>
Subject: Using sparse to catch invalid RCU dereferences?
Date: Tue, 08 Apr 2008 00:04:16 +0200 [thread overview]
Message-ID: <1207605856.12481.35.camel@johannes.berg> (raw)
[-- Attachment #1: Type: text/plain, Size: 674 bytes --]
Hi,
Just a thought, I haven't tried this yet because I'm not entirely sure
it's actually correct. I was just thinking it should be possible to
introduce something like
#define __rcu __attribute__((address_space(3)))
(for sparse only, of course) and then be able to say
struct myfoo *foo __rcu;
and sparse would warn on
struct myfoo *bar = foo;
but not on
struct myfoo *bar = rcu_dereference(foo);
by way of using __force inside rcu_dereference(), rcu_assign_pointer()
etc.
Would this be feasible? Or should one actually use __bitwise/__force to
also get the warning when assigning between two variables both marked
__rcu?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next reply other threads:[~2008-04-08 14:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 22:04 Johannes Berg [this message]
2008-04-08 15:52 ` Paul E. McKenney
2008-04-08 16:09 ` Johannes Berg
2008-04-08 17:24 ` Paul E. McKenney
2008-04-09 20:09 ` Johannes Berg
2008-04-10 22:32 ` Paul E. McKenney
2008-04-11 20:54 ` Johannes Berg
2008-04-11 18:18 ` Peter Zijlstra
2008-04-11 18:43 ` Paul E. McKenney
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=1207605856.12481.35.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.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®