From: Milan Broz <mbroz@redhat.com>
To: Salatiel Filho <salatiel.filho@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Data Corruption using cryptsetup luks on ARM arch
Date: Mon, 14 Sep 2009 11:59:36 +0200 [thread overview]
Message-ID: <4AAE1408.7000705@redhat.com> (raw)
In-Reply-To: <beb91d720909140225s2f80bf6bq5b4be7eadb936fe9@mail.gmail.com>
Salatiel Filho wrote:
> I do not think it is a hardware problem since the disk is fine and
> it works fine in other architectures with no corruption at all. And
> the page allocator failure always happens when using crypted swap but
> there is no problem when using uncrypted swap.
There was some problems with O_DIRECT on ARM architectures
(search archive, I think I posted some links).
Anyway, problem is with using already mapped volume (e.g. swap) or
with using cryptsetup (LUKS header/keyslot corruption)?
I do not thing that it is problem in dm-crypt
Do you have some reproducer? kernel version, syslog messages etc?
Milan
next prev parent reply other threads:[~2009-09-14 9:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-13 22:19 [dm-crypt] Data Corruption using cryptsetup luks on ARM arch Salatiel Filho
2009-09-14 3:35 ` Arno Wagner
2009-09-14 9:25 ` Salatiel Filho
2009-09-14 9:59 ` Milan Broz [this message]
2009-09-14 21:10 ` Arno Wagner
2009-09-15 10:48 ` Salatiel Filho
2009-09-15 11:53 ` Arno Wagner
2009-09-18 13:40 ` Salatiel Filho
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=4AAE1408.7000705@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--cc=salatiel.filho@gmail.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 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.