From: Martin Michlmayr <tbm@cyrius.com>
To: Clemens Fruhwirth <clemens@endorphin.org>
Cc: 403426@bugs.debian.org, dm-devel@redhat.com,
Brian Brunswick <bdb-reportbug@forbidden.co.uk>
Subject: Re: Bug#403426: kernel corrupts LUKS partition header on arm
Date: Wed, 3 Jan 2007 20:37:22 +0100 [thread overview]
Message-ID: <20070103193722.GC27931@deprecation.cyrius.com> (raw)
In-Reply-To: <87fyar6h49.wl%clemens@endorphin.org>
* Clemens Fruhwirth <clemens@endorphin.org> [2007-01-03 20:32]:
> > I just applied the two patches from that thread and successfully ran
> > 'cryptsetup luksClose' on ARM.
>
> "cryptsetup luksClose" is just an alias for "cryptsetup remove". This
> should never fail. What's with luksOpen after the patches?
Sorry, I meant to say that luksOpen worked with the patches. I simply
copy&pasted the wrong line.
> > Would the lack of __flush_anon_page() on ARM explain the corruption
> > you've observed?
> Again, I'm not familiar with this.
Well, it seems to fix the problem and according to the thread on lkml
the lack of flush_anon_page() on ARM is associated with some
corruption. At least FUSE doesn't work on ARM without those patches,
so it seems likely that luksOpen is also affected.
--
Martin Michlmayr
http://www.cyrius.com/
next prev parent reply other threads:[~2007-01-03 19:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061217022906.2434.60658.reportbug@LKG8A754B.example.org>
2006-12-20 16:15 ` Bug#403426: kernel corrupts LUKS partition header on arm Martin Michlmayr
2006-12-29 10:52 ` Clemens Fruhwirth
2006-12-29 16:38 ` Martin Michlmayr
2006-12-29 20:24 ` Martin Michlmayr
2006-12-30 10:50 ` Clemens Fruhwirth
2006-12-30 13:13 ` Martin Michlmayr
2007-01-02 17:00 ` Clemens Fruhwirth
2007-01-02 18:04 ` Martin Michlmayr
2007-01-02 18:34 ` Clemens Fruhwirth
2007-01-03 16:59 ` Clemens Fruhwirth
2007-01-03 19:14 ` Martin Michlmayr
2007-01-03 19:32 ` Clemens Fruhwirth
2007-01-03 19:37 ` Martin Michlmayr [this message]
2007-01-04 11:56 ` Clemens Fruhwirth
2007-01-04 15:09 ` Martin Michlmayr
2007-01-05 8:36 ` Gordon Farquharson
2007-01-05 9:59 ` Martin Michlmayr
2007-01-06 6:38 ` Gordon Farquharson
2007-01-07 5:47 ` Gordon Farquharson
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=20070103193722.GC27931@deprecation.cyrius.com \
--to=tbm@cyrius.com \
--cc=403426@bugs.debian.org \
--cc=bdb-reportbug@forbidden.co.uk \
--cc=clemens@endorphin.org \
--cc=dm-devel@redhat.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.