[BUG] dmsetup table output changed from 2.6.18 to 2.6.19-rc3 and breaks yaird.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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: signature.asc
Description: Digital signature

--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel

[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux