From: Steven Whitehouse <swhiteho@redhat.com>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: Al Viro <viro@ZenIV.linux.org.uk>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] gfs2: trivial sparse lock annotations
Date: Fri, 30 May 2008 10:27:42 +0100 [thread overview]
Message-ID: <1212139662.3474.27.camel@quoit> (raw)
In-Reply-To: <1212110871.28403.167.camel@brick>
Hi,
Now in the GFS2 -nmw git tree. Thanks,
Steve.
On Thu, 2008-05-29 at 18:27 -0700, Harvey Harrison wrote:
> Annotate the &sdp->sd_log_lock.
>
> Signed-off-by: Harvey Harrison <harvey.harrison@gmail.com>
> ---
> fs/gfs2/log.c | 2 ++
> fs/gfs2/log.h | 2 ++
> 2 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/fs/gfs2/log.c b/fs/gfs2/log.c
> index 548264b..6c6af9f 100644
> --- a/fs/gfs2/log.c
> +++ b/fs/gfs2/log.c
> @@ -87,6 +87,8 @@ void gfs2_remove_from_ail(struct gfs2_bufdata *bd)
> */
>
> static void gfs2_ail1_start_one(struct gfs2_sbd *sdp, struct gfs2_ail *ai)
> +__releases(&sdp->sd_log_lock)
> +__acquires(&sdp->sd_log_lock)
> {
> struct gfs2_bufdata *bd, *s;
> struct buffer_head *bh;
> diff --git a/fs/gfs2/log.h b/fs/gfs2/log.h
> index 7711528..7c64510 100644
> --- a/fs/gfs2/log.h
> +++ b/fs/gfs2/log.h
> @@ -21,6 +21,7 @@
> */
>
> static inline void gfs2_log_lock(struct gfs2_sbd *sdp)
> +__acquires(&sdp->sd_log_lock)
> {
> spin_lock(&sdp->sd_log_lock);
> }
> @@ -32,6 +33,7 @@ static inline void gfs2_log_lock(struct gfs2_sbd *sdp)
> */
>
> static inline void gfs2_log_unlock(struct gfs2_sbd *sdp)
> +__releases(&sdp->sd_log_lock)
> {
> spin_unlock(&sdp->sd_log_lock);
> }
prev parent reply other threads:[~2008-05-30 9:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 1:27 [PATCH] gfs2: trivial sparse lock annotations Harvey Harrison
2008-05-30 9:27 ` Steven Whitehouse [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=1212139662.3474.27.camel@quoit \
--to=swhiteho@redhat.com \
--cc=harvey.harrison@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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