From: Milan Broz <gmazyland@gmail.com>
To: Natanael Copa <ncopa@alpinelinux.org>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] luks header on initramfs img fails due to no O_DIRECT support in tmpfs
Date: Fri, 08 Aug 2014 13:20:13 +0200 [thread overview]
Message-ID: <53E4B26D.3030809@gmail.com> (raw)
In-Reply-To: <20140808092257.04ccaca7@ncopa-desktop.alpinelinux.org>
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
next prev parent reply other threads:[~2014-08-08 11:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 7:22 [dm-crypt] luks header on initramfs img fails due to no O_DIRECT support in tmpfs Natanael Copa
2014-08-08 11:20 ` Milan Broz [this message]
2014-08-08 13:38 ` Milan Broz
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=53E4B26D.3030809@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=ncopa@alpinelinux.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.