Skip to content

Conversation

PlaidCat
Copy link
Collaborator

@PlaidCat PlaidCat commented Sep 8, 2025

Update process (This kernel CentOS base for 6.12.0-55)

  • Kernel History Rebuild Process for all src.rpms hosted by RESF
  • Create sig-cloud-10/6.12.0-55.X.1.el10_0 branch
  • Check if any maintained code is included in the new el release.
  • Cherry-pick all code from previous branch into new branch (skipping unneeded code)
    • Fix conflicts as they arise
  • Build and Test

Removed Commits

None

Forward Port Process

[jmaple@devbox code]$ cat RR.resf_kernel-6.12.0-55.30.1.el10_0.log
[rolling release update] Rolling Product:  sig-cloud-10
[rolling release update] Checking out branch:  sig-cloud-10/6.12.0-55.27.1.el10_0
[rolling release update] Gathering all the RESF kernel Tags
b'9c864bb5ae3f (tag: resf_kernel-6.12.0-55.27.1.el10_0) Rebuild rocky10_0 with kernel-6.12.0-55.27.1.el10_0'
b'487af0f6f40e (tag: resf_kernel-6.12.0-55.25.1.el10_0) Rebuild rocky10_0 with kernel-6.12.0-55.25.1.el10_0'
b'ffbe2344d41a (tag: resf_kernel-6.12.0-55.24.1.el10_0) Rebuild rocky10_0 with kernel-6.12.0-55.24.1.el10_0'
b'9b9ae5b20f34 (tag: resf_kernel-6.12.0-55.22.1.el10_0) Rebuild rocky10_0 with kernel-6.12.0-55.22.1.el10_0'
b'fef28841a44f (tag: resf_kernel-6.12.0-55.21.1.el10_0) Rebuild rocky10_0 with kernel-6.12.0-55.21.1.el10_0'
b'3381775694c1 (tag: resf_kernel-6.12.0-55.20.1.el10_0) Rebuild rocky10_0 with kernel-6.12.0-55.20.1.el10_0'
b'072c27213755 (tag: resf_kernel-6.12.0-55.19.1.el10_0, origin/sig-cloud-10/6.12.0-55.19.1.el10_0) Rebuild rocky10_0 with kernel-6.12.0-55.19.1.el10_0'
b'4de01b5748c7 (tag: resf_kernel-6.12.0-55.18.1.el10_0) Rebuild rocky10_0 with kernel-6.12.0-55.18.1.el10_0'
b'71d4955b6748 (tag: resf_kernel-6.12.0-55.17.1.el10_0) Rebuild rocky10_0 with kernel-6.12.0-55.17.1.el10_0'
b'31b726f7bb14 (tag: resf_kernel-6.12.0-55.16.1.el10_0) Rebuild rocky10_0 with kernel-6.12.0-55.16.1.el10_0'
b'defbb7341054 (tag: resf_kernel-6.12.0-55.14.1.el10_0) Rebuild rocky10_0 with kernel-6.12.0-55.14.1.el10_0'
b'abf881e2d199 (tag: resf_kernel-6.12.0-55.13.1.el10_0) Rebuild rocky10_0 with kernel-6.12.0-55.13.1.el10_0'
b'd3c6fc1a3a45 (tag: resf_kernel-6.12.0-55.12.1.el10_0) Rebuild rocky10_0 with kernel-6.12.0-55.12.1.el10_0'
b'ce19035f5d30 (tag: resf_kernel-6.12.0-55.11.1.el10_0) Rebuild rocky10_0 with kernel-6.12.0-55.11.1.el10_0'
[rolling release update] Old Rolling Branch Tags:  [b'9c864bb5ae3f', b'487af0f6f40e', b'ffbe2344d41a', b'9b9ae5b20f34', b'fef28841a44f', b'3381775694c1', b'072c27213755', b'4de01b5748c7', b'71d4955b6748', b'31b726f7bb14', b'defbb7341054', b'abf881e2d199', b'd3c6fc1a3a45', b'ce19035f5d30']
[rolling release update] Checking out branch:  rocky10_0
[rolling release update] Gathering all the RESF kernel Tags
b'0b50c952cd24 (HEAD -> rocky10_0, tag: resf_kernel-6.12.0-55.30.1.el10_0, origin/rocky10_0) Rebuild rocky10_0 with kernel-6.12.0-55.30.1.el10_0'
b'065ddba2712a (tag: resf_kernel-6.12.0-55.29.1.el10_0) Rebuild rocky10_0 with kernel-6.12.0-55.29.1.el10_0'
b'9c864bb5ae3f (tag: resf_kernel-6.12.0-55.27.1.el10_0) Rebuild rocky10_0 with kernel-6.12.0-55.27.1.el10_0'
b'487af0f6f40e (tag: resf_kernel-6.12.0-55.25.1.el10_0) Rebuild rocky10_0 with kernel-6.12.0-55.25.1.el10_0'
b'ffbe2344d41a (tag: resf_kernel-6.12.0-55.24.1.el10_0) Rebuild rocky10_0 with kernel-6.12.0-55.24.1.el10_0'
b'9b9ae5b20f34 (tag: resf_kernel-6.12.0-55.22.1.el10_0) Rebuild rocky10_0 with kernel-6.12.0-55.22.1.el10_0'
b'fef28841a44f (tag: resf_kernel-6.12.0-55.21.1.el10_0) Rebuild rocky10_0 with kernel-6.12.0-55.21.1.el10_0'
b'3381775694c1 (tag: resf_kernel-6.12.0-55.20.1.el10_0) Rebuild rocky10_0 with kernel-6.12.0-55.20.1.el10_0'
b'072c27213755 (tag: resf_kernel-6.12.0-55.19.1.el10_0, origin/sig-cloud-10/6.12.0-55.19.1.el10_0) Rebuild rocky10_0 with kernel-6.12.0-55.19.1.el10_0'
b'4de01b5748c7 (tag: resf_kernel-6.12.0-55.18.1.el10_0) Rebuild rocky10_0 with kernel-6.12.0-55.18.1.el10_0'
b'71d4955b6748 (tag: resf_kernel-6.12.0-55.17.1.el10_0) Rebuild rocky10_0 with kernel-6.12.0-55.17.1.el10_0'
b'31b726f7bb14 (tag: resf_kernel-6.12.0-55.16.1.el10_0) Rebuild rocky10_0 with kernel-6.12.0-55.16.1.el10_0'
b'defbb7341054 (tag: resf_kernel-6.12.0-55.14.1.el10_0) Rebuild rocky10_0 with kernel-6.12.0-55.14.1.el10_0'
b'abf881e2d199 (tag: resf_kernel-6.12.0-55.13.1.el10_0) Rebuild rocky10_0 with kernel-6.12.0-55.13.1.el10_0'
b'd3c6fc1a3a45 (tag: resf_kernel-6.12.0-55.12.1.el10_0) Rebuild rocky10_0 with kernel-6.12.0-55.12.1.el10_0'
b'ce19035f5d30 (tag: resf_kernel-6.12.0-55.11.1.el10_0) Rebuild rocky10_0 with kernel-6.12.0-55.11.1.el10_0'
[rolling release update] New Base Branch Tags:  [b'0b50c952cd24', b'065ddba2712a', b'9c864bb5ae3f', b'487af0f6f40e', b'ffbe2344d41a', b'9b9ae5b20f34', b'fef28841a44f', b'3381775694c1', b'072c27213755', b'4de01b5748c7', b'71d4955b6748', b'31b726f7bb14', b'defbb7341054', b'abf881e2d199', b'd3c6fc1a3a45', b'ce19035f5d30']
[rolling release update] Latest RESF tag sha:  b'9c864bb5ae3f'
"9c864bb5ae3fe2949e9b923b2c760d2def482860 Rebuild rocky10_0 with kernel-6.12.0-55.27.1.el10_0"
[rolling release update] Checking out old rolling branch:  sig-cloud-10/6.12.0-55.27.1.el10_0
[rolling release update] Finding the CIQ Kernel and Associated Upstream commits between the last resf tag and HEAD
[rolling release update] Last RESF tag sha:  b'9c864bb5ae3f'
[rolling release update] Total Commit in old branch:  18
{ "CIQ COMMMIT" : "UPSTREAM COMMMIT" }
Printing first 5 and last 5 commits
{
  "e39cb4e1b3856437851ca894ad874f20bcc678ec": "fbe346ce9d626680a4dd0f079e17c7b5dd32ffad",
  "fe20edda1f6bee3040d2b6ba91b7ca9f781248ad": "7768c5f417336fa58dbfef9bb7ecd7eeec6d8886",
  "b0a2a557ab2d1835ba562edbc58241416ea603d8": "c09ef59e17c6921c577d54bc8da4331b955d01a7",
  "35a4d2ebe9b2200c85017407d67593abefa4506f": "fa37a8849634db2dd3545116873da8cf4b1e67c6",
  "61070bbbb1cc281ffa3861a5a9ecfe838f7a565c": "2fc8a346625eb1abfe202062c7e6a13d76cde5ea"
}
{
  "9821f91781140e7579c0b67bee923d4299c980ba": "4f98616b855cb0e3b5917918bb07b44728eb96ea",
  "77b282e6cf2b71e8e129961223826a7db3d30238": "380b75d3078626aadd0817de61f3143f5db6e393",
  "31d6b1ef236c4332c5b35bcb17db62adb5bab4a6": "b2f966568faaad326de97481096d0f3dc0971c43",
  "1d009c12cfd9e5d81fb496eba55480c63e206e71": "a9c0b33ef2306327dd2db02c6274107065ff9307",
  "01e0eab9f051a29a749f5a0104dfee8705ac9a7f": "290e5d3c49f687c1567bde634dc33d57b0674919"
}
[rolling release update] Checking out new base branch:  rocky10_0
[rolling release update] Finding the kernel version for the new rolling release
b'0b50c952cd24 (HEAD -> rocky10_0, tag: resf_kernel-6.12.0-55.30.1.el10_0, origin/rocky10_0) Rebuild rocky10_0 with kernel-6.12.0-55.30.1.el10_0'
<re.Match object; span=(0, 71), match=b'0b50c952cd24 (HEAD -> rocky10_0, tag: resf_kerne>
[rolling release update} New Branch to create  sig-cloud-10/6.12.0-55.30.1.el10_0
[rolling release update] Check if branch Exists:  sig-cloud-10/6.12.0-55.30.1.el10_0
Branch sig-cloud-10/6.12.0-55.30.1.el10_0 does not exists creating
[rolling release update] Creating new branch for PR:  jmaple_sig-cloud-10/6.12.0-55.30.1.el10_0
[rolling release update] Creating Map of all new commits from last rolling release fork
[rolling release update] Total Commit in new branch:  38
{ "CIQ COMMMIT" : "UPSTREAM COMMMIT" }
Printing first 5 and last 5 commits
{
  "0b50c952cd24b8510ad2a4a6f60750dd5e61e08c": "",
  "110406cfc90e9eb73825b2212d82d5cc15f1fe82": "6ccbda44e2cc3d26fd22af54c650d6d5d801addf",
  "18afa2a70050a64cd849a40362f616547d0b51f8": "8691abd3afaadd816a298503ec1a759df1305d2e",
  "ae6c1fd2a012b01c1dd2b1b34d2a702cee9c8f67": "2844ddbd540fc84d7571cca65d6c43088e4d6952",
  "032c1f1e1e2209971ac9f586ccafd46ace07523a": "can use to find if a VF has a configured parent PF. Use"
}
{
  "5d17adf7430f1dc64abeba2ab2be83bdfdb07574": "9988df07dbe1ca8282f5ae95f1b534f91bab73fc",
  "b0c3370c2128f951e2bb0a5ee9bbe8c005d010e6": "1d6123102e9fbedc8d25bf4731da6d513173e49e",
  "73532d9d197bc94f64ac381b9b478bba6bacea5e": "c7f2188d68c114095660a950b7e880a1e5a71c8f",
  "8ea46bbceaf3587210d9ebc950ef836e113bfcae": "6b3d638ca897e099fa99bd6d02189d3176f80a47",
  "cde9f49e3f4d5117271ff49de3c8e400ec80ecad": "3d30048958e0d43425f6d4e76565e6249fa71050"
}
[rolling release update] Checking if any of the commits from the old rolling release are already present in the new base branch
[rolling release update] Removing commits from the new branch
[rolling release update] Applying the remaining commits to the new branch
Applying commit  "01e0eab9f051a29a749f5a0104dfee8705ac9a7f net: mana: Add support for Multi Vports on Bare metal"
Applying commit  "1d009c12cfd9e5d81fb496eba55480c63e206e71 tools: hv: Enable debug logs for hv_kvp_daemon"
Applying commit  "31d6b1ef236c4332c5b35bcb17db62adb5bab4a6 scsi: storvsc: Increase the timeouts to storvsc_timeout"
Applying commit  "77b282e6cf2b71e8e129961223826a7db3d30238 Drivers: hv: Allow vmbus_sendpacket_mpb_desc() to create multiple ranges"
Applying commit  "9821f91781140e7579c0b67bee923d4299c980ba hv_netvsc: Use vmbus_sendpacket_mpb_desc() to send VMBus messages"
Applying commit  "061ba67b9f27515f5941d18206f950f98f9e1f3f hv_netvsc: Preserve contiguous PFN grouping in the page buffer array"
Applying commit  "fd52bd96574bb85942894053aa4668be9bac1bb9 hv_netvsc: Remove rmsg_pgcnt"
Applying commit  "a393007a2159764fb81335d8829846dc82e44b9d Drivers: hv: vmbus: Remove vmbus_sendpacket_pagebuffer()"
Applying commit  "66a96989a5d0a918ec9c616d239a5e9442251a5e hv_netvsc: Use VF's tso_max_size value when data path is VF"
Applying commit  "f1f30f8656a0579a9c2c3474285b39e4c2506992 net: mana: Allow tso_max_size to go up-to GSO_MAX_SIZE"
Applying commit  "85753b7c000c92f56d77b797817d399a98cecb73 net: mana: Add debug logs in MANA network driver"
Applying commit  "195c475f34a03340a9d75d3ccfebfd301caba28c net: mana: Change the function signature of mana_get_primary_netdev_rcu"
Applying commit  "427803e21f864f0d44631a23c888658712d9245c RDMA/mana_ib: Handle net event for pointing to the current netdev"
Applying commit  "61070bbbb1cc281ffa3861a5a9ecfe838f7a565c net: mana: Support holes in device list reply msg"
Applying commit  "35a4d2ebe9b2200c85017407d67593abefa4506f net: mana: Switch to page pool for jumbo frames"
Applying commit  "b0a2a557ab2d1835ba562edbc58241416ea603d8 net: mana: Expose additional hardware counters for drop and TC via ethtool."
Applying commit  "fe20edda1f6bee3040d2b6ba91b7ca9f781248ad net: mana: Add handler for hardware servicing events"
Applying commit  "e39cb4e1b3856437851ca894ad874f20bcc678ec net: mana: Handle Reset Request from MANA NIC"

Build

[jmaple@devbox code]$ egrep -B 5 -A 5 "\[TIMER\]|^Starting Build" $(ls -t kbuild* | head -n1)
/mnt/code/kernel-src-tree-build
Running make mrproper...
[TIMER]{MRPROPER}: 6s
x86_64 architecture detected, copying config
'configs/kernel-x86_64-rhel.config' -> '.config'
Setting Local Version for build
CONFIG_LOCALVERSION="-jmaple_sig-cloud-10_6.12.0-55.30.1.el10_0-cdc6b6f80cf"
Making olddefconfig
--
  HOSTCC  scripts/kconfig/util.o
  HOSTLD  scripts/kconfig/conf
#
# configuration written to .config
#
Starting Build
  GEN     arch/x86/include/generated/asm/orc_hash.h
  WRAP    arch/x86/include/generated/uapi/asm/bpf_perf_event.h
  WRAP    arch/x86/include/generated/uapi/asm/errno.h
  WRAP    arch/x86/include/generated/uapi/asm/fcntl.h
  WRAP    arch/x86/include/generated/uapi/asm/ioctl.h
--
  LD [M]  net/qrtr/qrtr.ko
  BTF [M] net/hsr/hsr.ko
  LD [M]  net/qrtr/qrtr-mhi.ko
  BTF [M] net/qrtr/qrtr.ko
  BTF [M] net/qrtr/qrtr-mhi.ko
[TIMER]{BUILD}: 2072s
Making Modules
  SYMLINK /lib/modules/6.12.0-jmaple_sig-cloud-10_6.12.0-55.30.1.el10_0-cdc6b6f80cf+/build
  INSTALL /lib/modules/6.12.0-jmaple_sig-cloud-10_6.12.0-55.30.1.el10_0-cdc6b6f80cf+/modules.order
  INSTALL /lib/modules/6.12.0-jmaple_sig-cloud-10_6.12.0-55.30.1.el10_0-cdc6b6f80cf+/modules.builtin
  INSTALL /lib/modules/6.12.0-jmaple_sig-cloud-10_6.12.0-55.30.1.el10_0-cdc6b6f80cf+/modules.builtin.modinfo
--
  STRIP   /lib/modules/6.12.0-jmaple_sig-cloud-10_6.12.0-55.30.1.el10_0-cdc6b6f80cf+/kernel/net/qrtr/qrtr-mhi.ko
  SIGN    /lib/modules/6.12.0-jmaple_sig-cloud-10_6.12.0-55.30.1.el10_0-cdc6b6f80cf+/kernel/net/hsr/hsr.ko
  SIGN    /lib/modules/6.12.0-jmaple_sig-cloud-10_6.12.0-55.30.1.el10_0-cdc6b6f80cf+/kernel/net/qrtr/qrtr-mhi.ko
  SIGN    /lib/modules/6.12.0-jmaple_sig-cloud-10_6.12.0-55.30.1.el10_0-cdc6b6f80cf+/kernel/net/qrtr/qrtr.ko
  DEPMOD  /lib/modules/6.12.0-jmaple_sig-cloud-10_6.12.0-55.30.1.el10_0-cdc6b6f80cf+
[TIMER]{MODULES}: 8s
Making Install
  INSTALL /boot
[TIMER]{INSTALL}: 17s
Checking kABI
kABI check passed
Setting Default Kernel to /boot/vmlinuz-6.12.0-jmaple_sig-cloud-10_6.12.0-55.30.1.el10_0-cdc6b6f80cf+ and Index to 3
Hopefully Grub2.0 took everything ... rebooting after time metrices
[TIMER]{MRPROPER}: 6s
[TIMER]{BUILD}: 2072s
[TIMER]{MODULES}: 8s
[TIMER]{INSTALL}: 17s
[TIMER]{TOTAL} 2108s
Rebooting in 10 seconds

KselfTest

[jmaple@devbox code]$ ls -rt kselftest.* | tail -n4 | while read line; do echo $line; grep '^ok ' $line | wc -l ; done
kselftest.6.12.0-rocky10_0_rebuild-09e336dca27b+.log
498
kselftest.6.12.0-jmaple_sig-cloud-10_6.12.0-55.27.1.el10_0-7f919518cf4+.log
498
kselftest.6.12.0-rocky10_0_rebuild-0b50c952cd24+.log
497
kselftest.6.12.0-jmaple_sig-cloud-10_6.12.0-55.30.1.el10_0-cdc6b6f80cf+.log
505

PlaidCat and others added 18 commits September 8, 2025 11:56
jira LE-3208
feature net_mana
commit-author Haiyang Zhang <[email protected]>
commit 290e5d3

To support Multi Vports on Bare metal, increase the device config response
version. And, skip the register HW vport, and register filter steps, when
the Bare metal hostmode is set.

	Signed-off-by: Haiyang Zhang <[email protected]>
Link: https://patch.msgid.link/[email protected]
	Signed-off-by: Paolo Abeni <[email protected]>

(cherry picked from commit 290e5d3)
	Signed-off-by: Jonathan Maple <[email protected]>
Signed-off-by: Jonathan Maple <[email protected]>
jira LE-3207
feature tools_hv
commit-author Shradha Gupta <[email protected]>
commit a9c0b33

Allow the KVP daemon to log the KVP updates triggered in the VM
with a new debug flag(-d).
When the daemon is started with this flag, it logs updates and debug
information in syslog with loglevel LOG_DEBUG. This information comes
in handy for debugging issues where the key-value pairs for certain
pools show mismatch/incorrect values.
The distro-vendors can further consume these changes and modify the
respective service files to redirect the logs to specific files as
needed.

	Signed-off-by: Shradha Gupta <[email protected]>
	Reviewed-by: Naman Jain <[email protected]>
	Reviewed-by: Dexuan Cui <[email protected]>
Link: https://lore.kernel.org/r/1744715978-8185-1-git-send-email-shradhagupta@linux.microsoft.com
	Signed-off-by: Wei Liu <[email protected]>
Message-ID: <1744715978-8185-1-git-send-email-shradhagupta@linux.microsoft.com>
(cherry picked from commit a9c0b33)
	Signed-off-by: Jonathan Maple <[email protected]>
Signed-off-by: Jonathan Maple <[email protected]>
jira LE-3546
commit-author Dexuan Cui <[email protected]>
commit b2f9665

Currently storvsc_timeout is only used in storvsc_sdev_configure(), and
5s and 10s are used elsewhere. It turns out that rarely the 5s is not
enough on Azure, so let's use storvsc_timeout everywhere.

In case a timeout happens and storvsc_channel_init() returns an error,
close the VMBus channel so that any host-to-guest messages in the
channel's ringbuffer, which might come late, can be safely ignored.

Add a "const" to storvsc_timeout.

	Cc: [email protected]
	Signed-off-by: Dexuan Cui <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
	Reviewed-by: Long Li <[email protected]>
	Signed-off-by: Martin K. Petersen <[email protected]>
(cherry picked from commit b2f9665)
	Signed-off-by: Sultan Alsawaf <[email protected]>
Signed-off-by: Jonathan Maple <[email protected]>
jira LE-3555
commit-author Michael Kelley <[email protected]>
commit 380b75d

vmbus_sendpacket_mpb_desc() is currently used only by the storvsc driver
and is hardcoded to create a single GPA range. To allow it to also be
used by the netvsc driver to create multiple GPA ranges, no longer
hardcode as having a single GPA range. Allow the calling driver to
specify the rangecount in the supplied descriptor.

Update the storvsc driver to reflect this new approach.

	Cc: <[email protected]> # 6.1.x
	Signed-off-by: Michael Kelley <[email protected]>
Link: https://patch.msgid.link/[email protected]
	Signed-off-by: Jakub Kicinski <[email protected]>
(cherry picked from commit 380b75d)
	Signed-off-by: Shreeya Patel <[email protected]>
Signed-off-by: Jonathan Maple <[email protected]>
jira LE-3555
commit-author Michael Kelley <[email protected]>
commit 4f98616

netvsc currently uses vmbus_sendpacket_pagebuffer() to send VMBus
messages. This function creates a series of GPA ranges, each of which
contains a single PFN. However, if the rndis header in the VMBus
message crosses a page boundary, the netvsc protocol with the host
requires that both PFNs for the rndis header must be in a single "GPA
range" data structure, which isn't possible with
vmbus_sendpacket_pagebuffer(). As the first step in fixing this, add a
new function netvsc_build_mpb_array() to build a VMBus message with
multiple GPA ranges, each of which may contain multiple PFNs. Use
vmbus_sendpacket_mpb_desc() to send this VMBus message to the host.

There's no functional change since higher levels of netvsc don't
maintain or propagate knowledge of contiguous PFNs. Based on its
input, netvsc_build_mpb_array() still produces a separate GPA range
for each PFN and the behavior is the same as with
vmbus_sendpacket_pagebuffer(). But the groundwork is laid for a
subsequent patch to provide the necessary grouping.

	Cc: <[email protected]> # 6.1.x
	Signed-off-by: Michael Kelley <[email protected]>
Link: https://patch.msgid.link/[email protected]
	Signed-off-by: Jakub Kicinski <[email protected]>
(cherry picked from commit 4f98616)
	Signed-off-by: Shreeya Patel <[email protected]>
Signed-off-by: Jonathan Maple <[email protected]>
jira LE-3555
commit-author Michael Kelley <[email protected]>
commit 41a6328

Starting with commit dca5161 ("hv_netvsc: Check status in
SEND_RNDIS_PKT completion message") in the 6.3 kernel, the Linux
driver for Hyper-V synthetic networking (netvsc) occasionally reports
"nvsp_rndis_pkt_complete error status: 2".[1] This error indicates
that Hyper-V has rejected a network packet transmit request from the
guest, and the outgoing network packet is dropped. Higher level
network protocols presumably recover and resend the packet so there is
no functional error, but performance is slightly impacted. Commit
dca5161 is not the cause of the error -- it only added reporting
of an error that was already happening without any notice. The error
has presumably been present since the netvsc driver was originally
introduced into Linux.

The root cause of the problem is that the netvsc driver in Linux may
send an incorrectly formatted VMBus message to Hyper-V when
transmitting the network packet. The incorrect formatting occurs when
the rndis header of the VMBus message crosses a page boundary due to
how the Linux skb head memory is aligned. In such a case, two PFNs are
required to describe the location of the rndis header, even though
they are contiguous in guest physical address (GPA) space. Hyper-V
requires that two rndis header PFNs be in a single "GPA range" data
struture, but current netvsc code puts each PFN in its own GPA range,
which Hyper-V rejects as an error.

The incorrect formatting occurs only for larger packets that netvsc
must transmit via a VMBus "GPA Direct" message. There's no problem
when netvsc transmits a smaller packet by copying it into a pre-
allocated send buffer slot because the pre-allocated slots don't have
page crossing issues.

After commit 14ad6ed ("net: allow small head cache usage with
large MAX_SKB_FRAGS values") in the 6.14-rc4 kernel, the error occurs
much more frequently in VMs with 16 or more vCPUs. It may occur every
few seconds, or even more frequently, in an ssh session that outputs a
lot of text. Commit 14ad6ed subtly changes how skb head memory is
allocated, making it much more likely that the rndis header will cross
a page boundary when the vCPU count is 16 or more. The changes in
commit 14ad6ed are perfectly valid -- they just had the side
effect of making the netvsc bug more prominent.

Current code in init_page_array() creates a separate page buffer array
entry for each PFN required to identify the data to be transmitted.
Contiguous PFNs get separate entries in the page buffer array, and any
information about contiguity is lost.

Fix the core issue by having init_page_array() construct the page
buffer array to represent contiguous ranges rather than individual
pages. When these ranges are subsequently passed to
netvsc_build_mpb_array(), it can build GPA ranges that contain
multiple PFNs, as required to avoid the error "nvsp_rndis_pkt_complete
error status: 2". If instead the network packet is sent by copying
into a pre-allocated send buffer slot, the copy proceeds using the
contiguous ranges rather than individual pages, but the result of the
copying is the same. Also fix rndis_filter_send_request() to construct
a contiguous range, since it has its own page buffer array.

This change has a side benefit in CoCo VMs in that netvsc_dma_map()
calls dma_map_single() on each contiguous range instead of on each
page. This results in fewer calls to dma_map_single() but on larger
chunks of memory, which should reduce contention on the swiotlb.

Since the page buffer array now contains one entry for each contiguous
range instead of for each individual page, the number of entries in
the array can be reduced, saving 208 bytes of stack space in
netvsc_xmit() when MAX_SKG_FRAGS has the default value of 17.

[1] https://bugzilla.kernel.org/show_bug.cgi?id=217503

Closes: https://bugzilla.kernel.org/show_bug.cgi?id=217503
	Cc: <[email protected]> # 6.1.x
	Signed-off-by: Michael Kelley <[email protected]>
Link: https://patch.msgid.link/[email protected]
	Signed-off-by: Jakub Kicinski <[email protected]>
(cherry picked from commit 41a6328)
	Signed-off-by: Shreeya Patel <[email protected]>
Signed-off-by: Jonathan Maple <[email protected]>
jira LE-3555
commit-author Michael Kelley <[email protected]>
commit 5bbc644

init_page_array() now always creates a single page buffer array entry
for the rndis message, even if the rndis message crosses a page
boundary. As such, the number of page buffer array entries used for
the rndis message must no longer be tracked -- it is always just 1.
Remove the rmsg_pgcnt field and use "1" where the value is needed.

	Cc: <[email protected]> # 6.1.x
	Signed-off-by: Michael Kelley <[email protected]>
Link: https://patch.msgid.link/[email protected]
	Signed-off-by: Jakub Kicinski <[email protected]>
(cherry picked from commit 5bbc644)
	Signed-off-by: Shreeya Patel <[email protected]>
Signed-off-by: Jonathan Maple <[email protected]>
jira LE-3555
commit-author Michael Kelley <[email protected]>
commit 45a442f

With the netvsc driver changed to use vmbus_sendpacket_mpb_desc()
instead of vmbus_sendpacket_pagebuffer(), the latter has no remaining
callers. Remove it.

	Cc: <[email protected]> # 6.1.x
	Signed-off-by: Michael Kelley <[email protected]>
Link: https://patch.msgid.link/[email protected]
	Signed-off-by: Jakub Kicinski <[email protected]>
(cherry picked from commit 45a442f)
	Signed-off-by: Shreeya Patel <[email protected]>
Signed-off-by: Jonathan Maple <[email protected]>
jira LE-3886
commit-author Shradha Gupta <[email protected]>
commit 6859209

On Azure, increasing VF's gso/gro packet size to up-to GSO_MAX_SIZE
is not possible without allowing the same for netvsc NIC
(as the NICs are bonded together). For bonded NICs, the min of the max
aggregated pkt size of the members is propagated in the stack.

Therefore, we use netif_set_tso_max_size() to set max aggregated pkt size
to VF's packet size for netvsc too, when the data path is switched over
to the VF
Tested on azure env with Accelerated Networking enabled and disabled.

	Signed-off-by: Shradha Gupta <[email protected]>
	Reviewed-by: Haiyang Zhang <[email protected]>
	Signed-off-by: David S. Miller <[email protected]>
(cherry picked from commit 6859209)
	Signed-off-by: Shreeya Patel <[email protected]>
Signed-off-by: Jonathan Maple <[email protected]>
jira LE-3886
commit-author Shradha Gupta <[email protected]>
commit 2731583

Allow the max aggregated pkt size to go up-to GSO_MAX_SIZE for MANA NIC.
This patch only increases the max allowable gso/gro pkt size for MANA
devices and does not change the defaults.
Following are the perf benefits by increasing the pkt aggregate size from
legacy gso_max_size value(64K) to newer one(up-to 511K

IPv4 tests
for i in {1..10}; do netperf -t TCP_RR  -H 10.0.0.5 -p50000 -- -r80000,80000
-O MIN_LATENCY,P90_LATENCY,P99_LATENCY,THROUGHPUT|tail -1; done

min	p90	p99	Throughput		gso_max_size
93	171	194	6594.25
97	154	180	7183.74
95	165	189	6927.86
96	165	188	6976.04
93	154	185	7338.05			64K
93	168	189	6938.03
94	169	189	6784.93
92	166	189	7117.56
94	179	191	6678.44
95	157	183	7277.81

min	p90	p99	Throughput
93	134	146	8448.75
95	134	140	8396.54
94	137	148	8204.12
94	137	148	8244.41
94	128	139	8666.52			80K
94	141	153	8116.86
94	138	149	8163.92
92	135	142	8362.72
92	134	142	8497.57
93	136	148	8393.23

IPv6 Tests
for i in {1..10}; do netperf -t TCP_RR  -H fd00:9013:cadd::4 -p50000 --
-r80000,80000 -O MIN_LATENCY,P90_LATENCY,P99_LATENCY,THROUGHPUT|tail -1; done

min	p90	p99	Throughput		gso_max_size
108	165	170	6673.2
101	169	189	6451.69
101	165	169	6737.65
102	167	175	6614.64
101	178	189	6247.13			64K
107	163	169	6678.63
106	176	187	6350.86
100	164	169	6617.36
102	163	170	6849.21
102	168	175	6605.7

min	p90	p99	Throughput
108	155	166	7183
110	154	163	7268.87
109	152	159	7434.35
107	145	157	7569.15
107	149	164	7496.17			80K
110	154	159	7245.85
108	156	162	7266.24
109	145	158	7526.66
106	145	151	7785.75
111	148	157	7246.65

Tested on azure env with Accelerated Networking enabled and disabled.

	Signed-off-by: Shradha Gupta <[email protected]>
	Reviewed-by: Haiyang Zhang <[email protected]>
	Signed-off-by: David S. Miller <[email protected]>
(cherry picked from commit 2731583)
	Signed-off-by: Shreeya Patel <[email protected]>
Signed-off-by: Jonathan Maple <[email protected]>
jira LE-3890
commit-author Erni Sri Satya Vennela <[email protected]>
commit 47dfd7a

Add more logs to assist in debugging and monitoring
driver behaviour, making it easier to identify potential
issues  during development and testing.

	Signed-off-by: Erni Sri Satya Vennela <[email protected]>
	Reviewed-by: Haiyang Zhang <[email protected]>
Link: https://patch.msgid.link/[email protected]
	Signed-off-by: Jakub Kicinski <[email protected]>
(cherry picked from commit 47dfd7a)
	Signed-off-by: Shreeya Patel <[email protected]>
Signed-off-by: Jonathan Maple <[email protected]>
jira LE-3894
commit-author Long Li <[email protected]>
commit a8445cf

Change mana_get_primary_netdev_rcu() to mana_get_primary_netdev(), and
return the ndev with refcount held. The caller is responsible for dropping
the refcount.

Also drop the check for IFF_SLAVE as it is not necessary if the upper
device is present.

	Signed-off-by: Long Li <[email protected]>
Link: https://patch.msgid.link/[email protected]
	Signed-off-by: Leon Romanovsky <[email protected]>
(cherry picked from commit a8445cf)
	Signed-off-by: Shreeya Patel <[email protected]>
Signed-off-by: Shreeya Patel <[email protected]>
Signed-off-by: Jonathan Maple <[email protected]>
jira LE-3894
commit-author Long Li <[email protected]>
commit bee35b7
upstream-diff There were conflicts when applying this patch
due to the following missing commits :-
79bccd7 ("RDMA/mana_ib: Add port statistics support")
df91c47 ("RDMA/mana_ib: create/destroy AH")

When running under Hyper-V, the master device to the RDMA device is always
bonded to this RDMA device. This is not user-configurable.

The master device can be unbind/bind from the kernel. During those events,
the RDMA device should set to the current netdev to reflect the change of
master device from those events.

	Signed-off-by: Long Li <[email protected]>
Link: https://patch.msgid.link/[email protected]
	Signed-off-by: Leon Romanovsky <[email protected]>
(cherry picked from commit bee35b7)
	Signed-off-by: Shreeya Patel <[email protected]>
Signed-off-by: Jonathan Maple <[email protected]>
jira LE-3904
commit-author Haiyang Zhang <[email protected]>
commit 2fc8a34

According to GDMA protocol, holes (zeros) are allowed at the beginning
or middle of the gdma_list_devices_resp message. The existing code
cannot properly handle this, and may miss some devices in the list.

To fix, scan the entire list until the num_of_devs are found, or until
the end of the list.

	Cc: [email protected]
Fixes: ca9c54d ("net: mana: Add a driver for Microsoft Azure Network Adapter (MANA)")
	Signed-off-by: Haiyang Zhang <[email protected]>
	Reviewed-by: Long Li <[email protected]>
	Reviewed-by: Shradha Gupta <[email protected]>
	Reviewed-by: Michal Swiatkowski <[email protected]>
Link: https://patch.msgid.link/[email protected]
	Signed-off-by: Paolo Abeni <[email protected]>

(cherry picked from commit 2fc8a34)
	Signed-off-by: Shreeya Patel <[email protected]>
Signed-off-by: Jonathan Maple <[email protected]>
jira LE-3908
commit-author Haiyang Zhang <[email protected]>
commit fa37a88

Frag allocators, such as netdev_alloc_frag(), were not designed to
work for fragsz > PAGE_SIZE.

So, switch to page pool for jumbo frames instead of using page frag
allocators. This driver is using page pool for smaller MTUs already.

	Cc: [email protected]
Fixes: 80f6215 ("net: mana: Add support for jumbo frame")
	Signed-off-by: Haiyang Zhang <[email protected]>
	Reviewed-by: Long Li <[email protected]>
	Reviewed-by: Shradha Gupta <[email protected]>
Link: https://patch.msgid.link/[email protected]
	Signed-off-by: Jakub Kicinski <[email protected]>
(cherry picked from commit fa37a88)
	Signed-off-by: Shreeya Patel <[email protected]>
Signed-off-by: Jonathan Maple <[email protected]>
…htool.

jira LE-3916
commit-author Dipayaan Roy <[email protected]>
commit c09ef59

Add support for reporting additional hardware counters for drop and
TC using the ethtool -S interface.

These counters include:

- Aggregate Rx/Tx drop counters
- Per-TC Rx/Tx packet counters
- Per-TC Rx/Tx byte counters
- Per-TC Rx/Tx pause frame counters

The counters are exposed using ethtool_ops->get_ethtool_stats and
ethtool_ops->get_strings. This feature/counters are not available
to all versions of hardware.

	Signed-off-by: Dipayaan Roy <[email protected]>
	Reviewed-by: Subbaraya Sundeep <[email protected]>
	Reviewed-by: Haiyang Zhang <[email protected]>
Link: https://patch.msgid.link/20250609100103.GA7102@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net
	Signed-off-by: Jakub Kicinski <[email protected]>
(cherry picked from commit c09ef59)
	Signed-off-by: Shreeya Patel <[email protected]>
Signed-off-by: Jonathan Maple <[email protected]>
jira LE-3920
commit-author Haiyang Zhang <[email protected]>
commit 7768c5f

To collaborate with hardware servicing events, upon receiving the special
EQE notification from the HW channel, remove the devices on this bus.
Then, after a waiting period based on the device specs, rescan the parent
bus to recover the devices.

	Signed-off-by: Haiyang Zhang <[email protected]>
	Reviewed-by: Shradha Gupta <[email protected]>
	Reviewed-by: Simon Horman <[email protected]>
Link: https://patch.msgid.link/[email protected]
	Signed-off-by: Jakub Kicinski <[email protected]>
(cherry picked from commit 7768c5f)
	Signed-off-by: Shreeya Patel <[email protected]>
Signed-off-by: Jonathan Maple <[email protected]>
jira LE-3924
commit-author Haiyang Zhang <[email protected]>
commit fbe346c
upstream-diff There were conflicts seen when applying this
patch due to the following missing commits :-
ca8ac48 ("net: mana: Handle unsupported HWC commands")
505cc26 ("net: mana: Add support for auxiliary device servicing
events")

Upon receiving the Reset Request, pause the connection and clean up
queues, wait for the specified period, then resume the NIC.
In the cleanup phase, the HWC is no longer responding, so set hwc_timeout
to zero to skip waiting on the response.

	Signed-off-by: Haiyang Zhang <[email protected]>
Link: https://patch.msgid.link/[email protected]
	Signed-off-by: Jakub Kicinski <[email protected]>
(cherry picked from commit fbe346c)
	Signed-off-by: Shreeya Patel <[email protected]>
Signed-off-by: Jonathan Maple <[email protected]>
Copy link
Collaborator

@bmastbergen bmastbergen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🥌

Copy link

@jdieter jdieter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@PlaidCat PlaidCat merged commit cdc6b6f into sig-cloud-10/6.12.0-55.30.1.el10_0 Sep 8, 2025
4 checks passed
@PlaidCat PlaidCat deleted the jmaple_sig-cloud-10/6.12.0-55.30.1.el10_0 branch September 8, 2025 21:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

5 participants