From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 1/5] gfs2_edit savemeta: Factor out the bh saving code
Date: Thu, 12 Jan 2017 10:42:26 -0500 (EST) [thread overview]
Message-ID: <1084579934.10026401.1484235746295.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20170110143446.14419-2-anprice@redhat.com>
----- Original Message -----
| save_block() accepts a block number, reads it and saves it, which makes
| it tricky to save an already-read block without reading it a second
| time. Split out the bh saving part of save_block() into save_bh() to
| make things more flexible.
|
| Also switch the return value of save_block to only convey error/success
| and return the block type through an optional pointer argument instead.
|
| Signed-off-by: Andrew Price <anprice@redhat.com>
| ---
Hi,
ACK,
Bob Peterson
Red Hat File Systems
next prev parent reply other threads:[~2017-01-12 15:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 14:34 [Cluster-devel] [PATCH 0/5] gfs2_edit fixes Andrew Price
2017-01-10 14:34 ` [Cluster-devel] [PATCH 1/5] gfs2_edit savemeta: Factor out the bh saving code Andrew Price
2017-01-12 15:42 ` Bob Peterson [this message]
2017-01-10 14:34 ` [Cluster-devel] [PATCH 2/5] gfs2_edit savemeta: Don't read rgrp blocks twice Andrew Price
2017-01-12 15:49 ` Bob Peterson
2017-01-13 14:42 ` Andrew Price
2017-01-13 15:06 ` Bob Peterson
2017-01-10 14:34 ` [Cluster-devel] [PATCH 3/5] gfs2_edit savemeta: Follow lf_next Andrew Price
2017-01-12 15:52 ` Bob Peterson
2017-01-10 14:34 ` [Cluster-devel] [PATCH 4/5] gfs2_edit: Fix unaligned access in restore_init() Andrew Price
2017-01-12 15:58 ` Bob Peterson
2017-01-10 14:34 ` [Cluster-devel] [PATCH 5/5] gfs2_edit: Fix unaligned accesses due to saved_metablock size Andrew Price
2017-01-12 16:02 ` Bob Peterson
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=1084579934.10026401.1484235746295.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).