Public bug reported:

SRU Justification

[Impact]

A google customer is building the nvidia-maintained version of the
graphics driver dkms. It is failing to build against the gcp-7.0 headers
because these headers have diverged from matching upstream nor generic.
This originally happened because the upstream headers were incompatible
with the doca-ofed dkms in 26.04, and instead of patching the doca-ofed
dkms we changed the gcp-7.0 headers.

To resolve this issue, we should patch the doca-ofed dkms package to be
compatible with the headers after the problematic symbols have been
renamed, and we should bring in the symbol rename commit to gcp-7.0 so
that these headers more closely match upstream.

Once the gcp-7.0 headers have symbols renamed to match upstream, the
external nvidia dkms package should start building again. We should
check if it builds for this particular ticket, however the customer
should not think that externally maintained dkms packages are part of
our support umbrella, we’re only fixing this because we’re fixing our
header policy.

The following commits must be applied:

95308225e5ba ("dma-buf: Rename dma_buf_move_notify() to 
dma_buf_invalidate_mappings()")
ef246da8e63c ("dma-buf: Rename .move_notify() callback to a clearer identifier")

[Fix]

95308225e5ba was already applied, ef246da8e63c is missing. So, the next
commits were included:

Reverted:
dc6d51959ec0 ("dma-buf: fix htmldocs error for dma_buf_attach_revocable")
be6d4c9e9d71 ("dma-buf: Add dma_buf_attach_revocable()")
575157b1b5fc ("dma-buf: Make .invalidate_mapping() truly optional")
609fc8766d68 ("dma-buf: Always build with DMABUF_MOVE_NOTIFY")

Backported:
ef246da8e63c ("dma-buf: Rename .move_notify() callback to a clearer identifier")

Reapplied cleanly:
609fc8766d68 ("dma-buf: Always build with DMABUF_MOVE_NOTIFY")
575157b1b5fc ("dma-buf: Make .invalidate_mapping() truly optional")
be6d4c9e9d71 ("dma-buf: Add dma_buf_attach_revocable()")
dc6d51959ec0 ("dma-buf: fix htmldocs error for dma_buf_attach_revocable")


[Test Plan]

Compiled and boot tested.
The external nvidia dkms for 615.71.10 built correctly.


[Regression potential]

Because the four commits (609fc8766d68, 575157b1b5fc, be6d4c9e9d71,
dc6d51959ec0) were temporarily reverted only to establish a clean
context for backporting ef246da8e63c and subsequently reapplied cleanly,
the resulting code state aligns properly with upstream history. No
regressions are expected from the revert-and-reapply sequence itself


[Other]
SF: 00453967

** Affects: linux-gcp (Ubuntu)
     Importance: Undecided
     Assignee: Rickey Castillo Valenzuela (rickeycv)
         Status: New

** Affects: linux-gcp (Ubuntu Resolute)
     Importance: Undecided
     Assignee: Rickey Castillo Valenzuela (rickeycv)
         Status: New

** Also affects: linux-gcp (Ubuntu Resolute)
   Importance: Undecided
       Status: New

** Changed in: linux-gcp (Ubuntu)
     Assignee: (unassigned) => Rickey Castillo Valenzuela (rickeycv)

** Changed in: linux-gcp (Ubuntu Resolute)
     Assignee: (unassigned) => Rickey Castillo Valenzuela (rickeycv)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2174892

Title:
  Fix gcp-7.0 nvidia-related headers mismatching upstream

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2174892/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to