From: Alex Elder <aelder@sgi.com>
To: Bill Kendall <wkendall@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH v3] xfsdump: enable dump header checksums
Date: Wed, 21 Sep 2011 12:27:20 -0500 [thread overview]
Message-ID: <1316626040.5872.0.camel@doink> (raw)
In-Reply-To: <1316625223-19970-1-git-send-email-wkendall@sgi.com>
On Wed, 2011-09-21 at 12:13 -0500, Bill Kendall wrote:
> Various structures in a dump file optionally contain a checksum, but
> the code to compute and validate the checksum has not been enabled.
> The checksum code has a negligible performance impact and so this
> patch enables the checksum code unconditionally. Also:
>
> - make sure all header sizes are multiples of 4 bytes
> (a requirement of the checksum routine)
> - zero structures to ensure internal padding has a known value
> - fix a bug in dump_extattr_buildrecord() which checksummed
> the wrong header structure
> - add calc_checksum() and is_checksum_valid() routines to
> cut down on duplicate code
>
> Signed-off-by: Bill Kendall <wkendall@sgi.com>
> ---
> Changes since v2:
> - Add an ASSERT in the checksum routines to enforce the
> multiple of 4 requirement, rather than checking at
> init (which may not catch all checksum users).
> - Remove unnecessary cast from void * to u_int32_t *.
> - Calculate endp different to avoid having to cast to
> void * or char *.
>
> common/content_inode.h | 27 ++++++++++++++++
> dump/content.c | 78 +++++++----------------------------------------
> restore/Makefile | 2 +-
> restore/content.c | 40 ++----------------------
> 4 files changed, 44 insertions(+), 103 deletions(-)
Looks good.
Reviewed-by: Alex Elder <aelder@sgi.com>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-09-21 17:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 17:13 [PATCH v3] xfsdump: enable dump header checksums Bill Kendall
2011-09-21 17:27 ` Alex Elder [this message]
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=1316626040.5872.0.camel@doink \
--to=aelder@sgi.com \
--cc=wkendall@sgi.com \
--cc=xfs@oss.sgi.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