@@ -14691,7 +14691,7 @@ CONFIG_VLAN_8021Q policy<{'amd64': 'm', 'arm64': '
CONFIG_VLAN_8021Q_GVRP policy<{'amd64': 'y', 'arm64': 'y', 'armhf': 'y', 'ppc64el': 'y', 'riscv64': 'y', 's390x': 'y'}>
CONFIG_VLAN_8021Q_MVRP policy<{'amd64': 'y', 'arm64': 'y', 'armhf': 'y', 'ppc64el': 'y', 'riscv64': 'y', 's390x': 'y'}>
CONFIG_VMAP_PFN policy<{'amd64': 'y', 'arm64': '-'}>
-CONFIG_VMAP_STACK policy<{'amd64': 'y', 'arm64': 'y', 'armhf': 'y', 'riscv64': 'n', 's390x': 'y'}>
+CONFIG_VMAP_STACK policy<{'amd64': 'y', 'arm64': 'y', 'armhf': 'y', 'riscv64': 'y', 's390x': 'y'}>
CONFIG_VMCP policy<{'s390x': 'y'}>
CONFIG_VMCP_CMA_SIZE policy<{'s390x': '4'}>
CONFIG_VMD policy<{'amd64': 'm'}>
BugLink: https://bugs.launchpad.net/bugs/1967130 On RISC-V there used to be a problem with accessing the EFI runtime services/variables if the kernel was configured with CONFIG_VMAP_STACK=y. This issue should now be resolved with the following upstream commit, so let's enable virtually mapped stacks again: 3f105a742725 ("riscv: Sync efi page table's kernel mappings before switching") Signed-off-by: Emil Renner Berthing <emil.renner.berthing@canonical.com> --- debian.master/config/annotations | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)