From: Eric Biggers <ebiggers@kernel.org>
To: fstests@vger.kernel.org
Cc: linux-fscrypt@vger.kernel.org, Ojaswin Mujoo <ojaswin@linux.ibm.com>
Subject: Re: [PATCH v2] generic/692: generalize the test for non-4K Merkle tree block sizes
Date: Wed, 11 Jan 2023 12:58:36 -0800 [thread overview]
Message-ID: <Y78i/G9cFZk0LmAo@sol.localdomain> (raw)
In-Reply-To: <20230111204739.77828-1-ebiggers@kernel.org>
On Wed, Jan 11, 2023 at 12:47:39PM -0800, Eric Biggers wrote:
> +bs=$FSV_BLOCK_SIZE
> +hash_size=32 # SHA-256
> +hash_per_block=$(echo "scale=30; $bs/($hash_size)" | $BC -q)
> +
> +# Compute the proportion of the original file size that the non-leaf levels of
> +# the Merkle tree take up. Ignoring padding, this is 1/${hashes_per_block}^2 +
> +# 1/${hashes_per_block}^3 + 1/${hashes_per_block}^4 + ... Compute it using the
Sorry, just saw a couple minor things to fix. v3 incoming...
- Eric
prev parent reply other threads:[~2023-01-11 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 20:47 [PATCH v2] generic/692: generalize the test for non-4K Merkle tree block sizes Eric Biggers
2023-01-11 20:58 ` Eric Biggers [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=Y78i/G9cFZk0LmAo@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=ojaswin@linux.ibm.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 read-only IMAP folder(s) and NNTP newsgroup(s).