From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Fri, 8 Aug 2014 13:20:16 +0200 (CEST) Received: by mail-wg0-f45.google.com with SMTP id x12so5395254wgg.28 for ; Fri, 08 Aug 2014 04:20:16 -0700 (PDT) Message-ID: <53E4B26D.3030809@gmail.com> Date: Fri, 08 Aug 2014 13:20:13 +0200 From: Milan Broz MIME-Version: 1.0 References: <20140808092257.04ccaca7@ncopa-desktop.alpinelinux.org> In-Reply-To: <20140808092257.04ccaca7@ncopa-desktop.alpinelinux.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] luks header on initramfs img fails due to no O_DIRECT support in tmpfs List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Natanael Copa Cc: dm-crypt@saout.de On 08/08/2014 09:22 AM, Natanael Copa wrote: > I found this posting while looking at an issue with cryptsetup-1.6.5 in initramfs: > http://www.saout.de/pipermail/dm-crypt/2014-August/004227.html > > I believe this is same thing as reported here: > http://bugs.alpinelinux.org/issues/3281 > > Seems like the problem is that open(2) does not support O_DIRECT when on tmpfs. Yes, I expected something like that. In cryptsetup 1.6.4 this was not happening because it was hidden by temporary dmcrypt device in the middle of stack. It is kernel bug, O_DIRECT should work on tmpfs and similar devices. Anyway, it should also work on older kernels, so I'll think about implementing some workaround here. Thanks, Milan