APPLIED: [SRU][S/R/N:linux-azure][PULL v2] C200 Plan and Patches

John Cabaj john.cabaj at canonical.com
Fri Sep 11 21:57:00 UTC 2026


On 9/9/26 8:05 PM, John Cabaj wrote:
> BugLink: https://bugs.launchpad.net/bugs/2146641
> 
> SRU Justification
> 
> [Impact]
> 
> * Microsoft requested patches to support new Cobalt 200 network-optimzed 
> SKUs
> 
> [Fix]
> 
> * Stonking
>    - Cherry-pick the following linux-next patches:
>      - d52f80731055: "net: mana: refactor mana_get_strings() and 
> mana_get_sset_count() to use switch"
>      - 5b5cb75fb86a: "net: mana: force full-page RX buffers via ethtool 
> private flag"
>      - 55d20f50a221: "net: mana: Extend RX CQE coalescing up to 8 packets"
>    - Backport the following linux-next patches:
>      - 433f482add31: "net: mana: Add Interrupt Moderation support"
> 
> * Resolute
>    - Cherry-pick the following upstream patches:
>      - dc3d720e12f6: "net: ethtool: add ethtool COALESCE_RX_CQE_FRAMES/ 
> NSECS"
>      - d01440e10a82: "net: mana: Add ethtool counters for RX CQEs in 
> coalesced type"
>      - 45b2b84ac6fd: "net: mana: Set default number of queues to 16"
>      - fb4b4a05aeeb: "net: mana: Use at least SZ_4K in doorbell ID range 
> check"
>      - 95084f1883a7: "net: mana: Fix crash from unvalidated SHM offset 
> read from BAR0 during FLR"
>      - fa1a3b7bcd16: "net: mana: Create separate EQs for each vPort"
>      - 55d20f50a221: "net: mana: Extend RX CQE coalescing up to 8 packets"
>    - Backport the following upstream patches:
>      - c2fe3ff3d66d: "net: mana: Add support for RX CQE Coalescing"
>      - 89fe91c65992: "net: mana: hardening: Validate doorbell ID from 
> GDMA_REGISTER_DEVICE response"
>    - Cherry-pick the following linux-next patches:
>      - d52f80731055: "net: mana: refactor mana_get_strings() and 
> mana_get_sset_count() to use switch"
>    - Backport the following linux-next patches:
>      - 433f482add31: "net: mana: Add Interrupt Moderation support"
>      - 5b5cb75fb86a: "net: mana: force full-page RX buffers via ethtool 
> private flag"
> 
> * Noble
>    - Cherry-pick the following upstream patches:
>      - d01440e10a82: "net: mana: Add ethtool counters for RX CQEs in 
> coalesced type"
>      - 45b2b84ac6fd: "net: mana: Set default number of queues to 16"
>      - f73896b4197e: "net: mana: Fix RX skb truesize accounting"
>      - fb4b4a05aeeb: "net: mana: Use at least SZ_4K in doorbell ID range 
> check"
>      - 95084f1883a7: "net: mana: Fix crash from unvalidated SHM offset 
> read from BAR0 during FLR"
>      - 5b05aa36ee24: "net: mana: Skip redundant detach on already- 
> detached port"
>      - 2e2a83b4998a: "net: mana: Validate the packet length reported by 
> the NIC"
>    - Backport the following upstream patches:
>      - dc3d720e12f6: "net: ethtool: add ethtool COALESCE_RX_CQE_FRAMES/ 
> NSECS"
>      - c2fe3ff3d66d: "net: mana: Add support for RX CQE Coalescing"
>      - 89fe91c65992: "net: mana: hardening: Validate doorbell ID from 
> GDMA_REGISTER_DEVICE response"
>      - 17bfe0a8c014: "net: mana: Add NULL guards in teardown path to 
> prevent panic on attach failure"
>      - c72a0f09c57f: "net: mana: Sync page pool RX frags for CPU"
>    - Backport the following linux-next patches:
>      - 433f482add31: "net: mana: Add Interrupt Moderation support"
>      - d52f80731055: "net: mana: refactor mana_get_strings() and 
> mana_get_sset_count() to use switch"
>      - 5b5cb75fb86a: "net: mana: force full-page RX buffers via ethtool 
> private flag"
>      - 55d20f50a221: "net: mana: Extend RX CQE coalescing up to 8 packets"
>    - SAUCE patch
>      - "UBUNTU: [SAUCE] azure: Adding channel_changing flag to prevent 
> RDMA from claiming port during detach/attach"
> 
> [Test Plan]
> 
> * Compile tested
> * Microsoft tested
> 
> [Regression potential]
> 
> * Patches largely isolated to MANA specifically. Possibly regression 
> could result in unexpected behavior of MANA driver. Other changes in 
> ethtool simply added two new parameters. Users of previous versions of 
> ethtool could see compatibility issues, but ethtool is being updated to 
> account for this as part of the bug.
> 
> [Other info]
> 
> * SF#00442740
> * SF#00437476
> * SF#00433126
> * SF#00444116
> * SF#00432536
> * SF#00444088
> 
> ---------------------------------------------------------
> 
> v2: Including fb4b4a05aeeb: "net: mana: Use at least SZ_4K in doorbell 
> ID range check" as fix commit for 89fe91c65992: "net: mana: hardening: 
> Validate doorbell ID from GDMA_REGISTER_DEVICE response". Removing some 
> commits already since added to Resolute

Applied to Stonking, Resolute, and Noble linux-azure master-next branches.


Thanks,
j-c





More information about the kernel-team mailing list