[UBUNTU 20.04] Null Pointer issue in nfs code running Ubuntu on IBM Z

[bugproxy]

SRU Justification:
==================

[Impact]

* The kernel crashed under load with a null pointer issue in nfs code:
    [556585.270959] Krnl Code:#0000000000000000: 0000 illegal
                              >0000000000000002: 0000 illegal
                               0000000000000004: 0000 illegal
                               0000000000000006: 0000 illegal
                               0000000000000008: 0000 illegal
                               000000000000000a: 0000 illegal
                               000000000000000c: 0000 illegal
                               000000000000000e: 0000 illegal
    [556585.270967] Call Trace:
    [556585.270982] ([<000003ff80d6fb1a>] rpcauth_lookup_credcache+0x5a/0x300 [sunrpc])
    [556585.270993] [<000003ff80e1182c>] nfs_ctx_key_to_expire+0xec/0x130 [nfs]
    [556585.271004] [<000003ff80e1189c>] nfs_key_timeout_notify+0x2c/0x70 [nfs]
    [556585.271014] [<000003ff80dfdf7e>] nfs_file_write+0x3e/0x320 [nfs]
    [556585.271016] [<00000028165944a8>] new_sync_write+0x118/0x1b0
    [556585.271017] [<0000002816594ee0>] vfs_write+0xb0/0x1b0
    [556585.271019] [<0000002816596a1e>] ksys_pwrite64+0x7e/0xc0
    [556585.271021] [<0000002816bb26b2>] system_call+0x2a6/0x2c8

* Several dumps were generated and shared with Canonical.

* Analysis (done by kernel and SEG) point to refcount leaks fixed,
  that are already fixed in the following commit/fix:

[Fix]

* ca05cbae2a0468e5d78e9b4605936a8bf5da328b ca05cbae2a04 "NFS: Fix up nfs_ctx_key_to_expire()"

[Test Case]

* There is unfortunately no reproducer or trigger available for this issue.

* It just happens now and then under higher load.

* Patched test kernels (focal 5.4 and bionic 5.4-hwe) were created and
  ran for more than a week in a special staging environment (at IBM)
  without further crashes.

* Hence the test and verification will be done by the IBM Z team.

[Where problems could occur]

* The inode handling can become broken, in case the changes
  on the pointers are erroneous.

* Problems with the authentication and/or the credentials could occur
  due to the modifications in put_rpccred, rpc_cred and rpc_auth.

* The expiration of the cached credentials could be harmed as well,
  due to the changes in nfs_ctx_key_to_expire.

* The different pointer arithmetic may cause further issues - wrong
  or null pointer references.

* Positive is that the original commit was brought upstream by nfs experts.

* A patched test kernel sustained day long runs under load in a staging
  and test environment.

* The author of the upstream commit/patch is well known in the NFS area.

[Other]

* The Salesforce Case Number 00334334 is associated with this bug.

* Commit ca05cbae2a04 was upstream accepted with 5.16-rc1.

* But commit ca05cbae2a04 was unfortunately not tagged as stable,
  hence it was not picked automatically.

* Since kinetic's (22.10) target kernel is 5.18,
  it will have the patch included,
  hence no dedicated PATCH request for kinetic.

__________

State the component where the Bug is occurring:
  kernel

Indicate the nature of the problem by answering the below questions:
- Is this problem reproducible? No
No, steps unknown, but we have seen these before

- Is the system sitting at a debugger (kdb, or xmon)? No

- Is the system hung? No
No, dumped and rebooted

- Are there any custom patches installed? Yes
On base system level (CloudAppliance) we are still running with the zfpc_proc module loaded. But no recent changes in the module and is running absolutely stable in HA (same kernel and userspace, Ubuntu 20.04 LTS)

- Is there any special hardware that may be relevant to this problem? Yes
We are running with mlx (cloud network adapters) installed.

- Is access information for the machine the problem was found on available? Yes

- Is the bug occuring in a userspace application? No

- Was a stack trace produced? Yes
This is what mention in first comment by @Boris Barth

- Did the system produce an Oops message on the console? Yes
[556585.270902] illegal operation: 0001 ilc:1 [#10] SMP
[556585.270905] Modules linked in: vhost_net macvtap macvlan tap rpcsec_gss_krb5 auth_rpcgss nfsv3 nfs_acl nfs lockd grace fscache veth xt_statistic ipt_REJECT nf_reject_ipv4 ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs iptable_mangle xt_mark sunrpc nf_log_ipv6 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_set ip_set_hash_net ip_set_hash_ip ip_set tcp_diag inet_diag xt_comment xt_nat cls_cgroup sch_htb act_gact sch_multiq act_mirred act_pedit act_tunnel_key cls_flower act_police cls_u32 vxlan ip6_udp_tunnel udp_tunnel dummy nf_tables ebtable_filter ebtables xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key sch_ingress mlx5_ib ib_uverbs ib_core mlx5_core tls mlxfw ptp pps_core dm_integrity async_xor async_tx dm_bufio bonding xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat br_netfilter bridge vhost_vsock vmw_vsock_virtio_transport_common vhost vsock 8021q garp mrp stp llc xt_multiport xt_tcpudp qeth_l2 lcs ctcm fsm dasd_fba_mod aufs overlay scsi_dh_rdac
[556585.270923] scsi_dh_emc s390_trng xt_state xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6table_filter ip6_tables iptable_filter bpfilter sch_fq_codel zFPC_proc(OE) zFPC_diag(OE) vfio_ap vfio_mdev drm vfio_iommu_type1 drm_panel_orientation_quirks i2c_core ip_tables x_tables scsi_dh_alua pkey zcrypt ghash_s390 prng aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common chsc_sch qeth ccwgroup eadm_sch vfio_ccw mdev vfio btrfs libcrc32c crc32_vx_s390 xor zstd_compress raid6_pq dm_crypt virtio_blk dm_service_time dm_multipath zfcp scsi_transport_fc qdio dasd_eckd_mod dasd_mod zlib_deflate [last unloaded: tls]
[556585.270945] CPU: 28 PID: 217741 Comm: worker Kdump: loaded Tainted: G D OE 5.4.0-90-generic #101-Ubuntu
[556585.270947] Hardware name: IBM 8562 GT2 A00 (LPAR)
[556585.270948] Krnl PSW : 0704d00180000000 0000000000000002 (0x2)
[556585.270951] R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 RI:0 EA:3
[556585.270953] Krnl GPRS: 0000000000000000 0000000000000000 000003e010ebbcf8 00000071c45e1ec0
[556585.270954] 0000000000000000 0000002816f7b18c 00000078dd36a4a0 000000713a62f718
[556585.270955] 0000000000000000 000003e010ebbcf8 0000000000000068 00000071c45e1ec0
[556585.270957] 0000006090a12200 0000000000000c40 000003ff80d6fb54 000003e010ebbbf0
[556585.270959] Krnl Code:#0000000000000000: 0000 illegal
                          >0000000000000002: 0000 illegal
                           0000000000000004: 0000 illegal
                           0000000000000006: 0000 illegal
                           0000000000000008: 0000 illegal
                           000000000000000a: 0000 illegal
                           000000000000000c: 0000 illegal
                           000000000000000e: 0000 illegal
[556585.270967] Call Trace:
[556585.270982] ([<000003ff80d6fb1a>] rpcauth_lookup_credcache+0x5a/0x300 [sunrpc])
[556585.270993] [<000003ff80e1182c>] nfs_ctx_key_to_expire+0xec/0x130 [nfs]
[556585.271004] [<000003ff80e1189c>] nfs_key_timeout_notify+0x2c/0x70 [nfs]
[556585.271014] [<000003ff80dfdf7e>] nfs_file_write+0x3e/0x320 [nfs]
[556585.271016] [<00000028165944a8>] new_sync_write+0x118/0x1b0
[556585.271017] [<0000002816594ee0>] vfs_write+0xb0/0x1b0
[556585.271019] [<0000002816596a1e>] ksys_pwrite64+0x7e/0xc0
[556585.271021] [<0000002816bb26b2>] system_call+0x2a6/0x2c8

- Was a system dump produced ie kdump, netdumpmp, or LKCD? Yes
That is the kdump where the stacktrace from.

Enter data below to accurately describe the problem:
- Problem description:
Null Pointer issue in nfs code running Ubuntu Ubuntu 18.04 with HWE kernel 5.4 on IBM Z

- Enter uname -a output:
@lon1-qz1-sr4-rk101-s04> uname -a
Linux lon1-qz1-sr4-rk101-s04 5.4.0-90-generic #101-Ubuntu SMP Fri Oct 15 19:59:45 UTC 2021 s390x s390x s390x GNU/Linux

- Enter failing machine type and model (ie p520 9111-520 lpar, x336 47U-8637):
Manufacturer: IBM
Type: 8562
Model: A00 GT2
Model Capacity: A00 00000000
Capacity Adj. Ind.: 100
LPAR CPUs Total: 16
LPAR CPUs Configured: 16
LPAR CPUs Standby: 0
LPAR CPUs Reserved: 0
LPAR CPUs Dedicated: 0
LPAR CPUs Shared: 16
LPAR CPUs G-MTID: 0
LPAR CPUs S-MTID: 1
LPAR CPUs PS-MTID: 1

- Enter primary and backup contact information (name/email):
Prabhat Ranjan
<email address hidden>

Christoph Schlameu?
<email address hidden>

- Detail the configuration of the additonal hardware

- Enter common userspace tool name: N/A

- Enter name of userspace RPM: N/A

- If failing tool is obtained from project website vs RPM install, what is the version/release/mod.
  If from the project's CVS, what is the branch tag and date of checkout (put "na" if not applicable)?

N/A

- Is the failing userspace tool 32-bit, 64-bit, or both? N/A

- Describe how unresponsive the system is. What steps have you taken to reclaim the system:
kernel oops was detected and automatically dumped and restarted

- Is a debugger configured (xmon or kdb enabled)? No

- Enter Oops message from console:
[556585.270902] illegal operation: 0001 ilc:1 [#10] SMP
[556585.270905] Modules linked in: vhost_net macvtap macvlan tap rpcsec_gss_krb5 auth_rpcgss nfsv3 nfs_acl nfs lockd grace fscache veth xt_statistic ipt_REJECT nf_reject_ipv4 ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs iptable_mangle xt_mark sunrpc nf_log_ipv6 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_set ip_set_hash_net ip_set_hash_ip ip_set tcp_diag inet_diag xt_comment xt_nat cls_cgroup sch_htb act_gact sch_multiq act_mirred act_pedit act_tunnel_key cls_flower act_police cls_u32 vxlan ip6_udp_tunnel udp_tunnel dummy nf_tables ebtable_filter ebtables xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key sch_ingress mlx5_ib ib_uverbs ib_core mlx5_core tls mlxfw ptp pps_core dm_integrity async_xor async_tx dm_bufio bonding xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat br_netfilter bridge vhost_vsock vmw_vsock_virtio_transport_common vhost vsock 8021q garp mrp stp llc xt_multiport xt_tcpudp qeth_l2 lcs ctcm fsm dasd_fba_mod aufs overlay scsi_dh_rdac
[556585.270923] scsi_dh_emc s390_trng xt_state xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6table_filter ip6_tables iptable_filter bpfilter sch_fq_codel zFPC_proc(OE) zFPC_diag(OE) vfio_ap vfio_mdev drm vfio_iommu_type1 drm_panel_orientation_quirks i2c_core ip_tables x_tables scsi_dh_alua pkey zcrypt ghash_s390 prng aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common chsc_sch qeth ccwgroup eadm_sch vfio_ccw mdev vfio btrfs libcrc32c crc32_vx_s390 xor zstd_compress raid6_pq dm_crypt virtio_blk dm_service_time dm_multipath zfcp scsi_transport_fc qdio dasd_eckd_mod dasd_mod zlib_deflate [last unloaded: tls]
[556585.270945] CPU: 28 PID: 217741 Comm: worker Kdump: loaded Tainted: G D OE 5.4.0-90-generic #101-Ubuntu
[556585.270947] Hardware name: IBM 8562 GT2 A00 (LPAR)
[556585.270948] Krnl PSW : 0704d00180000000 0000000000000002 (0x2)
[556585.270951] R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 RI:0 EA:3
[556585.270953] Krnl GPRS: 0000000000000000 0000000000000000 000003e010ebbcf8 00000071c45e1ec0
[556585.270954] 0000000000000000 0000002816f7b18c 00000078dd36a4a0 000000713a62f718
[556585.270955] 0000000000000000 000003e010ebbcf8 0000000000000068 00000071c45e1ec0
[556585.270957] 0000006090a12200 0000000000000c40 000003ff80d6fb54 000003e010ebbbf0
[556585.270959] Krnl Code:#0000000000000000: 0000 illegal
                          >0000000000000002: 0000 illegal
                           0000000000000004: 0000 illegal
                           0000000000000006: 0000 illegal
                           0000000000000008: 0000 illegal
                           000000000000000a: 0000 illegal
                           000000000000000c: 0000 illegal
                           000000000000000e: 0000 illegal
[556585.270967] Call Trace:
[556585.270982] ([<000003ff80d6fb1a>] rpcauth_lookup_credcache+0x5a/0x300 [sunrpc])
[556585.270993] [<000003ff80e1182c>] nfs_ctx_key_to_expire+0xec/0x130 [nfs]
[556585.271004] [<000003ff80e1189c>] nfs_key_timeout_notify+0x2c/0x70 [nfs]
[556585.271014] [<000003ff80dfdf7e>] nfs_file_write+0x3e/0x320 [nfs]
[556585.271016] [<00000028165944a8>] new_sync_write+0x118/0x1b0
[556585.271017] [<0000002816594ee0>] vfs_write+0xb0/0x1b0
[556585.271019] [<0000002816596a1e>] ksys_pwrite64+0x7e/0xc0
[556585.271021] [<0000002816bb26b2>] system_call+0x2a6/0x2c8

- Detail the steps to reproduce this problem: unknown

- Was the system configured to capture a system dump? Yes

[Frank Heimes (fheimes)]

Thanks for raising this. First of all I've noticed that the kernel in use is pretty outdated (package 'linux-meta-hwe-5.4 (5.4.0.90.101~18.04.80', changelog date 22 Oct 2021) and about half a year old - the current one is '5.4.0-107-generic' (package '5.4.0.107.121~18.04.92').
The delta between 5.4.0.107.121 and 5.4.0.90.101 are 12 updated kernels with ~2000 commits and more than 20 are NFS related and also some about vfs.
Hence I need to ask to update the system to the latest 'linux-image-generic-hwe-18.04' in 'bionic-updates' (5.4.0-107-generic) to be on the latest (and supported) level.
(A test with '5.4.0.108.122~18.04.93' from 'bionic-proposed' would be ideal on top.)

It also looks like a kernel dump was created, could you please share this dump (ideally from the current kernel) for further analysis (either via IBM Box or Canonical's anon. ftp 'http://archive.admin.canonical.com/')?

[bugproxy (bugproxy)]

The delta between 5.4.0.107.121 and 5.4.0.90.101 are about 2000 commits and more than 20 are NFS related and also some about vfs.

------- Comment From <email address hidden> 2022-04-07 09:14 EDT-------
thanks for starting to look into this issue!

We have a large number of LPARs running client workload. This issue happens occasionally - each time impacting client SLAs and causing several hours to re-install LPARs and integrating them in our cloud environment. We need to understand the root cause of the issue.
While we will update our systems any time soon, we cannot afford waiting for the updates to happen to see if the issue disappears. So I hope we can identify the root cause! If it is fixed already - the better :-)

Regarding the kdump: I'm currently clarifying if we can send the kdump. Since it is from a production machine. And I want to ensure we are GDPR compliant. Do you happen to know, if there is a GDPR compliant process established on your side?
As far as I know, a box folder is not an option. But the ftp transfer may be.

Or would it be possible for you to specify the commands to run? We could then ensure the data is clean and send it over

[Frank Heimes (fheimes)]

Tbh. if this happens on a production machine,
than it's not the preferred way to get this addressed via a Launchpad bug (which is mainly for tracking development related bugs) and this should have been addressed as a Salesforce case.

[Frank Heimes (fheimes)]

Our GDPR compliant process is described here:
https://support.canonical.com/ua/s/article/sending-files-sts
It's essentially via uploading to (anon. ftp) files.support.canonical.com

IBM shared logs and dumps via this approach already before, so it should be acceptable...

I still suggest to open a salesforce ticket on top in this case to get it addressed to the right channel.

And based on the information provided, we can only do some high-level checks and verification.
I think a real analysis is only possible based on a dump

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2022-04-07 10:32 EDT-------
yes... makes sense :-) I forwarded the link to our compliance folks. I hope they will say that it's ok to ftp the data.

Regarding salesforce: this is the first time I'm doing this.. and I asked Nicolas Maeding about the approach. He told me to do it this way. Unfortunately both, Nicolas and Boris are out. So I cannot talk to them.
Can we have a short call tomorrow to discuss how to do this (properly)? I should know, but actually don't know :-)
My e-mail is <email address hidden> and I can make myself available most of the time tomorrow.
Frank - I don't have your e-mail address otherwise I would have contacted you via e-mail.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2022-04-08 08:01 EDT-------
I opened https://portal.support.canonical.com/ua/s/case/5004K00000E93ZlQAJ/null-pointer-issue-in-nfs-code-running-ubuntu-on-ibm-z after discussions with Frank.

I assume it is ok to close this bugzilla, correct?

[Frank Heimes (fheimes)]

Well, I suggest to leave it open - sometimes SF cases may cause that a subsequent LP bug need to be opened on top...
And it doesn't hurt to have and leave it for some time ...

[Frank Heimes (fheimes)]

Just for the records, even if the bug description mentions "18.04 with HWE kernel 5.4", this is about and happens with the stock focal 5.4 kernel (the dump that was shared is also a focal 5.4).

[Frank Heimes (fheimes)]

SRU request submitted to the Ubuntu kernel team mailing list for jammy, impish and focal:
https://lists.ubuntu.com/archives/kernel-team/2022-May/thread.html#130364
Changing status to 'In Progress' for jammy, impish and focal.

[Frank Heimes (fheimes)]

Kernel test builds are available here:
https://launchpad.net/~fheimes/+archive/ubuntu/sf00334334/+packages
https://launchpad.net/~fheimes/+archive/ubuntu/lp1968096/+packages

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux/5.15.0-36.37 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!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux/5.4.0-121.137 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'.

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!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux/5.13.0-52.59 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-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'.

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!

[Frank Heimes (fheimes)]

I'm running a patched jammy kernel for more than a week now in one of my test LPARs, and what I've heard is that IBM ran patched kernels for the other Ubuntu releases in their staging are for several days.
With that I feel confident to mark the needed verification as done.

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 5.4.0-121.137

---------------
linux (5.4.0-121.137) focal; urgency=medium

  * focal/linux: 5.4.0-121.137 -proposed tracker (LP: #1978666)

  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- update from kernel-versions (main/2022.05.30)

  * CVE-2022-28388
    - can: usb_8dev: usb_8dev_start_xmit(): fix double dev_kfree_skb() in error
      path

  * test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM
    connectivity through VXLAN (underlay in the default VRF) [FAIL])
    (LP: #1871015)
    - selftests: net: test_vxlan_under_vrf: fix HV connectivity test

  * [UBUNTU 20.04] CPU-MF: add extended counter set definitions for new IBM z16
    (LP: #1974433)
    - s390/cpumf: add new extended counter set for IBM z16

  * [UBUNTU 20.04] KVM nesting support leaks too much memory, might result in
    stalls during cleanup (LP: #1974017)
    - KVM: s390: vsie/gmap: reduce gmap_rmap overhead

  * [UBUNTU 20.04] Null Pointer issue in nfs code running Ubuntu on IBM Z
    (LP: #1968096)
    - NFS: Fix up nfs_ctx_key_to_expire()

 -- Stefan Bader <email address hidden> Wed, 15 Jun 2022 15:13:27 +0200

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 5.13.0-52.59

---------------
linux (5.13.0-52.59) impish; urgency=medium

  * impish/linux: 5.13.0-52.59 -proposed tracker (LP: #1978628)

  * CVE-2022-28388
    - can: usb_8dev: usb_8dev_start_xmit(): fix double dev_kfree_skb() in error
      path

  * test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM
    connectivity through VXLAN (underlay in the default VRF) [FAIL])
    (LP: #1871015)
    - selftests: net: test_vxlan_under_vrf: fix HV connectivity test
    - selftests: test_vxlan_under_vrf: Fix broken test case

  * [UBUNTU 20.04] CPU-MF: add extended counter set definitions for new IBM z16
    (LP: #1974433)
    - s390/cpumf: add new extended counter set for IBM z16

  * [UBUNTU 20.04] KVM nesting support leaks too much memory, might result in
    stalls during cleanup (LP: #1974017)
    - KVM: s390: vsie/gmap: reduce gmap_rmap overhead

  * [UBUNTU 20.04] Null Pointer issue in nfs code running Ubuntu on IBM Z
    (LP: #1968096)
    - NFS: Fix up nfs_ctx_key_to_expire()

  * prevent kernel panic with overlayfs + shiftfs (LP: #1973620)
    - SAUCE: overlayfs: prevent dereferencing struct file in ovl_vm_prfile_set()

  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- update from kernel-versions (main/2022.05.30)

 -- Luke Nowakowski-Krijger <email address hidden> Wed, 15 Jun 2022 12:56:23 -0700

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 5.15.0-40.43

---------------
linux (5.15.0-40.43) jammy; urgency=medium

  * jammy/linux: 5.15.0-40.43 -proposed tracker (LP: #1978610)

  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- update from kernel-versions (main/2022.05.30)

  * [SRU][OEM-5.14/OEM-5.17/J][PATCH 0/2] Fix system hangs after s2idle on AMD
    A+A GPU (LP: #1975804)
    - Revert "drm/amd/pm: keep the BACO feature enabled for suspend"
    - drm/amd: Don't reset dGPUs if the system is going to s2idle

  * [SRU][OEM-5.14/OEM-5.17/J][PATCH 0/1] Read the discovery registers for
    AMD_SFH (LP: #1975798)
    - HID: amd_sfh: Add support for sensor discovery

  * [UBUNTU 20.04] CPU-MF: add extended counter set definitions for new IBM z16
    (LP: #1974433)
    - s390/cpumf: add new extended counter set for IBM z16

  * [UBUNTU 20.04] KVM nesting support leaks too much memory, might result in
    stalls during cleanup (LP: #1974017)
    - KVM: s390: vsie/gmap: reduce gmap_rmap overhead

  * [UBUNTU 20.04] Null Pointer issue in nfs code running Ubuntu on IBM Z
    (LP: #1968096)
    - NFS: Fix up nfs_ctx_key_to_expire()

  * Fix REG_WAIT timeout for Yellow Carp (LP: #1971417)
    - drm/amd/display: Clear encoder assignments when state cleared.
    - drm/amd/display: fix stale info in link encoder assignment
    - drm/amd/display: Query all entries in assignment table during updates.
    - drm/amd/display: Initialise encoder assignment when initialising dc_state

  * Enable hotspot feature for Realtek 8821CE (LP: #1969326)
    - rtw88: Add update beacon flow for AP mode
    - rtw88: 8821c: Enable TX report for management frames
    - rtw88: do PHY calibration while starting AP
    - rtw88: 8821c: fix debugfs rssi value
    - rtw88: add ieee80211:sta_rc_update ops

  * prevent kernel panic with overlayfs + shiftfs (LP: #1973620)
    - SAUCE: overlayfs: prevent dereferencing struct file in ovl_vm_prfile_set()

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

  * Mute/mic LEDs no function on Elitebook 630 (LP: #1974111)
    - ALSA: hda/realtek: fix right sounds and mute/micmute LEDs for HP machine

  * [Regression] Real-time Kernel Build Failure (LP: #1972899)
    - x86/mm: Include spinlock_t definition in pgtable.

  * build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI (LP: #1969434)
    - [Packaging] support standalone dkms module builds
    - [Packaging] drop do_<mod> arch specific configs

  * IPU6 camera has no function on Andrews MLK (LP: #1964983)
    - SAUCE: IPU6: 2022-03-11 alpha release for Andrews MLK
    - [Config] IPU6: enable OV02C10 sensor
    - SAUCE: IPU6: 2022-04-01 Andrews MLK PV release
    - SAUCE: spi: ljca: return when a sub-transaction first failed
    - SACUE: ljca: disable parallelly stub write
    - SAUCE: ljca: fix race condition issue in runtime PM
    - SAUCE: i2c-ljca: fix a null pointer access issue on tgl
    - SAUCE: ljca: fix a typo issue
    - SAUCE: ljca: assume stub enum failed as a warning
    - SAUCE: mei: cleanup header file including
    - SAUCE: intel_ulpss: Replaced by LJCA and remove
    ...

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2022-07-06 20:04 EDT-------
Fix verified and released, therefore we can close this bug.
Thanks everybody for your work.

Changing status to: CLOSED