From: Stefan Schmidt <stefan@datenfreihafen.org>
To: linux-kernel@vger.kernel.org
Cc: herbert@gondor.apana.org.au, dm-devel@redhat.com
Subject: [BUG] dmsetup table output changed from 2.6.18 to 2.6.19-rc3 and breaks yaird.
Date: Mon, 30 Oct 2006 16:19:30 +0100 [thread overview]
Message-ID: <20061030151930.GQ27337@susi> (raw)
[-- Attachment #1: Type: text/plain, Size: 833 bytes --]
Hello.
Today the build of an initrd from a 2.6.19-rc3 kernel failed.
fairlight:/boot# yaird -o /tmp/foo.initrd 2.6.19-rc3-fairlight
yaird error: Could not read output for /sbin/modprobe -v -n --show-depends --set-version 2.6.19-rc3-fairlight cbc(aes) (fatal)
dmsetup table has changed the report for luks cipher.
dmsetup table on 2.6.18 reports: aes-cbc-essiv:sha256
dmsetup table on 2.6.19-rc3 reports: cbc(aes)-cbc-essiv:sha256
The problem seems to be on the kernel side here. Herbert Xu changed
the output with d1806f6a97a536b043fe50e6d8a25b061755cf50
http://kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d1806f6a97a536b043fe50e6d8a25b061755cf50
The question is if this change was intentional and yaird should be
fixed, or it's a kernel API breakage.
regards
Stefan Schmidt
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 241 bytes --]
next reply other threads:[~2006-10-30 15:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 15:19 Stefan Schmidt [this message]
2006-10-30 18:43 ` [BUG] dmsetup table output changed from 2.6.18 to 2.6.19-rc3 and breaks yaird Alasdair G Kergon
2006-10-30 19:00 ` Linus Torvalds
2006-10-30 19:15 ` Alasdair G Kergon
2006-10-30 19:39 ` Christophe Saout
2006-10-31 0:56 ` Herbert Xu
2006-10-30 19:52 ` Stefan Schmidt
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=20061030151930.GQ27337@susi \
--to=stefan@datenfreihafen.org \
--cc=dm-devel@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox