From: Milan Broz <gmazyland@gmail.com>
To: Vadim Finkelstein <vad007@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] 4k block size in dm-crypt
Date: Fri, 07 Dec 2012 12:53:24 +0100 [thread overview]
Message-ID: <50C1D8B4.3080503@gmail.com> (raw)
In-Reply-To: <CAKK7v0SaPs-cewXrkG2YdfA9p6KydmbAqit87dS+VQ9xviGcjw@mail.gmail.com>
On 12/07/2012 04:58 AM, Vadim Finkelstein wrote:
> Regarding this:
> http://www.saout.de/pipermail/dm-crypt/2011-April/001673.html
>
> Was the issue of 4k block sizes ever solved? I have applied a 4k
> block size patch to my dm-crypt, but now seeing the same problem - if
> the data is read back with block size of 8192 (for example) it does
> not match what was previously written with block size of 4092.
What issue? The patch is not upstream and cannot be used wihout
additional changes.
If we add block-size parameter, we must reject all unaligned and
partial block reads to avoid this problem (and this part is still
missing, set proper io hinds for device and announce proper block size).
I would like to have such parameter one day in dmcrypt, but still
not sure what's the real use case (except workaround slow hw accelerators).
(And AES-NI and clones works quite well here with 512 block.)
Milan
prev parent reply other threads:[~2012-12-07 11:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 3:58 [dm-crypt] 4k block size in dm-crypt Vadim Finkelstein
2012-12-07 11:53 ` Milan Broz [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=50C1D8B4.3080503@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=vad007@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