Skip to content

Conversation

@shreeya-patel98
Copy link
Collaborator

Update process (This kernel CentOS base for 5.14.0-570)

  • Kernel History Rebuild Process for all src.rpms hosted by RESF
  • Create sig-cloud-9/5.14.0-570.X.1.el9_6 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

shreeya@spatel-dev-bom:~/ciq/workspace/sig-cloud-9/kernel-src-tree-tools$ python3 rolling-release-update.py --repo ../kernel-src-tree/ --new-base-branch rocky9_6 --old-rolling-branch sig-cloud-9/5.14.0-570.49.1.el9_6
[rolling release update] Rolling Product:  sig-cloud-9
[rolling release update] Checking out branch:  sig-cloud-9/5.14.0-570.49.1.el9_6
[rolling release update] Gathering all the RESF kernel Tags
b'6be68ff1dc33 (tag: resf_kernel-5.14.0-570.49.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.49.1.el9_6'
b'7d4826997117 (tag: resf_kernel-5.14.0-570.46.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.46.1.el9_6'
b'4eb20e218dc1 (tag: resf_kernel-5.14.0-570.42.2.el9_6, origin/rocky9_6_rebuild) Rebuild rocky9_6 with kernel-5.14.0-570.42.2.el9_6'
b'4d2fb3e9de8a (tag: resf_kernel-5.14.0-570.41.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.41.1.el9_6'
b'1b9ea68b26cf (tag: resf_kernel-5.14.0-570.39.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.39.1.el9_6'
b'6ad42715f2bf (tag: resf_kernel-5.14.0-570.37.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.37.1.el9_6'
b'0564e55498d2 (tag: resf_kernel-5.14.0-570.32.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.32.1.el9_6'
b'e0a1a84bc26b (tag: resf_kernel-5.14.0-570.30.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.30.1.el9_6'
b'9fbeb8c24bbd (tag: resf_kernel-5.14.0-570.28.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.28.1.el9_6'
b'8cc6f289778f (tag: resf_kernel-5.14.0-570.26.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.26.1.el9_6'
b'cad0cbcb03be (tag: resf_kernel-5.14.0-570.25.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.25.1.el9_6'
b'4743a27158ca (tag: resf_kernel-5.14.0-570.24.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.24.1.el9_6'
b'08b6475feb07 (tag: resf_kernel-5.14.0-570.23.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.23.1.el9_6'
b'667004a38548 (tag: resf_kernel-5.14.0-570.22.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.22.1.el9_6'
b'9477e3364951 (tag: resf_kernel-5.14.0-570.21.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.21.1.el9_6'
b'b94108159618 (tag: resf_kernel-5.14.0-570.19.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.19.1.el9_6'
b'e8b954c95fef (tag: resf_kernel-5.14.0-570.18.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.18.1.el9_6'
b'838cd1e8d046 (tag: resf_kernel-5.14.0-570.17.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.17.1.el9_6'
b'171ceb527773 (tag: resf_kernel-5.14.0-570.16.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.16.1.el9_6'
b'18c0812a6563 (tag: resf_kernel-5.14.0-570.12.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.12.1.el9_6'
[rolling release update] Old Rolling Branch Tags:  [b'6be68ff1dc33', b'7d4826997117', b'4eb20e218dc1', b'4d2fb3e9de8a', b'1b9ea68b26cf', b'6ad42715f2bf', b'0564e55498d2', b'e0a1a84bc26b', b'9fbeb8c24bbd', b'8cc6f289778f', b'cad0cbcb03be', b'4743a27158ca', b'08b6475feb07', b'667004a38548', b'9477e3364951', b'b94108159618', b'e8b954c95fef', b'838cd1e8d046', b'171ceb527773', b'18c0812a6563']
[rolling release update] Checking out branch:  rocky9_6
[rolling release update] Gathering all the RESF kernel Tags
b'c18abab0e029 (HEAD -> rocky9_6, tag: resf_kernel-5.14.0-570.52.1.el9_6, origin/rocky9_6, origin/fips-9-compliant/5.14.0-570.52.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.52.1.el9_6'
b'eed76cad25c1 (tag: resf_kernel-5.14.0-570.51.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.51.1.el9_6'
b'6be68ff1dc33 (tag: resf_kernel-5.14.0-570.49.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.49.1.el9_6'
b'7d4826997117 (tag: resf_kernel-5.14.0-570.46.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.46.1.el9_6'
b'4eb20e218dc1 (tag: resf_kernel-5.14.0-570.42.2.el9_6, origin/rocky9_6_rebuild) Rebuild rocky9_6 with kernel-5.14.0-570.42.2.el9_6'
b'4d2fb3e9de8a (tag: resf_kernel-5.14.0-570.41.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.41.1.el9_6'
b'1b9ea68b26cf (tag: resf_kernel-5.14.0-570.39.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.39.1.el9_6'
b'6ad42715f2bf (tag: resf_kernel-5.14.0-570.37.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.37.1.el9_6'
b'0564e55498d2 (tag: resf_kernel-5.14.0-570.32.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.32.1.el9_6'
b'e0a1a84bc26b (tag: resf_kernel-5.14.0-570.30.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.30.1.el9_6'
b'9fbeb8c24bbd (tag: resf_kernel-5.14.0-570.28.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.28.1.el9_6'
b'8cc6f289778f (tag: resf_kernel-5.14.0-570.26.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.26.1.el9_6'
b'cad0cbcb03be (tag: resf_kernel-5.14.0-570.25.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.25.1.el9_6'
b'4743a27158ca (tag: resf_kernel-5.14.0-570.24.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.24.1.el9_6'
b'08b6475feb07 (tag: resf_kernel-5.14.0-570.23.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.23.1.el9_6'
b'667004a38548 (tag: resf_kernel-5.14.0-570.22.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.22.1.el9_6'
b'9477e3364951 (tag: resf_kernel-5.14.0-570.21.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.21.1.el9_6'
b'b94108159618 (tag: resf_kernel-5.14.0-570.19.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.19.1.el9_6'
b'e8b954c95fef (tag: resf_kernel-5.14.0-570.18.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.18.1.el9_6'
b'838cd1e8d046 (tag: resf_kernel-5.14.0-570.17.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.17.1.el9_6'
b'171ceb527773 (tag: resf_kernel-5.14.0-570.16.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.16.1.el9_6'
b'18c0812a6563 (tag: resf_kernel-5.14.0-570.12.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.12.1.el9_6'
[rolling release update] New Base Branch Tags:  [b'c18abab0e029', b'eed76cad25c1', b'6be68ff1dc33', b'7d4826997117', b'4eb20e218dc1', b'4d2fb3e9de8a', b'1b9ea68b26cf', b'6ad42715f2bf', b'0564e55498d2', b'e0a1a84bc26b', b'9fbeb8c24bbd', b'8cc6f289778f', b'cad0cbcb03be', b'4743a27158ca', b'08b6475feb07', b'667004a38548', b'9477e3364951', b'b94108159618', b'e8b954c95fef', b'838cd1e8d046', b'171ceb527773', b'18c0812a6563']
[rolling release update] Latest RESF tag sha:  b'6be68ff1dc33'
"6be68ff1dc3328409622f69ed21f1a1f72c39954 Rebuild rocky9_6 with kernel-5.14.0-570.49.1.el9_6"
[rolling release update] Checking out old rolling branch:  sig-cloud-9/5.14.0-570.49.1.el9_6
[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'6be68ff1dc33'
[rolling release update] Total Commit in old branch:  21
{ "CIQ COMMMIT" : "UPSTREAM COMMMIT" }
Printing first 5 and last 5 commits
{
  "230e93fb69bf5c2a7a2d9fdaa303923a96d00c4c": "fbe346ce9d626680a4dd0f079e17c7b5dd32ffad",
  "619bb577b0ee5ed9d089e141425447546dc2115a": "7768c5f417336fa58dbfef9bb7ecd7eeec6d8886",
  "79020dc82b656b6efe540353853756eec9c65cd4": "c09ef59e17c6921c577d54bc8da4331b955d01a7",
  "225d912a1fbcc1b676ac85ae7a97575687881e60": "fa37a8849634db2dd3545116873da8cf4b1e67c6",
  "f212148a4f868b726d3ee700f280e10675175f6d": "2fc8a346625eb1abfe202062c7e6a13d76cde5ea"
}
{
  "aeab6683c52b3b30b995a5cc3cfc61db9216a9f9": "9e517a8e9d9a303bf9bde35e5c5374795544c152",
  "b08f3fcf1d1e07ee656028d034869c185de7044f": "4a3b99bc04e501b816db78f70064e26a01257910",
  "efd4c95f46b98a1c764b3ee5cd47009b2878e7e8": "a9c0b33ef2306327dd2db02c6274107065ff9307",
  "ea61668031bce8457b7f1daa2a97a62623416f93": "290e5d3c49f687c1567bde634dc33d57b0674919",
  "07b89ae0292b25672068d350714d923717eb94ba": ""
}
[rolling release update] Checking out new base branch:  rocky9_6
[rolling release update] Finding the kernel version for the new rolling release
b'c18abab0e029 (HEAD -> rocky9_6, tag: resf_kernel-5.14.0-570.52.1.el9_6, origin/rocky9_6, origin/fips-9-compliant/5.14.0-570.52.1.el9_6) Rebuild rocky9_6 with kernel-5.14.0-570.52.1.el9_6'
<re.Match object; span=(0, 70), match=b'c18abab0e029 (HEAD -> rocky9_6, tag: resf_kernel>
[rolling release update} New Branch to create  sig-cloud-9/5.14.0-570.52.1.el9_6
[rolling release update] Check if branch Exists:  sig-cloud-9/5.14.0-570.52.1.el9_6
Branch sig-cloud-9/5.14.0-570.52.1.el9_6 does not exists creating
[rolling release update] Creating new branch for PR:  shreeya_sig-cloud-9/5.14.0-570.52.1.el9_6
[rolling release update] Creating Map of all new commits from last rolling release fork
[rolling release update] Total Commit in new branch:  43
{ "CIQ COMMMIT" : "UPSTREAM COMMMIT" }
Printing first 5 and last 5 commits
{
  "c18abab0e0297b9f20d92e476a57f82b62b79ed3": "",
  "7ac80205f8870667e38f82fba3761d61523d2faa": "32e62025e5e52fbe4812ef044759de7010b15dbc",
  "a870ed1b83e64242019d0516e315300e50dc61c3": "33caa208dba6fa639e8a92fd0c8320b652e5550c",
  "a16ad332e8378800e04457f81b2d1ae0ccf9ee4c": "62de0e67328e9503459a24b9343c3358937cdeef",
  "eb0235ee3595ef8568de433083a68145ac844671": "fbe346ce9d626680a4dd0f079e17c7b5dd32ffad"
}
{
  "eed76cad25c1850b72a57d6022340b6444f09926": "",
  "38c43d18b2685d8d28bd51f6d934ea72951303b6": "7c0884fcd2ddde0544d2e77f297ae461e1f53f58",
  "bf3df34247fb6b2d53cbeba3f4de58d9a312e456": "42e6ddda4c17fa0d5120e3723d522649f8fc62fa",
  "1cc41894e646fd3344df706e733cca5808c592bb": "4a74da044ec9ec8679e6beccc4306b936b62873f",
  "e55463f89873940a5cc326292a1ca09595db778d": "fa787ac07b3ceb56dd88a62d1866038498e96230"
}
[rolling release update] Checking if any of the commits from the old rolling release are already present in the new base branch
- Commit 230e93fb69bf5c2a7a2d9fdaa303923a96d00c4c already present in new base branch: 230e93fb69bf5c2a7a2d9fdaa303923a96d00c4c net: mana: Handle Reset Request from MANA NIC
- Commit 619bb577b0ee5ed9d089e141425447546dc2115a already present in new base branch: 619bb577b0ee5ed9d089e141425447546dc2115a net: mana: Add handler for hardware servicing events
- Commit 79020dc82b656b6efe540353853756eec9c65cd4 already present in new base branch: 79020dc82b656b6efe540353853756eec9c65cd4 net: mana: Expose additional hardware counters for drop and TC via ethtool.
- Commit 225d912a1fbcc1b676ac85ae7a97575687881e60 already present in new base branch: 225d912a1fbcc1b676ac85ae7a97575687881e60 net: mana: Switch to page pool for jumbo frames
- Commit f212148a4f868b726d3ee700f280e10675175f6d already present in new base branch: f212148a4f868b726d3ee700f280e10675175f6d net: mana: Support holes in device list reply msg
- Commit ca3ea7f3324e40509650a6c2c074b7e1182b5c62 already present in new base branch: ca3ea7f3324e40509650a6c2c074b7e1182b5c62 RDMA/mana_ib: Handle net event for pointing to the current netdev
- Commit 564a0a78989dcc9320ce6397263e600627753f0e already present in new base branch: 564a0a78989dcc9320ce6397263e600627753f0e net: mana: Change the function signature of mana_get_primary_netdev_rcu
- Commit 263f9e8b678340bc77b76533769f34363056fa9a already present in new base branch: 263f9e8b678340bc77b76533769f34363056fa9a net: mana: Add debug logs in MANA network driver
- Commit fc0324f7b8e30cfb5dc05b9242453e85cb1ba0b4 already present in new base branch: fc0324f7b8e30cfb5dc05b9242453e85cb1ba0b4 net: mana: Allow tso_max_size to go up-to GSO_MAX_SIZE
- Commit 42b9dab58fa412dddbef3da2b8938ca8d855ddbf already present in new base branch: 42b9dab58fa412dddbef3da2b8938ca8d855ddbf hv_netvsc: Use VF's tso_max_size value when data path is VF
- Commit aeab6683c52b3b30b995a5cc3cfc61db9216a9f9 already present in new base branch: aeab6683c52b3b30b995a5cc3cfc61db9216a9f9 RDMA/mana_ib: use the correct page table index based on hardware page size
- Commit b08f3fcf1d1e07ee656028d034869c185de7044f already present in new base branch: b08f3fcf1d1e07ee656028d034869c185de7044f RDMA/mana_ib: use the correct page size for mapping user-mode doorbell page
- Commit ea61668031bce8457b7f1daa2a97a62623416f93 already present in new base branch: ea61668031bce8457b7f1daa2a97a62623416f93 net: mana: Add support for Multi Vports on Bare metal
[rolling release update] Removing commits from the new branch
230e93fb69bf5c2a7a2d9fdaa303923a96d00c4c net: mana: Handle Reset Request from MANA NIC
619bb577b0ee5ed9d089e141425447546dc2115a net: mana: Add handler for hardware servicing events
79020dc82b656b6efe540353853756eec9c65cd4 net: mana: Expose additional hardware counters for drop and TC via ethtool.
225d912a1fbcc1b676ac85ae7a97575687881e60 net: mana: Switch to page pool for jumbo frames
f212148a4f868b726d3ee700f280e10675175f6d net: mana: Support holes in device list reply msg
ca3ea7f3324e40509650a6c2c074b7e1182b5c62 RDMA/mana_ib: Handle net event for pointing to the current netdev
564a0a78989dcc9320ce6397263e600627753f0e net: mana: Change the function signature of mana_get_primary_netdev_rcu
263f9e8b678340bc77b76533769f34363056fa9a net: mana: Add debug logs in MANA network driver
fc0324f7b8e30cfb5dc05b9242453e85cb1ba0b4 net: mana: Allow tso_max_size to go up-to GSO_MAX_SIZE
42b9dab58fa412dddbef3da2b8938ca8d855ddbf hv_netvsc: Use VF's tso_max_size value when data path is VF
aeab6683c52b3b30b995a5cc3cfc61db9216a9f9 RDMA/mana_ib: use the correct page table index based on hardware page size
b08f3fcf1d1e07ee656028d034869c185de7044f RDMA/mana_ib: use the correct page size for mapping user-mode doorbell page
ea61668031bce8457b7f1daa2a97a62623416f93 net: mana: Add support for Multi Vports on Bare metal
[rolling release update] Applying the remaining commits to the new branch
Applying commit  "07b89ae0292b25672068d350714d923717eb94ba selftests/mm temporary fix of hmm infinite loop"
Applying commit  "efd4c95f46b98a1c764b3ee5cd47009b2878e7e8 tools: hv: Enable debug logs for hv_kvp_daemon"
Applying commit  "7a610e33b5f55d3204d9cda31a647c7011064681 scsi: storvsc: Increase the timeouts to storvsc_timeout"
Applying commit  "55ff3f49a50ed4cd791ca5658c02c31cc0dc00f1 Drivers: hv: Allow vmbus_sendpacket_mpb_desc() to create multiple ranges"
Applying commit  "0d0eb984129c8ede9aa86da45fe7aedfb862787c hv_netvsc: Use vmbus_sendpacket_mpb_desc() to send VMBus messages"
Applying commit  "aed11cc86a0434dfb1e1508329d60a0ddb0d19a9 hv_netvsc: Preserve contiguous PFN grouping in the page buffer array"
Applying commit  "3d125013827ee3e92f47ace7c99015c386bd799d hv_netvsc: Remove rmsg_pgcnt"
Applying commit  "8e46d21fca3f199bc1325d23af34d2e211590a32 Drivers: hv: vmbus: Remove vmbus_sendpacket_pagebuffer()"

BUILD

/mnt/scratch/workspace/sig-cloud-9/kernel-src-tree
Skipping make mrproper
[TIMER]{MRPROPER}: 0s
x86_64 architecture detected, copying config
'configs/kernel-x86_64-rhel.config' -> '.config'
Setting Local Version for build
CONFIG_LOCALVERSION="-shreeya_sig-cloud-9_5.14.0-570.52.1.el9_6-7e72364dc97"
Making olddefconfig
#
# configuration written to .config
#
Starting Build
  SYNC    include/config/auto.conf.cmd
  UPD     include/generated/uapi/linux/version.h
mkdir -p /mnt/scratch/workspace/sig-cloud-9/kernel-src-tree/tools/objtool && make O=/mnt/scratch/workspace/sig-cloud-9/kernel-src-tree subdir=tools/objtool --no-print-directory -C objtool 
  UPD     include/config/kernel.release
mkdir -p /mnt/scratch/workspace/sig-cloud-9/kernel-src-tree/tools/bpf/resolve_btfids && make O=/mnt/scratch/workspace/sig-cloud-9/kernel-src-tree subdir=tools/bpf/resolve_btfids --no-print-directory -C bpf/resolve_btfids 
  UPD     include/generated/utsrelease.h
  HOSTCC  scripts/mod/modpost.o
  INSTALL libsubcmd_headers
  HDRINST usr/include/linux/version.h
  HOSTLD  scripts/mod/modpost
  CALL    scripts/atomic/check-atomics.sh
warning: generated include/linux/atomic/atomic-instrumented.h has been modified.
  CALL    scripts/checksyscalls.sh
--
  STRIP   /lib/modules/5.14.0-shreeya_sig-cloud-9_5.14.0-570.52.1.el9_6-7e72364dc97+/kernel/sound/virtio/virtio_snd.ko
  STRIP   /lib/modules/5.14.0-shreeya_sig-cloud-9_5.14.0-570.52.1.el9_6-7e72364dc97+/kernel/sound/x86/snd-hdmi-lpe-audio.ko
  STRIP   /lib/modules/5.14.0-shreeya_sig-cloud-9_5.14.0-570.52.1.el9_6-7e72364dc97+/kernel/sound/xen/snd_xen_front.ko
  SIGN    /lib/modules/5.14.0-shreeya_sig-cloud-9_5.14.0-570.52.1.el9_6-7e72364dc97+/kernel/sound/virtio/virtio_snd.ko
  SIGN    /lib/modules/5.14.0-shreeya_sig-cloud-9_5.14.0-570.52.1.el9_6-7e72364dc97+/kernel/sound/xen/snd_xen_front.ko
  SIGN    /lib/modules/5.14.0-shreeya_sig-cloud-9_5.14.0-570.52.1.el9_6-7e72364dc97+/kernel/sound/x86/snd-hdmi-lpe-audio.ko
  SIGN    /lib/modules/5.14.0-shreeya_sig-cloud-9_5.14.0-570.52.1.el9_6-7e72364dc97+/kernel/arch/x86/crypto/crct10dif-pclmul.ko
  DEPMOD  /lib/modules/5.14.0-shreeya_sig-cloud-9_5.14.0-570.52.1.el9_6-7e72364dc97+
[TIMER]{MODULES}: 12s
Making Install
sh ./arch/x86/boot/install.sh 5.14.0-shreeya_sig-cloud-9_5.14.0-570.52.1.el9_6-7e72364dc97+ \
	arch/x86/boot/bzImage System.map "/boot"
[TIMER]{INSTALL}: 31s
Checking kABI
kABI check passed
Setting Default Kernel to /boot/vmlinuz-5.14.0-shreeya_sig-cloud-9_5.14.0-570.52.1.el9_6-7e72364dc97+ and Index to 0
The default is /boot/loader/entries/10b309961c7e4c8c874a592079eefa4b-5.14.0-shreeya_sig-cloud-9_5.14.0-570.52.1.el9_6-7e72364dc97+.conf with index 0 and kernel /boot/vmlinuz-5.14.0-shreeya_sig-cloud-9_5.14.0-570.52.1.el9_6-7e72364dc97+
The default is /boot/loader/entries/10b309961c7e4c8c874a592079eefa4b-5.14.0-shreeya_sig-cloud-9_5.14.0-570.52.1.el9_6-7e72364dc97+.conf with index 0 and kernel /boot/vmlinuz-5.14.0-shreeya_sig-cloud-9_5.14.0-570.52.1.el9_6-7e72364dc97+
Generating grub configuration file ...
Adding boot menu entry for UEFI Firmware Settings ...
done
Hopefully Grub2.0 took everything ... rebooting after time metrices
[TIMER]{MRPROPER}: 0s
[TIMER]{BUILD}: 591s
[TIMER]{MODULES}: 12s
[TIMER]{INSTALL}: 31s
[TIMER]{TOTAL} 639s
Rebooting in 10 seconds

kernel-build.log

Kselftests

shreeya@spatel-dev-bom ~/c/w/sig-cloud-9> grep -a ^ok kselftest-before.log | wc -l
382
shreeya@spatel-dev-bom ~/c/w/sig-cloud-9> grep -a ^ok kselftest-after.log | wc -l
382

kselftest-after.log
kselftest-before.log

PlaidCat and others added 8 commits October 16, 2025 11:58
jira SECO-170

In Rocky9 if you run ./run_vmtests.sh -t hmm it will fail and cause an
infinite loop on ASSERTs in FIXTURE_TEARDOWN()
This temporary fix is based on the discussion here
https://patchwork.kernel.org/project/linux-kselftest/patch/26017fe3-5ad7-6946-57db-e5ec48063ceb@suse.cz/#25046055

We will investigate further kselftest updates that will resolve the root
causes of this.

Signed-off-by: Jonathan Maple <jmaple@ciq.com>
Signed-off-by: Shreeya Patel <spatel@ciq.com>
jira LE-3207
feature tools_hv
commit-author Shradha Gupta <shradhagupta@linux.microsoft.com>
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 <shradhagupta@linux.microsoft.com>
	Reviewed-by: Naman Jain <namjain@linux.microsoft.com>
	Reviewed-by: Dexuan Cui <decui@microsoft.com>
Link: https://lore.kernel.org/r/1744715978-8185-1-git-send-email-shradhagupta@linux.microsoft.com
	Signed-off-by: Wei Liu <wei.liu@kernel.org>
Message-ID: <1744715978-8185-1-git-send-email-shradhagupta@linux.microsoft.com>
(cherry picked from commit a9c0b33)
	Signed-off-by: Jonathan Maple <jmaple@ciq.com>
Signed-off-by: Jonathan Maple <jmaple@ciq.com>
Signed-off-by: Shreeya Patel <spatel@ciq.com>
jira LE-3545
commit-author Dexuan Cui <decui@microsoft.com>
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: stable@kernel.org
	Signed-off-by: Dexuan Cui <decui@microsoft.com>
Link: https://lore.kernel.org/r/1749243459-10419-1-git-send-email-decui@microsoft.com
	Reviewed-by: Long Li <longli@microsoft.com>
	Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
(cherry picked from commit b2f9665)
	Signed-off-by: Sultan Alsawaf <sultan@ciq.com>
Signed-off-by: Jonathan Maple <jmaple@ciq.com>
Signed-off-by: Shreeya Patel <spatel@ciq.com>
jira LE-3554
commit-author Michael Kelley <mhklinux@outlook.com>
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: <stable@vger.kernel.org> # 6.1.x
	Signed-off-by: Michael Kelley <mhklinux@outlook.com>
Link: https://patch.msgid.link/20250513000604.1396-2-mhklinux@outlook.com
	Signed-off-by: Jakub Kicinski <kuba@kernel.org>
(cherry picked from commit 380b75d)
	Signed-off-by: Shreeya Patel <spatel@ciq.com>
Signed-off-by: Jonathan Maple <jmaple@ciq.com>
Signed-off-by: Shreeya Patel <spatel@ciq.com>
jira LE-3554
commit-author Michael Kelley <mhklinux@outlook.com>
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: <stable@vger.kernel.org> # 6.1.x
	Signed-off-by: Michael Kelley <mhklinux@outlook.com>
Link: https://patch.msgid.link/20250513000604.1396-3-mhklinux@outlook.com
	Signed-off-by: Jakub Kicinski <kuba@kernel.org>
(cherry picked from commit 4f98616)
	Signed-off-by: Shreeya Patel <spatel@ciq.com>
Signed-off-by: Jonathan Maple <jmaple@ciq.com>
Signed-off-by: Shreeya Patel <spatel@ciq.com>
jira LE-3554
commit-author Michael Kelley <mhklinux@outlook.com>
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: <stable@vger.kernel.org> # 6.1.x
	Signed-off-by: Michael Kelley <mhklinux@outlook.com>
Link: https://patch.msgid.link/20250513000604.1396-4-mhklinux@outlook.com
	Signed-off-by: Jakub Kicinski <kuba@kernel.org>
(cherry picked from commit 41a6328)
	Signed-off-by: Shreeya Patel <spatel@ciq.com>
Signed-off-by: Jonathan Maple <jmaple@ciq.com>
Signed-off-by: Shreeya Patel <spatel@ciq.com>
jira LE-3554
commit-author Michael Kelley <mhklinux@outlook.com>
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: <stable@vger.kernel.org> # 6.1.x
	Signed-off-by: Michael Kelley <mhklinux@outlook.com>
Link: https://patch.msgid.link/20250513000604.1396-5-mhklinux@outlook.com
	Signed-off-by: Jakub Kicinski <kuba@kernel.org>
(cherry picked from commit 5bbc644)
	Signed-off-by: Shreeya Patel <spatel@ciq.com>
Signed-off-by: Jonathan Maple <jmaple@ciq.com>
Signed-off-by: Shreeya Patel <spatel@ciq.com>
jira LE-3554
commit-author Michael Kelley <mhklinux@outlook.com>
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: <stable@vger.kernel.org> # 6.1.x
	Signed-off-by: Michael Kelley <mhklinux@outlook.com>
Link: https://patch.msgid.link/20250513000604.1396-6-mhklinux@outlook.com
	Signed-off-by: Jakub Kicinski <kuba@kernel.org>
(cherry picked from commit 45a442f)
	Signed-off-by: Shreeya Patel <spatel@ciq.com>
Signed-off-by: Jonathan Maple <jmaple@ciq.com>
Signed-off-by: Shreeya Patel <spatel@ciq.com>
@shreeya-patel98 shreeya-patel98 requested a review from a team October 16, 2025 13:59
@shreeya-patel98 shreeya-patel98 self-assigned this Oct 16, 2025
@bmastbergen bmastbergen self-requested a review October 16, 2025 14:21
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
Collaborator

@PlaidCat PlaidCat left a comment

Choose a reason for hiding this comment

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

:shipit:

@shreeya-patel98 shreeya-patel98 merged commit 424dfec into sig-cloud-9/5.14.0-570.52.1.el9_6 Oct 17, 2025
4 of 6 checks passed
@shreeya-patel98 shreeya-patel98 deleted the shreeya_sig-cloud-9/5.14.0-570.52.1.el9_6 branch October 17, 2025 08:14
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.

6 participants