From: Milan Broz <gmazyland@gmail.com>
To: dm-crypt <dm-crypt@saout.de>
Cc: jason_daly@lavabit.com
Subject: Re: [dm-crypt] Unexpected behavior in cryptsetup-1.5.1
Date: Sat, 29 Dec 2012 15:37:08 +0100 [thread overview]
Message-ID: <50DF0014.20105@gmail.com> (raw)
In-Reply-To: <50DDEFDD.4010102@gmail.com>
On 12/28/2012 08:15 PM, Milan Broz wrote:
> On 12/28/2012 04:22 PM, jason_daly@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.
Thanks,
Milan
prev parent reply other threads:[~2012-12-29 14:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 15:22 [dm-crypt] Unexpected behavior in cryptsetup-1.5.1 jason_daly
2012-12-28 19:15 ` Milan Broz
2012-12-29 14:37 ` 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=50DF0014.20105@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=jason_daly@lavabit.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