[dm-crypt] Unexpected behavior in cryptsetup-1.5.1
gmazyland at gmail.com
Sat Dec 29 15:37:08 CET 2012
On 12/28/2012 08:15 PM, Milan Broz wrote:
> On 12/28/2012 04:22 PM, jason_daly at lavabit.com wrote:
>> I see that in the release notes for cryptsetup-1.5.1, it talks about "lazy
>> initializations." Could this be the cause of this new behavior, and if
>> so, is this an expected trade-off in order to allow for some cryptsetup
>> operations to be run by non-root users?
> Yes, it is caused by this change and it is a bug (and should be fixed
> in devel tree already), so next release will work again here.
This was a new regression, some filesystems do not support O_DIRECT flag
(here it was tmpfs) so code now tries to workaround it by repeating
open without direct-io if it fails.
Fixed in git devel tree.
More information about the dm-crypt