From: Pavel Roskin <proski@gnu.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Michael Buesch <mb@bu3sch.de>,
linux-wireless <linux-wireless@vger.kernel.org>,
James Ketrenos <jketreno@linux.intel.com>
Subject: Re: cfg80211 wext compat w/o wext code changes, rtnl locking
Date: Mon, 02 Apr 2007 14:23:05 -0400 [thread overview]
Message-ID: <1175538185.25048.10.camel@dv> (raw)
In-Reply-To: <1175537741.16379.1.camel@johannes.berg>
On Mon, 2007-04-02 at 20:15 +0200, Johannes Berg wrote:
> On Mon, 2007-04-02 at 14:00 -0400, Pavel Roskin wrote:
>
> > Just for your information, rtnl_lock() is actually a mutex. Neither
> > rtnl_lock() nor any mutex operation are annotated to give sparse any
> > idea of what they are doing.
>
> Oh. And I guess rtnl_lock/unlock would need to be annotated and not just
> the mutex operations (or are they inlines? I forgot)
They are not inlines. Either way, sparse would require annotating them
if mutexes are to be tracked the way it's done for spinlocks.
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2007-04-02 18:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 23:00 cfg80211 wext compat w/o wext code changes, rtnl locking Johannes Berg
2007-03-30 10:11 ` Michael Buesch
2007-03-30 10:37 ` Johannes Berg
2007-04-02 18:00 ` Pavel Roskin
2007-04-02 18:15 ` Johannes Berg
2007-04-02 18:23 ` Pavel Roskin [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=1175538185.25048.10.camel@dv \
--to=proski@gnu.org \
--cc=jketreno@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
/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.