From: Milan Broz <mbroz@redhat.com>
To: Massimo Burcheri <massimo@burcheri.de>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Fwd: Incompatible LRW changes from 2.6.27 to 2.6.29?
Date: Fri, 09 Oct 2009 13:55:31 +0200 [thread overview]
Message-ID: <4ACF24B3.2040507@redhat.com> (raw)
In-Reply-To: <200910051934.53231.massimo@burcheri.de>
On 10/05/2009 07:34 PM, Massimo Burcheri wrote:
> I even wrote to the authors of the LRW kernel modules who told me to
> better ask the LUKS community...
dm-crypt mailing is the best place for this report. This is IMHO kernel
problem (dm-crypt or cryptoAPI).
I would really appreciate that such bug reports are forwarded here,
(or in the case of kernel bug you can use bugzilla.kernel.org,
for cryptsetup issue page http://code.google.com/p/cryptsetup/issues/list)
I never heard about this problem (otherwise it was already explained or
solved).
> since 2.6.29 (especially patched linux-2.6.29-gentoo-r5) I cannot open a
> LUKS encrypted partition anymore. The same with 2.6.30. Under 2.6.27 it
> still works.
> By cryptsetup -c twofish or without -c option (that is AES by default)
> there are no problems with using encrypted partitions on both kernels.
> Therefore it could be related to the LRW option.
>
> My applied cipher is twofish-lrw-benbi:sha256.
> Kernel configuration on "Cryptographic API is unchanged from 2.6.27 to
> the more recent.
I'll run bisect on that to find where is the problem
(if reproducible on upstream gentoo-unpatched kernel).
Please can you check that there is no error message in syslog?
Milan
--
mbroz@redhat.com
next prev parent reply other threads:[~2009-10-09 11:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 17:34 [dm-crypt] Fwd: Incompatible LRW changes from 2.6.27 to 2.6.29? Massimo Burcheri
2009-10-09 11:55 ` Milan Broz [this message]
2009-10-09 12:26 ` Milan Broz
2009-10-09 20:07 ` Moji
2009-10-11 20:05 ` Massimo Burcheri
2009-10-11 21:56 ` 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=4ACF24B3.2040507@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--cc=massimo@burcheri.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox