linux-modules-4.18.0-8-generic has:
./lib/modules/4.18.0-8-generic/kernel/arch/s390/crypto/paes_s390.ko
./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/pkey.ko
./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt.ko
./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt_cex2a.ko
./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt_cex4.ko
./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt_pcixcc.ko
All of the above appear to be missing from the crypto-modules-4.18.0-8
-generic-di, please ship them in crypto-modules udeb.
To avoid discrepancies as to what crypto is supported by the installed
system, versus d-i environment, it would be nice to make udebs and
linux-modules packages roughly the same.
Does it at all make sense to ship matching set of
kernel/{arch,drivers}/s390/crypto/*.ko in crypto-modules udeb, as
shilled in linux-modules deb?
** Description changed:
- for zkey feature, check that all the required modules are in -image
- package, not extras.
+ todo: check that these modules are included in the initramfs as well.
- check that these are also shipped in udebs (probably like crypto-modules
- udeb and/or disk drivers).
+ === linux crypto-modules udeb task ==
+ linux-modules-4.18.0-8-generic has:
+ ./lib/modules/4.18.0-8-generic/kernel/arch/s390/crypto/paes_s390.ko
+ ./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/pkey.ko
+ ./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt.ko
+ ./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt_cex2a.ko
+ ./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt_cex4.ko
+ ./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt_pcixcc.ko
- check that these modules are included in the initramfs as well.
+ All of the above appear to be missing from the crypto-modules-4.18.0-8
+ -generic-di, please ship them in crypto-modules udeb.
+
+ To avoid discrepancies as to what crypto is supported by the installed
+ system, versus d-i environment, it would be nice to make udebs and
+ linux-modules packages roughly the same.
+
+ Does it at all make sense to ship matching set of
kernel/{arch,drivers}/s390/crypto/*.ko in crypto-modules udeb, as shilled in
linux-modules deb?
+ ===
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1794346
Title:
check and fix zkey required kernel modules locations in debs, udebs,
and initramfs
Status in linux package in Ubuntu:
Triaged
Bug description:
todo: check that these modules are included in the initramfs as well.
=== linux crypto-modules udeb task ==
linux-modules-4.18.0-8-generic has:
./lib/modules/4.18.0-8-generic/kernel/arch/s390/crypto/paes_s390.ko
./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/pkey.ko
./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt.ko
./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt_cex2a.ko
./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt_cex4.ko
./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt_pcixcc.ko
All of the above appear to be missing from the crypto-modules-4.18.0-8
-generic-di, please ship them in crypto-modules udeb.
To avoid discrepancies as to what crypto is supported by the installed
system, versus d-i environment, it would be nice to make udebs and
linux-modules packages roughly the same.
Does it at all make sense to ship matching set of
kernel/{arch,drivers}/s390/crypto/*.ko in crypto-modules udeb, as shilled in
linux-modules deb?
===
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794346/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
