From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH] GFS2: Check rs_free with rd_rsspin protection
Date: Wed, 6 Jul 2016 17:01:25 +0100 [thread overview]
Message-ID: <577D2B55.9090103@redhat.com> (raw)
In-Reply-To: <1537255470.7048688.1467820347281.JavaMail.zimbra@redhat.com>
Hi,
Acked-by: Steven Whitehouse <swhiteho@redhat.com>
Steve.
On 06/07/16 16:52, Bob Peterson wrote:
> Hi,
>
> For the last process to close a file opened for write, function
> gfs2_rsqa_delete was deleting the file's inode's block reservation
> out of the rgrp reservations tree. Then it was checking to make sure
> rs_free was 0, but it was performing the check outside the protection
> of rd_rsspin spin_lock. The rd_rsspin spin_lock protection is needed
> to prevent a race between the process freeing the reservation and
> another who is allocating a new set of blocks inside the same rgrp
> for the same inode, thus changing its value.
>
> Signed-off-by: Bob Peterson <rpeterso@redhat.com>
>
> Regards,
>
> Bob Peterson
> Red Hat File Systems
> ---
> diff --git a/fs/gfs2/rgrp.c b/fs/gfs2/rgrp.c
> index fba38ca..86ccc015 100644
> --- a/fs/gfs2/rgrp.c
> +++ b/fs/gfs2/rgrp.c
> @@ -658,6 +658,7 @@ void gfs2_rs_deltree(struct gfs2_blkreserv *rs)
> if (rgd) {
> spin_lock(&rgd->rd_rsspin);
> __rs_deltree(rs);
> + BUG_ON(rs->rs_free);
> spin_unlock(&rgd->rd_rsspin);
> }
> }
> @@ -671,10 +672,8 @@ void gfs2_rs_deltree(struct gfs2_blkreserv *rs)
> void gfs2_rsqa_delete(struct gfs2_inode *ip, atomic_t *wcount)
> {
> down_write(&ip->i_rw_mutex);
> - if ((wcount == NULL) || (atomic_read(wcount) <= 1)) {
> + if ((wcount == NULL) || (atomic_read(wcount) <= 1))
> gfs2_rs_deltree(&ip->i_res);
> - BUG_ON(ip->i_res.rs_free);
> - }
> up_write(&ip->i_rw_mutex);
> gfs2_qa_delete(ip, wcount);
> }
>
prev parent reply other threads:[~2016-07-06 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <323041035.7048186.1467820249716.JavaMail.zimbra@redhat.com>
2016-07-06 15:52 ` [Cluster-devel] [GFS2 PATCH] GFS2: Check rs_free with rd_rsspin protection Bob Peterson
2016-07-06 16:01 ` 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=577D2B55.9090103@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).