s390x kernels are inconsistent for cloud stuff
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Tim Gardner | ||
Xenial |
Fix Released
|
Medium
|
Tim Gardner |
Bug Description
So to do virtual machine / cloudy stuff things in the kernel config, are not how one would expect them to be. Whilst investigating that I've went ahead to compare all our kernel configs.
amd64/config.
amd64/config.
arm64/config.
arm64/config.
armhf/config.
armhf/config.
i386/config.
i386/config.
powerpc/
powerpc/
ppc64el/
ppc64el/
but...
s390x/config.
s390x/config.
It would make sense to set CONFIG_VIRTIO_BLK and _NET to "=y" on s390x.
Also:
amd64/config.
arm64/config.
armhf/config.
i386/config.
powerpc/
ppc64el/
s390x/config.
Is a bit of mixed bag... x86+s390x have it as a module, yet arm*+powerpc* have it built in? Maybe all arches should be =y ?
another one:
Is there something special about ZLIB_DEFLATE on s390x?
amd64/config.
arm64/config.
armhf/config.
i386/config.
powerpc/
ppc64el/
s390x/config.
CVE References
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Changed in linux (Ubuntu Xenial): | |
importance: | Undecided → Medium |
I'm not sure why CONFIG_ZLIB_DEFLATE is forced to =m for s390. Regardless, the whole lib directory is referenced in debian. master/ control. d/generic. inclusion- list which gets zlib_deflate.ko into the linux-image- generic- *.deb package.