From: Patryk Obara <patryk.obara@gmail.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>, git@vger.kernel.org
Cc: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>, "Jeff King" <peff@peff.net>
Subject: Re: [PATCH 02/12] hash: create union for hash context allocation
Date: Sun, 28 Jan 2018 20:57:21 +0100 [thread overview]
Message-ID: <54b29396-d994-7afd-9c18-83fca8e4ad6f@gmail.com> (raw)
In-Reply-To: <20180128155722.880805-3-sandals@crustytoothpaste.net>
On 28/01/2018 16:57, brian m. carlson wrote:
> In various parts of our code, we want to allocate a structure
> representing the internal state of a hash algorithm. The original
> implementation of the hash algorithm abstraction assumed we would do
> that using heap allocations, and added a context size element to struct
> git_hash_algo. However, most of the existing code uses stack
> allocations and conversion would needlessly complicate various parts of
> the code. Add a union for the purpose of allocating hash contexts on
> the stack and a typedef for ease of use. Remove the ctxsz element for
> struct git_hash_algo, which is no longer very useful.
Overall, I am OK with this approach (it's straightforward change and
cleanest way to replace direct calls to git_SHA1_* functions), but just
to play devil's advocate: OpenSSL decided to sway users into heap
allocated contexts, citing binary compatibility issues if they change
the size of context structure. [1]
I think we might need to revisit this design decision in future -
perhaps as soon as we'll transition away from calling git_SHA1_*
functions directly.
> +/* A suitably aligned type for stack allocations of hash contexts. */
> +union git_hash_ctx {
> + git_SHA_CTX sha1;
> +};
> +typedef union git_hash_ctx git_hash_ctx;
> +
> typedef void (*git_hash_init_fn)(void *ctx);
> typedef void (*git_hash_update_fn)(void *ctx, const void *in, size_t len);
> typedef void (*git_hash_final_fn)(unsigned char *hash, void *ctx);
I think it would be appropriate to replace "void *ctx" with
"git_hash_ctx *ctx". This way we can avoid unnecessary casting in
git_hash_sha1_* functions.
[1] https://wiki.openssl.org/index.php/Manual:EVP_DigestInit(3)#NOTES
--
| ← Ceci n'est pas une pipe
Patryk Obara
next prev parent reply other threads:[~2018-01-28 19:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-28 15:57 [PATCH 00/12] object_id part 11 (the_hash_algo) brian m. carlson
2018-01-28 15:57 ` [PATCH 01/12] hash: move SHA-1 macros to hash.h brian m. carlson
2018-01-28 15:57 ` [PATCH 02/12] hash: create union for hash context allocation brian m. carlson
2018-01-28 19:57 ` Patryk Obara [this message]
2018-01-28 20:16 ` brian m. carlson
2018-01-28 15:57 ` [PATCH 03/12] builtin/index-pack: improve hash function abstraction brian m. carlson
2018-01-28 15:57 ` [PATCH 04/12] builtin/unpack-objects: switch uses of SHA-1 to the_hash_algo brian m. carlson
2018-01-28 15:57 ` [PATCH 05/12] sha1_file: " brian m. carlson
2018-01-28 15:57 ` [PATCH 06/12] fast-import: switch various " brian m. carlson
2018-01-28 20:10 ` Patryk Obara
2018-01-28 15:57 ` [PATCH 07/12] pack-check: convert various uses of SHA-1 to abstract forms brian m. carlson
2018-01-28 15:57 ` [PATCH 08/12] pack-write: switch various SHA-1 values " brian m. carlson
2018-01-28 20:30 ` Patryk Obara
2018-01-28 21:52 ` brian m. carlson
2018-01-28 15:57 ` [PATCH 09/12] read-cache: abstract away uses of SHA-1 brian m. carlson
2018-01-28 19:50 ` Eric Sunshine
2018-01-28 20:10 ` brian m. carlson
2018-01-28 15:57 ` [PATCH 10/12] csum-file: rename sha1file to hashfile brian m. carlson
2018-01-28 15:57 ` [PATCH 11/12] csum-file: abstract uses of SHA-1 brian m. carlson
2018-01-28 15:57 ` [PATCH 12/12] bulk-checkin: abstract SHA-1 usage brian m. carlson
2018-01-28 20:48 ` [PATCH 00/12] object_id part 11 (the_hash_algo) Patryk Obara
2018-01-28 22:00 ` brian m. carlson
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=54b29396-d994-7afd-9c18-83fca8e4ad6f@gmail.com \
--to=patryk.obara@gmail.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
/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).