From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 1/2] gfs2_edit savemeta: Fix up saving of dinodes/symlinks
Date: Thu, 17 Aug 2017 14:09:02 -0400 (EDT) [thread overview]
Message-ID: <165490896.1611916.1502993342247.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20170817171027.8449-1-anprice@redhat.com>
----- Original Message -----
| Factor out the code that decides whether to save the dinode contents,
| improve its error reporting (and don't exit) and make sure contents of
| symlink dinodes are saved.
|
| Signed-off-by: Andrew Price <anprice@redhat.com>
| ---
| gfs2/edit/savemeta.c | 52
| +++++++++++++++++++++++++++++++++-------------------
| 1 file changed, 33 insertions(+), 19 deletions(-)
|
Hi,
Both patches look good. ACK
Regards,
Bob Peterson
Red Hat File Systems
next prev parent reply other threads:[~2017-08-17 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 17:10 [Cluster-devel] [PATCH 1/2] gfs2_edit savemeta: Fix up saving of dinodes/symlinks Andrew Price
2017-08-17 17:10 ` [Cluster-devel] [PATCH 2/2] gfs2_edit savemeta: Use size_t for saved structure lengths Andrew Price
2017-08-17 18:09 ` Bob Peterson [this message]
2017-08-17 19:35 ` [Cluster-devel] [PATCH 1/2] gfs2_edit savemeta: Fix up saving of dinodes/symlinks Andrew Price
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=165490896.1611916.1502993342247.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).