APPLIED: [SRU][N:aws/Q:aws/R:aws][PATCH 0/1] UBUNTU: [Config] Revert ENA to be a loadable module on AWS

Magali Lemes magali.lemes.do.sacramento at canonical.com
Tue Jun 30 16:19:46 UTC 2026


On 6/16/26 17:37, Leah Goldberg via kernel-team wrote:

> BugLink: https://bugs.launchpad.net/bugs/2156924
>
> [ Impact ]
>
> * The previous change made the ENA driver built-in to the kernel
>    in order to mitigate a cloud-init early boot race condition on
>    AWS instances (LP #2144694).
>
> * This change introduced a regression for users who ship custom or
>    upstream AWS ENA drivers via DKMS, as the built-in driver cannot
>    be overridden by out-of-tree modules.
>
> * This SRU reverts ENA from built-in back to a loadable kernel
>    module, restoring the expected module override behavior.
>
> [ Test Plan ]
>
>   * 1. Launch an AWS instance using a kernel with this revert applied.
>
>   * 2. Verify ENA is built as a loadable module:
>        "grep CONFIG_ENA /boot/config-$(uname -r)"
>        Expected result: "CONFIG_ENA_ETHERNET=m".
>
> [ Where problems could occur ]
>
>   * Reverting ENA to a module may reintroduce or increase exposure to
>     a known timing issue where cloud-init local runs before NIC initialization
>     completes. This can affect datasource detection timing on some AWS instance
>     types (e.g. notably hpc7a.*), potentially delaying metadata availability
>     during first boot (LP #2144694).
>
> [ Other Info ]
>
>   * This change is the result of a regression introduced by LP #2144694.
>
> Leah Goldberg (1):
>    Revert ENA_ETHERNET to a loadable module
>
>   debian.aws/config/annotations | 3 ---
>   1 file changed, 3 deletions(-)
>
Applied to resolute:linux-aws/master-next, 
questing:linux-aws/master-next, and noble:linux-aws/master-next (with 
some context adjustment for the last two).
Thanks!

Magali





More information about the kernel-team mailing list