From: "René Scharfe" <l.s.r@web.de>
To: Matt Turner <mattst88@gmail.com>,
David Oberhollenzer <david.oberhollenzer@sigma-star.at>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] archive: Store checksum correctly
Date: Tue, 23 Jul 2019 22:08:38 +0200 [thread overview]
Message-ID: <9a0c89e4-b216-86f1-c721-c54fb2ee0a10@web.de> (raw)
In-Reply-To: <14410e00-4701-40d0-6960-e481fea50ed0@web.de>
Am 23.07.19 um 21:38 schrieb René Scharfe:
> is_checksum_valid() in
> https://github.com/AgentD/squashfs-tools-ng/blob/master/lib/tar/checksum.c
> compares the formatted checksum byte-by-byte. That seems
> unnecessarily strict. Parsing and comparing the numerical value
> of the checksum would be more forgiving, better adhere to POSIX and
> might be a tiny bit quicker.
I mean something like the patch below. Code and text size are bigger,
but it's more lenient and writes less. Untested.
(Side note: I'm a bit surprised that GCC 8.3 adds the eight spaces one
by one in the middle loop with -O2..)
---
lib/tar/checksum.c | 31 ++++++++++++++++++++++---------
1 file changed, 22 insertions(+), 9 deletions(-)
diff --git a/lib/tar/checksum.c b/lib/tar/checksum.c
index a2a101a..af94ab4 100644
--- a/lib/tar/checksum.c
+++ b/lib/tar/checksum.c
@@ -1,15 +1,27 @@
/* SPDX-License-Identifier: GPL-3.0-or-later */
#include "internal.h"
-void update_checksum(tar_header_t *hdr)
+static unsigned int get_checksum(const tar_header_t *hdr)
{
+ const unsigned char *header_start = (const unsigned char *)hdr;
+ const unsigned char *chksum_start = (const unsigned char *)hdr->chksum;
+ const unsigned char *header_end = header_start + sizeof(*hdr);
+ const unsigned char *chksum_end = chksum_start + sizeof(hdr->chksum);
+ const unsigned char *p;
unsigned int chksum = 0;
- size_t i;
- memset(hdr->chksum, ' ', sizeof(hdr->chksum));
+ for (p = header_start; p < chksum_start; p++)
+ chksum += *p;
+ for (; p < chksum_end; p++)
+ chksum += ' ';
+ for (; p < header_end; p++)
+ chksum += *p;
+ return chksum;
+}
- for (i = 0; i < sizeof(*hdr); ++i)
- chksum += ((unsigned char *)hdr)[i];
+void update_checksum(tar_header_t *hdr)
+{
+ unsigned int chksum = get_checksum(hdr);
sprintf(hdr->chksum, "%06o", chksum);
hdr->chksum[6] = '\0';
@@ -18,9 +30,10 @@ void update_checksum(tar_header_t *hdr)
bool is_checksum_valid(const tar_header_t *hdr)
{
- tar_header_t copy;
+ unsigned int calculated_chksum = get_checksum(hdr);
+ uint64_t read_chksum;
- memcpy(©, hdr, sizeof(*hdr));
- update_checksum(©);
- return memcmp(hdr, ©, sizeof(*hdr)) == 0;
+ if (read_octal(hdr->chksum, sizeof(hdr->chksum), &read_chksum))
+ return 0;
+ return read_chksum == calculated_chksum;
}
--
2.22.0
next prev parent reply other threads:[~2019-07-23 20:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 2:57 [PATCH] archive: Store checksum correctly Matt Turner
2019-07-23 16:49 ` Junio C Hamano
2019-07-23 19:31 ` Jeff King
2019-07-23 19:38 ` René Scharfe
2019-07-23 20:08 ` René Scharfe [this message]
2019-07-23 21:34 ` David Oberhollenzer
2019-07-23 21:21 ` Junio C Hamano
2019-07-24 1:04 ` Jonathan Nieder
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=9a0c89e4-b216-86f1-c721-c54fb2ee0a10@web.de \
--to=l.s.r@web.de \
--cc=david.oberhollenzer@sigma-star.at \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mattst88@gmail.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).