From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH V2] GFS2: Combine func meta_prep_new with its only caller
Date: Fri, 26 May 2017 09:56:28 -0400 (EDT) [thread overview]
Message-ID: <1752575275.14905093.1495806988111.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <2004376135.14896837.1495806824589.JavaMail.zimbra@redhat.com>
Hi,
This patch is the same as the one I posted earlier, but I
moved the setting of mh_magic inside the protection of the
buffer lock, since Steve pointed out how flawed that was.
I like Steve's other idea of combining some of the other code
of the callers, for example, adding the new buffer to an existing
transaction, but I'll address that with a later patch.
Regards,
Bob Peterson
---
Before this patch function meta_prep_new was only called in one
place, function gfs2_meta_new which is only a couple lines long.
This patch combines them for readability.
Signed-off-by: Bob Peterson <rpeterso@redhat.com>
---
diff --git a/fs/gfs2/meta_io.c b/fs/gfs2/meta_io.c
index 663ffc1..b1705a7 100644
--- a/fs/gfs2/meta_io.c
+++ b/fs/gfs2/meta_io.c
@@ -158,18 +158,6 @@ struct buffer_head *gfs2_getbuf(struct gfs2_glock *gl, u64 blkno, int create)
return bh;
}
-static void meta_prep_new(struct buffer_head *bh)
-{
- struct gfs2_meta_header *mh = (struct gfs2_meta_header *)bh->b_data;
-
- lock_buffer(bh);
- clear_buffer_dirty(bh);
- set_buffer_uptodate(bh);
- unlock_buffer(bh);
-
- mh->mh_magic = cpu_to_be32(GFS2_MAGIC);
-}
-
/**
* gfs2_meta_new - Get a block
* @gl: The glock associated with this block
@@ -180,9 +168,15 @@ static void meta_prep_new(struct buffer_head *bh)
struct buffer_head *gfs2_meta_new(struct gfs2_glock *gl, u64 blkno)
{
- struct buffer_head *bh;
- bh = gfs2_getbuf(gl, blkno, CREATE);
- meta_prep_new(bh);
+ struct buffer_head *bh = gfs2_getbuf(gl, blkno, CREATE);
+ struct gfs2_meta_header *mh = (struct gfs2_meta_header *)bh->b_data;
+
+ lock_buffer(bh);
+ clear_buffer_dirty(bh);
+ set_buffer_uptodate(bh);
+ mh->mh_magic = cpu_to_be32(GFS2_MAGIC);
+ unlock_buffer(bh);
+
return bh;
}
parent reply other threads:[~2017-05-26 13:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <2004376135.14896837.1495806824589.JavaMail.zimbra@redhat.com>]
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=1752575275.14905093.1495806988111.JavaMail.zimbra@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).