DLPX-86675 Disk quota exceeded when unpacking an upgrade image

[prakashsurya]

It looks like there's a new config directory for the 5.15 kernel, so I think the prior OVERRIDES file is no longer getting applied. This change moves the file to the correct location for the 5.15 kernel. No changes being made to the file contents as part of this change.

Related Work

• DLPX-86675 Disk quota exceeded when unpacking an upgrade image linux-kernel-azure#28
• DLPX-86675 Disk quota exceeded when unpacking an upgrade image linux-kernel-gcp#28
• DLPX-86675 Disk quota exceeded when unpacking an upgrade image linux-kernel-generic#27
• DLPX-86675 Disk quota exceeded when unpacking an upgrade image linux-kernel-oracle#27

[prakashsurya]

git-ab-pre-push with changes to all kernel (e.g. to check upgrade image size) is here

[prakashsurya]

upgrade image is back down to 4.6G with these changes (applied to all kernels):

$ sudo get-property-from-image internal-qa.upgrade.tar VERSION
13.0.0.0-snapshot.20230627015835706+jenkins-selfservice-appliance-build-develop-pre-push-586

$ ls -lh internal-qa.upgrade.tar
-rw-r--r-- 1 delphix staff 4.6G Jun 27 03:48 internal-qa.upgrade.tar

[prakashsurya]

@sebroy I had to make the following additional changes to get the build to work on all the platforms:

--- a/debian.aws-5.15/config/OVERRIDES
+++ b/debian.aws-5.15/config/OVERRIDES
@@ -18,6 +18,7 @@ CONFIG_WIRELESS=n
 # Disable various "drivers" modules which we don't use.
 #
 CONFIG_ACCESSIBILITY=n
+CONFIG_AMD_PMC=n
 CONFIG_ATA=n
 CONFIG_ATM_DRIVERS=n
 CONFIG_AUXDISPLAY=n
@@ -67,7 +68,6 @@ CONFIG_SFI=n
 CONFIG_SIOX=n
 CONFIG_SLIMBUS=n
 CONFIG_SOUNDWIRE=n
-CONFIG_SPI=n
 CONFIG_SPMI=n
 CONFIG_STAGING=n
 CONFIG_THERMAL=n

are you OK with this?

[sebroy]

@prakashsurya yeah, that seems fine to me. I'm curious to know why the build depends on SPI, but I'm fine with it.

[prakashsurya]

12:08:11  ERROR: modpost: "__spi_register_driver" [drivers/misc/mei/mei-vsc.ko] undefined!
12:08:11  ERROR: modpost: "spi_sync_locked" [drivers/misc/mei/mei-vsc.ko] undefined!

this was the error, and only on some kernels (e.g. generic)..

seems like the mei-vsc module is currently built, and it depends on a symbol that was no longer being built due to our CONFIG_SPI setting.. I haven't determined why this didn't fail on 5.4.. we might be able to solve this by removing mei-vsc as well (in addition to SPI), but I can look into that in a follow up PR, as it wasn't clear if removing mei-vsc was OK for us to do.. re-enabling SPI seemed safer to me.