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
- Follow-Ups:
- Re: [BUG] dmsetup table output changed from 2.6.18 to 2.6.19-rc3 and breaks yaird.
- From: Alasdair G Kergon <[email protected]>
- Re: [BUG] dmsetup table output changed from 2.6.18 to 2.6.19-rc3 and breaks yaird.
- Prev by Date: Re: Background scan of sata drives
- Next by Date: Re: compiling error: WARNING: "mii_nway_restart" [drivers/usb/net/usbnet.ko] undefined!
- Previous by thread: 2.6.19-rc3-git7: scsi_device_unbusy: inconsistent lock state
- Next by thread: Re: [BUG] dmsetup table output changed from 2.6.18 to 2.6.19-rc3 and breaks yaird.
- Index(es):
 |