From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2: Fix one RG corner case
Date: Tue, 13 Nov 2012 10:41:34 -0500 (EST) [thread overview]
Message-ID: <1341787120.38256162.1352821294753.JavaMail.root@redhat.com> (raw)
In-Reply-To: <1352819973.2727.18.camel@menhir>
----- Original Message -----
| >From aa8920c96897dd82f0520f9e7db7311b42547ce6 Mon Sep 17 00:00:00
| >2001
| From: Steven Whitehouse <swhiteho@redhat.com>
| Date: Tue, 13 Nov 2012 14:50:35 +0000
| Subject: GFS2: Fix one RG corner case
|
| For filesystems with only a single resource group, we need to be
| careful
| that the allocation loop will not land up with a NULL resource group.
| This
| fixes a bug in a previous patch where the gfs2_rgrpd_get_next()
| function
| was being used instead of gfs2_rgrpd_get_first()
|
| Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
|
| diff --git a/fs/gfs2/rgrp.c b/fs/gfs2/rgrp.c
| index 99a6197..5625e93 100644
| --- a/fs/gfs2/rgrp.c
| +++ b/fs/gfs2/rgrp.c
| @@ -1776,10 +1776,11 @@ static u32 gfs2_orlov_skip(const struct
| gfs2_inode *ip)
| static bool gfs2_select_rgrp(struct gfs2_rgrpd **pos, const struct
| gfs2_rgrpd *begin)
| {
| struct gfs2_rgrpd *rgd = *pos;
| + struct gfs2_sbd *sdp = rgd->rd_sbd;
|
| rgd = gfs2_rgrpd_get_next(rgd);
| if (rgd == NULL)
| - rgd = gfs2_rgrpd_get_next(NULL);
| + rgd = gfs2_rgrpd_get_first(sdp);
| *pos = rgd;
| if (rgd != begin) /* If we didn't wrap */
| return true;
| --
| 1.7.4
Hi,
If we do this, can't we get into an infinite loop if the one and only
rgrp is full? In that case, rgrp will be == begin, so it won't return
true, so the caller won't ever realize it's wrapped.
Regards,
Bob Peterson
Red Hat File Systems
next prev parent reply other threads:[~2012-11-13 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 15:19 [Cluster-devel] GFS2: Fix one RG corner case Steven Whitehouse
2012-11-13 15:41 ` Bob Peterson [this message]
2012-11-13 15:46 ` Steven Whitehouse
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=1341787120.38256162.1352821294753.JavaMail.root@redhat.com \
--to=rpeterso@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).