From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.saout.de ([127.0.0.1]) by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vJcDhf9Gh2c7 for ; Sat, 29 Dec 2012 15:37:13 +0100 (CET) Received: from mail-ee0-f43.google.com (mail-ee0-f43.google.com [74.125.83.43]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Sat, 29 Dec 2012 15:37:12 +0100 (CET) Received: by mail-ee0-f43.google.com with SMTP id e49so5705918eek.16 for ; Sat, 29 Dec 2012 06:37:11 -0800 (PST) Message-ID: <50DF0014.20105@gmail.com> Date: Sat, 29 Dec 2012 15:37:08 +0100 From: Milan Broz MIME-Version: 1.0 References: <56447.5.39.88.44.1356708146.squirrel@lavabit.com> <50DDEFDD.4010102@gmail.com> In-Reply-To: <50DDEFDD.4010102@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] Unexpected behavior in cryptsetup-1.5.1 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt Cc: jason_daly@lavabit.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