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>,
Gordon Farquharson <gordonfarquharson@gmail.com>
Subject: Re: Bug#403426: kernel corrupts LUKS partition header on arm
Date: Thu, 4 Jan 2007 16:09:51 +0100 [thread overview]
Message-ID: <20070104150951.GM27931@deprecation.cyrius.com> (raw)
In-Reply-To: <87ejqb57k4.wl%clemens@endorphin.org>
* Clemens Fruhwirth <clemens@endorphin.org> [2007-01-04 12:56]:
> > corruption. At least FUSE doesn't work on ARM without those patches,
> > so it seems likely that luksOpen is also affected.
>
> So, can we close the bug against cryptsetup in this case?
#403426 is really about the header corruption which you have fixed in
SVN. It should be closed when the Debian maintainers make a new
upload with that fix.
> Maybe someone else can verify that?
CCing Gordon. :)
--
Martin Michlmayr
http://www.cyrius.com/
next prev parent reply other threads:[~2007-01-04 15:09 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
2007-01-04 11:56 ` Clemens Fruhwirth
2007-01-04 15:09 ` Martin Michlmayr [this message]
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=20070104150951.GM27931@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 \
--cc=gordonfarquharson@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.