From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2: Clear dirty bit at end of inode glock sync
Date: Mon, 20 Apr 2009 10:18:38 +0100 [thread overview]
Message-ID: <1240219118.3345.3.camel@localhost.localdomain> (raw)
In-Reply-To: <1240218982.3345.2.camel@localhost.localdomain>
Hi,
I should also add that this patch has gone into the -fixes tree as well
and I'm intending to push it to Linus fairly shortly,
Steve.
On Mon, 2009-04-20 at 10:16 +0100, Steven Whitehouse wrote:
> >From 5e60bcaa263dac8a3df4334459414bcb0808009f Mon Sep 17 00:00:00 2001
> From: Steven Whitehouse <swhiteho@redhat.com>
> Date: Mon, 20 Apr 2009 08:58:45 +0100
> Subject: [PATCH] GFS2: Clear dirty bit at end of inode glock sync
>
> The dirty bit can get set during the inode glock sync. Its too
> complicated to change that at the moment, so this is the quick
> fix - to clear the bit again at the end of the function.
>
> Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
>
> diff --git a/fs/gfs2/glops.c b/fs/gfs2/glops.c
> index bf23a62..70f87f4 100644
> --- a/fs/gfs2/glops.c
> +++ b/fs/gfs2/glops.c
> @@ -156,6 +156,12 @@ static void inode_go_sync(struct gfs2_glock *gl)
> error = filemap_fdatawait(metamapping);
> mapping_set_error(metamapping, error);
> gfs2_ail_empty_gl(gl);
> + /*
> + * Writeback of the data mapping may cause the dirty flag to be set
> + * so we have to clear it again here.
> + */
> + smp_mb__before_clear_bit();
> + clear_bit(GLF_DIRTY, &gl->gl_flags);
> }
>
> /**
prev parent reply other threads:[~2009-04-20 9:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 9:16 [Cluster-devel] GFS2: Clear dirty bit at end of inode glock sync Steven Whitehouse
2009-04-20 9:18 ` 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=1240219118.3345.3.camel@localhost.localdomain \
--to=swhiteho@redhat.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