From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] GFS2: Patch to protect sd_log_num_jdata
Date: Wed, 22 Aug 2007 17:13:04 +0100 [thread overview]
Message-ID: <1187799184.8765.947.camel@quoit> (raw)
In-Reply-To: <1187799330.15734.21.camel@technetium.msp.redhat.com>
Hi,
Now in the -nmw git tree. Thanks,
Steve.
On Wed, 2007-08-22 at 11:15 -0500, Bob Peterson wrote:
> Hi,
>
> This is a patch to GFS2 to protect sd_log_num_jdata with the
> gfs2_log_lock. Without this patch, there is a timing window
> where you can get hit the following assert from function
> gfs2_log_flush():
>
> gfs2_assert_withdraw(sdp,
> sdp->sd_log_num_buf + sdp->sd_log_num_jdata ==
> sdp->sd_log_commited_buf +
> sdp->sd_log_commited_databuf);
>
> I've tested it on my roth cluster and it fixes the problem.
>
> Regards,
>
> Bob Peterson
> --
> diff -pur a/fs/gfs2/lops.c b/fs/gfs2/lops.c
> --- a/fs/gfs2/lops.c 2007-08-21 18:01:07.000000000 -0500
> +++ b/fs/gfs2/lops.c 2007-08-21 18:13:33.000000000 -0500
> @@ -492,11 +492,12 @@ static void databuf_lo_add(struct gfs2_s
>
> gfs2_trans_add_gl(bd->bd_gl);
> if (gfs2_is_jdata(ip)) {
> - sdp->sd_log_num_jdata++;
> gfs2_pin(sdp, bd->bd_bh);
> tr->tr_num_databuf_new++;
> }
> gfs2_log_lock(sdp);
> + if (gfs2_is_jdata(ip))
> + sdp->sd_log_num_jdata++;
> sdp->sd_log_num_databuf++;
> list_add(&le->le_list, &sdp->sd_log_le_databuf);
> gfs2_log_unlock(sdp);
>
>
prev parent reply other threads:[~2007-08-22 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 16:15 [Cluster-devel] [PATCH] GFS2: Patch to protect sd_log_num_jdata Bob Peterson
2007-08-22 16:13 ` 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=1187799184.8765.947.camel@quoit \
--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 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.