From: Josh Triplett <josht@us.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>,
Andreas Gruenbacher <a.gruenbacher@computer.org>
Subject: [PATCH] [fs/mbcache.c] Add lock annotation for __mb_cache_entry_release_unlock
Date: Mon, 24 Jul 2006 17:28:10 -0700 [thread overview]
Message-ID: <1153787290.31581.37.camel@josh-work.beaverton.ibm.com> (raw)
__mb_cache_entry_release_unlock releases mb_cache_spinlock, so annotate it
accordingly.
Signed-off-by: Josh Triplett <josh@freedesktop.org>
---
fs/mbcache.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/fs/mbcache.c b/fs/mbcache.c
index e4fde1a..0ff7125 100644
--- a/fs/mbcache.c
+++ b/fs/mbcache.c
@@ -160,6 +160,7 @@ __mb_cache_entry_forget(struct mb_cache_
static void
__mb_cache_entry_release_unlock(struct mb_cache_entry *ce)
+ __releases(mb_cache_spinlock)
{
/* Wake up all processes queuing for this cache entry. */
if (ce->e_queued)
reply other threads:[~2006-07-25 0:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1153787290.31581.37.camel@josh-work.beaverton.ibm.com \
--to=josht@us.ibm.com \
--cc=a.gruenbacher@computer.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).