From: rpeterso@sourceware.org <rpeterso@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/gfs2/libgfs2 fs_ops.c
Date: 22 Jun 2007 20:49:11 -0000 [thread overview]
Message-ID: <20070622204911.26766.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: rpeterso at sourceware.org 2007-06-22 20:49:11
Modified files:
gfs2/libgfs2 : fs_ops.c
Log message:
Resolves: bz 245360: GFS2: userland tools have problems with small
block sizes
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs2/libgfs2/fs_ops.c.diff?cvsroot=cluster&r1=1.8&r2=1.9
--- cluster/gfs2/libgfs2/fs_ops.c 2007/05/15 18:11:10 1.8
+++ cluster/gfs2/libgfs2/fs_ops.c 2007/06/22 20:49:10 1.9
@@ -195,7 +195,7 @@
buffer_copy_tail(bh, 0,
ip->i_bh, sizeof(struct gfs2_dinode));
- brelse(bh, not_updated);
+ brelse(bh, updated);
}
}
@@ -345,9 +345,7 @@
unsigned int height;
unsigned int end_of_metadata;
unsigned int x;
- enum update_flags f;
- f = not_updated;
*new = 0;
*dblock = 0;
if (extlen)
@@ -379,7 +377,7 @@
for (x = 0; x < end_of_metadata; x++) {
lookup_block(ip, bh, x, mp, create, new, dblock);
- brelse(bh, not_updated);
+ brelse(bh, updated);
if (!*dblock)
goto out;
@@ -390,7 +388,6 @@
mh.mh_type = GFS2_METATYPE_IN;
mh.mh_format = GFS2_FORMAT_IN;
gfs2_meta_header_out(&mh, bh->b_data);
- f = updated;
} else
bh = bread(sdp, *dblock);
}
@@ -420,7 +417,7 @@
}
}
- brelse(bh, f);
+ brelse(bh, updated);
out:
free(mp);
next reply other threads:[~2007-06-22 20:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 20:49 rpeterso [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-09-25 16:01 [Cluster-devel] cluster/gfs2/libgfs2 fs_ops.c rpeterso
2007-09-24 23:17 rpeterso
2007-09-24 23:16 rpeterso
2007-06-22 20:50 rpeterso
2007-03-26 19:32 rpeterso
2007-03-26 19:32 rpeterso
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=20070622204911.26766.qmail@sourceware.org \
--to=rpeterso@sourceware.org \
/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.