GDS: Add NFS patches to optimized kernel

Bug #1982519 reported by Brad Figg
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-nvidia (Ubuntu)
New
Undecided
Unassigned
Jammy
Fix Released
Undecided
Unassigned
linux-nvidia-5.19 (Ubuntu)
New
Undecided
Unassigned
Jammy
Fix Released
Undecided
Unassigned
linux-nvidia-6.2 (Ubuntu)
New
Undecided
Unassigned
Jammy
Fix Released
Undecided
Unassigned

Bug Description

 [Impact]
    Adding these changes will enable GDS functionality NFS drivers.

 [Fix]
    This is a not a fix but a new feature being to NFS driver.

 [Test]

Tested the NFS driver on a hpe system as I did not have a setup with BASEOS6.
     1) Installed 5.15.39 kernel on the system (this is the kernel that optimized kernel is on currently).
     2) Downloaded the optimized kernel.
     3) Applied the patches to the optimized kernel
     4) Replaced the NFS modules on the system with the one's built on optimized kernel.
     5) Ran gds and compat mode tests on a NFS mount with the patched NFS driver. All tests went fine.

Attaching the results

Compat mode tests
==================
**************************************************
API Tests, : 72 / 72 tests passed
**************************************************
Testsuite : 211 / 211 tests passed
done tests:Thu Jul 21 08:27:58 PM UTC 2022

GDS mode tests
==================
**************************************************
NVFS IOCTL negative Tests, : 23 / 23 tests passed
**************************************************
Testsuite : 249 / 249 tests passed
End: nvidia-fs:
GDS Version: 1.4.0.31
NVFS statistics(ver: 4.0)

Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (118.0 KiB)

This bug was fixed in the package linux-nvidia - 5.15.0-1007.7

---------------
linux-nvidia (5.15.0-1007.7) jammy; urgency=medium

  * jammy/linux-nvidia: 5.15.0-1007.7 -proposed tracker (LP: #1990418)

  * GDS: Add NFS patches to optimized kernel (LP: #1982519)
    - NFS: Patch NFS driver to support GDS

  * NVMe/MVMEeOF: Patch NVMe/NVMeOF driver to support GDS (LP: #1982518)
    - NVMe/MVMEeOF: Patch NVMe/NVMeOF driver to support GDS

linux-nvidia (5.15.0-1006.6) jammy; urgency=medium

  * jammy/linux-nvidia: 5.15.0-1006.6 -proposed tracker (LP: #1988357)

  * Ubuntu 22.04 and 20.04 DPC Fixes for Failure Cases of DownPort Containment
    events (LP: #1965241)
    - [Config] Enable config option CONFIG_PCIE_EDR

  * disable Intel DMA remapping by default (LP: #1971699)
    - Revert "UBUNTU: [Config] enable Intel DMA remapping options by default"

  * Jammy update: v5.15.49 upstream stable release (LP: #1983149)
    - [Config] updateconfigs for LIB_MEMNEQ

  * GPIO character device v1 API not enabled in kernel (LP: #1953613)
    - [Config] Enable CONFIG_GPIO_CDEV_V1

  * Jammy update: v5.15.46 upstream stable release (LP: #1981864)
    - [Config] updateconfigs for IMA_TEMPLATE
    - [Packaging] add python3-dev as build dependency

  * Jammy update: v5.15.44 upstream stable release (LP: #1981649)
    - [Config] update configs for CRYPTO_LIB_BLAKE2S

  * Miscellaneous Ubuntu changes
    - [Packaging] Enable nvidia-lowlatency for amd64
    - remove debian.nvidia/control.stub which was inadvertently committed
    - [Config] CONFIG_LIBMEMNEQ -> CONFIG_LIB_MEMNEQ

  [ Ubuntu: 5.15.0-48.54 ]

  * jammy/linux: 5.15.0-48.54 -proposed tracker (LP: #1987775)
  * System freeze after resuming from suspend due to PCI ASPM settings
    (LP: #1980829)
    - SAUCE: PCI/ASPM: Save/restore L1SS Capability for suspend/resume
    - SAUCE: whitelist platforms that needs save/restore ASPM L1SS for
      suspend/resume
  * [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average
    luminance (LP: #1978986)
    - SAUCE: drm: New function to get luminance range based on static hdr metadata
    - SAUCE: drm/amdgpu_dm: Rely on split out luminance calculation function
    - SAUCE: drm/i915: Use luminance range calculated during edid parsing
  * Jammy: Add OVS Internal Port HW Offload to mlx5 driver (LP: #1983498)
    - net/mlx5e: Refactor rx handler of represetor device
    - net/mlx5e: Use generic name for the forwarding dev pointer
    - net/mlx5: E-Switch, Add ovs internal port mapping to metadata support
    - net/mlx5e: Support accept action
    - net/mlx5e: Accept action skbedit in the tc actions list
    - net/mlx5e: Offload tc rules that redirect to ovs internal port
    - net/mlx5e: Offload internal port as encap route device
    - net/mlx5e: Enable TC offload for ingress MACVLAN
    - net/mlx5e: Add indirect tc offload of ovs internal port
    - net/mlx5e: Term table handling of internal port rules
    - net/mlx5: Support internal port as decap route device
    - net/mlx5: Fix some error handling paths in 'mlx5e_tc_add_fdb_flow()'
    - net/mlx5e: TC, Fix memory leak with rules with internal port
    - net/mlx5e: Fix skb memory leak when TC cl...

Changed in linux-nvidia (Ubuntu Jammy):
status: New → Fix Released
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-nvidia-5.19/5.19.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-nvidia-5.19 verification-needed-jammy
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-nvidia-6.2/6.2.0-1009.9 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-6.2' to 'verification-done-jammy-linux-nvidia-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-6.2' to 'verification-failed-jammy-linux-nvidia-6.2'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-nvidia-6.2-v2 verification-needed-jammy-linux-nvidia-6.2
Ian May (ian-may)
Changed in linux-nvidia-6.2 (Ubuntu Jammy):
status: New → Fix Released
Ian May (ian-may)
Changed in linux-nvidia-5.19 (Ubuntu Jammy):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.