[Kernel-packages] [Bug 2064266] Re: linux-virtual: recommends linux-tools and ubuntu-kernel-accessories

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Noble)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2064266

Title:
  linux-virtual: recommends linux-tools and ubuntu-kernel-accessories

Status in linux package in Ubuntu:
  New
Status in linux source package in Noble:
  Fix Committed

Bug description:
  [Impact]

  The linux-virtual meta is missing a recommends line (already present
  in every other noble/ubuntu kernel):

  ...
  Recommends: linux-tools-${kernel-abi-version}-generic, 
ubuntu-kernel-accessories
  ...

  [Fix]

  Apply the attached fix.

  [How to test]

  Install linux-virtual with '--install-recommends' and it should pull
  in:

  -linux-tools-${kernel-abi-version}-generic
  -ubuntu-kernel-accessories

  [Regression potential]

  Low: it's recommend line and it's already present in every other
  Ubuntu Noble kernel.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one

[Roxana Nicolescu]

** Changed in: linux-meta (Ubuntu Noble)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2061747

Title:
  obsolete out-of-tree ivsc dkms in favor of in-tree one

Status in ipu6-drivers package in Ubuntu:
  Fix Committed
Status in ivsc-driver package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  In Progress
Status in linux-meta package in Ubuntu:
  In Progress
Status in linux-meta-oem-6.8 package in Ubuntu:
  In Progress
Status in linux-oem-6.8 package in Ubuntu:
  In Progress
Status in ipu6-drivers source package in Noble:
  Fix Committed
Status in ivsc-driver source package in Noble:
  Invalid
Status in linux source package in Noble:
  Fix Committed
Status in linux-meta source package in Noble:
  Fix Committed
Status in linux-meta-oem-6.8 source package in Noble:
  In Progress
Status in linux-oem-6.8 source package in Noble:
  In Progress

Bug description:
  [SRU Justification]

  BugLink: https://bugs.launchpad.net/bugs/2061747

  == linux-meta, linux-meta-unstable, linux-meta-oem-6.8
  ==

  [Impact]

  Starting from kernel v6.8, Intel demands the use of in-tree VSC driver
  instead of the out-of-tree dkms originated from
  https://github.com/intel/ivsc-driver.

  [Fix]

  The main fixes are in kernel & dkms packages. This adds ivsc-modules to
  Provides list of linux-image-generic as other built-in linux-modules-foo
  packages do.

  [Test Case]

  The generated meta package linux-image-generic should then provides
  "ivsc-modules".

  [Where problems could occur]

  Meta package changes only. No real effect but in package dependency.

  [Other Info]

  While the ivsc-dkms obsoletion only happens for kernel >= 6.8, this will
  only be nominated for Unstable/Noble/OEM-6.8.

  == ipu6-drivers, linux, linux-oem-6.8 ==

  [Impact]

  Starting from kernel v6.8, Intel demands the use of in-tree VSC driver
  instead of the out-of-tree dkms originated from
  https://github.com/intel/ivsc-driver.

  [Fix]

  The in-tree vsc driver as of v6.8 still needs a few fixes to achieve
  the same support level to launch Intel IPU6 Camera devices. Commit
  1,3, and 4 are to add supported devices and platforms. Commit 2
  resolves an issue after resumed.

  [Test Case]

  This is supposed to work together with the updated dkms, which shall
  also be built along with the kernel itself as linux-modules-
  ipu6-. Install the corresponding kernel/modules packages and
  test camera functions.

  [Where problems could occur]

  While this is the first time we switch to in-tree VSC driver, and the
  out-of-tree driver is not aligned at the time of transition and
  probably never will, the provided functions and verified stability
  issues may vary.

  [Other Info]

  The dkms is created to be compatible of multiple kernel versions, yet
  the in-tree vsc driver transitioning should only happen for kernel >=
  v6.8. That is, oem-6.8, noble and linux-unstable will be nominated.

  == original bug description ==

  Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel
  demands the use of in-tree IVSC drivers instead of out-of-tree dkms
  from https://github.com/intel/ivsc-driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2061747/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Noble)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2061747

Title:
  obsolete out-of-tree ivsc dkms in favor of in-tree one

Status in ipu6-drivers package in Ubuntu:
  Fix Committed
Status in ivsc-driver package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  In Progress
Status in linux-meta package in Ubuntu:
  In Progress
Status in linux-meta-oem-6.8 package in Ubuntu:
  In Progress
Status in linux-oem-6.8 package in Ubuntu:
  In Progress
Status in ipu6-drivers source package in Noble:
  Fix Committed
Status in ivsc-driver source package in Noble:
  Invalid
Status in linux source package in Noble:
  Fix Committed
Status in linux-meta source package in Noble:
  In Progress
Status in linux-meta-oem-6.8 source package in Noble:
  In Progress
Status in linux-oem-6.8 source package in Noble:
  In Progress

Bug description:
  [SRU Justification]

  BugLink: https://bugs.launchpad.net/bugs/2061747

  == linux-meta, linux-meta-unstable, linux-meta-oem-6.8
  ==

  [Impact]

  Starting from kernel v6.8, Intel demands the use of in-tree VSC driver
  instead of the out-of-tree dkms originated from
  https://github.com/intel/ivsc-driver.

  [Fix]

  The main fixes are in kernel & dkms packages. This adds ivsc-modules to
  Provides list of linux-image-generic as other built-in linux-modules-foo
  packages do.

  [Test Case]

  The generated meta package linux-image-generic should then provides
  "ivsc-modules".

  [Where problems could occur]

  Meta package changes only. No real effect but in package dependency.

  [Other Info]

  While the ivsc-dkms obsoletion only happens for kernel >= 6.8, this will
  only be nominated for Unstable/Noble/OEM-6.8.

  == ipu6-drivers, linux, linux-oem-6.8 ==

  [Impact]

  Starting from kernel v6.8, Intel demands the use of in-tree VSC driver
  instead of the out-of-tree dkms originated from
  https://github.com/intel/ivsc-driver.

  [Fix]

  The in-tree vsc driver as of v6.8 still needs a few fixes to achieve
  the same support level to launch Intel IPU6 Camera devices. Commit
  1,3, and 4 are to add supported devices and platforms. Commit 2
  resolves an issue after resumed.

  [Test Case]

  This is supposed to work together with the updated dkms, which shall
  also be built along with the kernel itself as linux-modules-
  ipu6-. Install the corresponding kernel/modules packages and
  test camera functions.

  [Where problems could occur]

  While this is the first time we switch to in-tree VSC driver, and the
  out-of-tree driver is not aligned at the time of transition and
  probably never will, the provided functions and verified stability
  issues may vary.

  [Other Info]

  The dkms is created to be compatible of multiple kernel versions, yet
  the in-tree vsc driver transitioning should only happen for kernel >=
  v6.8. That is, oem-6.8, noble and linux-unstable will be nominated.

  == original bug description ==

  Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel
  demands the use of in-tree IVSC drivers instead of out-of-tree dkms
  from https://github.com/intel/ivsc-driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2061747/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2064266] Re: linux-virtual: recommends linux-tools and ubuntu-kernel-accessories

[Roxana Nicolescu]

** Also affects: linux (Ubuntu Noble)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2064266

Title:
  linux-virtual: recommends linux-tools and ubuntu-kernel-accessories

Status in linux package in Ubuntu:
  New
Status in linux source package in Noble:
  New

Bug description:
  [Impact]

  The linux-virtual meta is missing a recommends line (already present
  in every other noble/ubuntu kernel):

  ...
  Recommends: linux-tools-${kernel-abi-version}-generic, 
ubuntu-kernel-accessories
  ...

  [Fix]

  Apply the attached fix.

  [How to test]

  Install linux-virtual with '--install-recommends' and it should pull
  in:

  -linux-tools-${kernel-abi-version}-generic
  -ubuntu-kernel-accessories

  [Regression potential]

  Low: it's recommend line and it's already present in every other
  Ubuntu Noble kernel.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2042500] Re: Fix after-suspend-mediacard/sdhc-insert test failed

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Noble)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042500

Title:
  Fix after-suspend-mediacard/sdhc-insert test failed

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux-oem-6.8 package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux-oem-6.8 source package in Jammy:
  Invalid
Status in linux source package in Mantic:
  Won't Fix
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux-oem-6.8 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Fix Committed
Status in linux-oem-6.1 source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid
Status in linux-oem-6.8 source package in Noble:
  In Progress

Bug description:
  SRU Justification for Noble

  [Impact]
  checkbox test case, after-suspend-mediacard/sdhc-insert, failed.

  [Fix]
  The new series of the fix has been merged into v6.9

  6d4266675279 PCI/ASPM: Update save_state when configuration changes
  64dbb2d70744 PCI/ASPM: Disable L1 before configuring L1 Substates
  c198fafa0125 PCI/ASPM: Call pci_save_ltr_state() from pci_save_pcie_state()
  17423360a27a PCI/ASPM: Save L1 PM Substates Capability for suspend/resume
  1e11b5494c3d PCI/ASPM: Move pci_save_ltr_state() to aspm.c
  f3994bba8200 PCI/ASPM: Always build aspm.c
  fa84f4435a62 PCI/ASPM: Move pci_configure_ltr() to aspm.c

  [Test Case]
  1. suspend and resume.
  2. check if the error appears in dmesg
  ~~~
   pcieport :00:1c.0: pciehp: Slot(5): Card not present
   rtsx_pci :05:00.0: Unable to change power state from D0 to D3hot, device 
inaccessible
   rtsx_pci :05:00.0: Unable to change power state from D3cold to D0, 
device inaccessible
  ~~~

  [Where the problems could occur]
  Hard to evaluate, these patches change the PCI/ASPM behavior and may lead to 
PCI devices work abnormal.

  =
  [Impact]
  checkbox test case, after-suspend-mediacard/sdhc-insert, failed.

  [Fix]
  Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability
  for suspend/resume"") reverted saving and restoring of ASPM L1 Substates
  due to a regression that caused resume from suspend to fail on certain
  systems. However, we never added this capability back and this is now
  causing systems fail to enter low power CPU states, drawing more power
  from the battery.

  The original revert mentioned that we restore L1 PM substate configuration
  even though ASPM L1 may already be enabled. This is due the fact that
  the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state().

  Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4
  more closely by:

  1) Do not restore ASPM configuration in pci_restore_pcie_state() but
     do that after PCIe capability is restored in pci_restore_aspm_state()
     following PCIe r6.0, sec 5.5.4.

  2) ASPM is first enabled on the upstream component and then downstream
     (this is already forced by the parent-child ordering of Linux
     Device Power Management framework).

  3) Program ASPM L1 PM substate configuration before L1 enables.

  4) Program ASPM L1 PM substate enables last after rest of the fields
     in the capability are programmed.

  5) Add denylist that skips restoring on the ASUS and TUXEDO systems
     where these regressions happened, just in case. For the TUXEDO case
     we only skip restore if the BIOS is involved in system suspend
     (that's forcing "mem_sleep=deep" in the command line). This is to
     avoid possible power regression when the default suspend to idle is
     used, and at the same time make sure the devices continue working
     after resume when the BIOS is involved.

  [Test Case]
  1. suspend and resume.
  2. check if the error appears in dmesg
  ~~~
   pcieport :00:1c.0: pciehp: Slot(5): Card not present
   rtsx_pci :05:00.0: Unable to change power state from D0 to D3hot, device 
inaccessible
   rtsx_pci :05:00.0: Unable to change power state from D3cold to D0, 
device inaccessible
  ~~~

  [where the issue could happen]
  low, the patch works well on the reported malfunctioned ASUS platform too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042500/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : 

[Kernel-packages] [Bug 2062556] Re: [Ubuntu-24.04] Hugepage memory is not getting released even after destroying the guest!

[Roxana Nicolescu]

** Also affects: linux (Ubuntu Noble)
   Importance: High
   Status: Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2062556

Title:
  [Ubuntu-24.04] Hugepage memory is not getting released even after
  destroying the guest!

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Noble:
  Fix Committed

Bug description:
  ---Problem Description---

  Hugepages memory is not getting released even after destroying the guest
   
  Machine Type = P10 Denali LPAR 
   
  ---uname output---
  Linux ubuntu2404lp3 6.8.0-22-generic #22-Ubuntu SMP Thu Apr  4 22:47:57 UTC 
2024 ppc64le ppc64le ppc64le GNU/Linux

   
  ---Steps to Reproduce---
  1. Create a guest which is backed by hugepages.
  2. Destroy the guest
  3. execute "free -h" or "cat /proc/meminfo" to see that Hugepage memory is 
still getting held.
   
   
  HugePages_Total:   20480
  HugePages_Free:20419
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:   2048 kB
  Hugetlb:41943040 kB
  DirectMap4k:   0 kB
  DirectMap64k:52428800 kB
  DirectMap2M:   0 kB
  DirectMap1G:   0 kB
  root@ubuntu2404lp3:~# virsh list --all
   Id   Name   State
  ---
   -ramlp2g1   shut off
   -ramlp2g2   shut off
   -ramlp2g3   shut off
   -ramlp3g3   shut off

  root@ubuntu2404lp3:~# free -h
 totalusedfree  shared  buff/cache   
available
  Mem:48Gi43Gi   4.6Gi   2.6Mi   277Mi   
4.6Gi
  Swap:  8.0Gi   243Mi   7.8Gi
  root@ubuntu2404lp3:~#

  
  This is an issue created by commit 1b151e2435fc ("block: Remove 
special-casing of compound pages") that moved the direct-io hugetlb handling 
from compound pages to folios.

  Following commit has been proposed and merged into 6.9-rc1 which fixes this 
issue.
  38b43539d64b2fa020b3b9a752a986769f87f7a6("block: Fix page refcounts for 
unaligned buffers in __bio_release_pages()")

  So the same needs to be backported to the Ubuntu24.04 kernel as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2062556/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2060422] Re: Avoid creating non-working backlight sysfs knob from ASUS board

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Noble)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2060422

Title:
  Avoid creating non-working backlight sysfs knob from ASUS board

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  Backlight sysfs knobs created by asus-wmi don't really work, hence
  systemd-backlight services are in failed state.

  [Fix]
  Ensure the backlight device are really present

  [Test]
  With the fix applied, the backlight sysfs knobs are not longer present
  under /sys/class/backlight, so there's no more failed systemd-backlight
  service.

  [Where problems could occur]
  Though highly unlikely, but if there's working device that is created
  even when the WMI read is 0x, the device will be missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2060422/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2063096] Re: RTL8852BE fw security fail then lost WIFI function during suspend/resume cycle

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Noble)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2063096

Title:
  RTL8852BE fw security fail then lost WIFI function during
  suspend/resume cycle

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.5 source package in Jammy:
  New
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Fix Committed
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]

  On a Dell laptop, When we do suspend/resume test, we found the
  realtek wifi couldn't work after resume, from the dmesg, we found
  the error log as below:
  Log:
  三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: fw security 
fail
  三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: download 
firmware fail
  三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: [ERR]fwdl 
0x1E0 = 0x62
  三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: [ERR]fwdl 
0x83F2 = 0x8

  [Fix]

  Backport a commit from mainline kernel (linux-next), this will retry firmware
  loading for 5 times.

  [Test Case]

  run suspend/resume test case for over 100 times, the wifi still
  works.

  [Where problems could occur]

  This commit comes from mailine kernel, and it doesn't change existing
  driver except loading firmware a couple of more times if there is an error.
  In theory this will not introduce regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2063096/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2042546] Re: Include cifs.ko in linux-modules package

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Noble)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2042546

Title:
  Include cifs.ko in linux-modules package

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  Fix Committed

Bug description:
  [Impact]

  Commit: "smb: move client and server files to common directory fs/smb" moved 
the fs/cifs directory to fs/sb/client. The inclusion list for linux-modules was 
not updated, it still contains the old path. This means that the cifs.ko module 
cannot be loaded if only linux-modules package is installed, now being part of 
linux-modules-extra.
  For the main kernels this is not a problem because linux-modules-extra is 
always installed, but for derivatives like aws, azure etc, this module cannot 
be loaded without explicitly installing linux-modules-extra.

  [How to reproduce it]:
  1. Install the latest azure kernel 6.5.0-1017.17
  2. Load cifs module
  $ modprobe cifs
  modprobe: FATAL: Module cifs not found in directory 
/lib/modules/6.5.0-1017-azure
  If modules-extra is installed, this works.

  [Fix]

  Replace fs/cifs/* with fs/smb/client/* in
  debian./control.d/.inclusion-list. First the
  main kernels are addressed, derivatives will be fixed via cranky fix.

  [Test Plan]

  1. Apply the fix to one of the derivative (azure), build a new kernel and 
install it
  2. Load cifs module
  $ modprobe cifs
  It should work without installing modules-extra.

  [Regression potential]

  Very low, it's a straightforward fix.

  [Other Info]
  Sending a patch for every derivative takes time and each derivative will be 
fixed once this proposal is acked via cranky fix.

  Original for lunar only
  SRU Justification:

  [Impact]

  Commit: "smb: move client and server files to common directory fs/smb" 
introduced in 2023.09.04 moved the fs/cifs directory to fs/sb/client. The 
inclusion list for linux-modules was not updated, it still contains the old 
path. This means that the cifs.ko module cannot be loaded if only linux-modules 
package is installed, now being part of linux-modules-extra.
  For lunar:main this is not a problem because linux-modules-extra is always 
installed, but for derivatives like aws, azure etc, this module cannot be 
loaded without explicitly installing linux-modules-extra.

  [How to reproduce it]:
  1. Install the latest azure kernel 6.2.0-1016.16
  2. Load cifs module
  $ modprobe cifs
  modprobe: FATAL: Module cifs not found in directory 
/lib/modules/6.2.0-1016-azure
  If modules-extra is installed, this works.

  [Fix]

  Replace fs/cifs/* with fs/smb/client/* in 
debian./control.d/.inclusiojn-list
  This is going to be done in s2023.10.02 cycle for derivatives.

  [Test Plan]

  1. Apply the fix to one of the derivative (azure), build a new kernel and 
install it
  2. Load cifs module
  $ modprobe cifs
  It should work without installing modules-extra.

  [Regression potential]

  Very low, it's a straightforward fix.

  [Other Info]
  Sending a patch for every derivative takes time and each derivative will be 
fixed once this proposal is acked.
  There is also the possibility to do it via cranky fix, but owners may omit it 
during security updates and it's hard to enforce it. Plus, it is a one-time 
change.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2060531] Re: Noble update: v6.8.3 upstream stable release

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Noble)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2060531

Title:
  Noble update: v6.8.3 upstream stable release

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Noble:
  Fix Committed

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 v6.8.3 upstream stable release
 from git://git.kernel.org/

  
  Linux 6.8.3
  drm/sched: fix null-ptr-deref in init entity
  drm/amdgpu: fix use-after-free bug
  tools/resolve_btfids: fix build with musl libc
  x86/sev: Skip ROM range scans and validation for SEV-SNP guests
  perf/x86/amd/core: Update and fix stalled-cycles-* events for Zen 2 and later
  scsi: libsas: Fix disk not being scanned in after being removed
  scsi: libsas: Add a helper sas_get_sas_addr_and_dev_type()
  scsi: lpfc: Correct size for wqe for memset()
  scsi: lpfc: Correct size for cmdwqe/rspwqe for memset()
  usb: dwc3: pci: Drop duplicate ID
  Revert "x86/bugs: Use fixed addressing for VERW operand"
  x86/bugs: Use fixed addressing for VERW operand
  drm/amd/display: fix IPX enablement
  crash: use macro to add crashk_res into iomem early for specific arch
  x86/bugs: Fix the SRSO mitigation on Zen3/4
  scsi: qla2xxx: Delay I/O Abort on PCI error
  scsi: qla2xxx: Change debug message during driver unload
  scsi: qla2xxx: Fix double free of fcport
  scsi: qla2xxx: Fix double free of the ha->vp_map pointer
  scsi: qla2xxx: Fix command flush on cable pull
  scsi: qla2xxx: NVME|FCP prefer flag not being honored
  scsi: qla2xxx: Update manufacturer detail
  scsi: qla2xxx: Split FCE|EFT trace control
  scsi: qla2xxx: Fix N2N stuck connection
  scsi: qla2xxx: Prevent command send on chip reset
  usb: typec: ucsi: Clear UCSI_CCI_RESET_COMPLETE before reset
  usb: typec: ucsi_acpi: Refactor and fix DELL quirk
  usb: typec: ucsi: Ack unsupported commands
  usb: typec: ucsi: Clear EVENT_PENDING under PPM lock
  usb: typec: Return size of buffer if pd_set operation succeeds
  usb: typec: tcpm: Update PD of Type-C port upon pd_set
  usb: typec: tcpm: Correct port source pdo array in pd_set callback
  usb: typec: tcpm: fix double-free issue in tcpm_port_unregister_pd()
  usb: typec: ucsi: Fix race between typec_switch and role_switch
  usb: udc: remove warning when queue disabled ep
  usb: dwc2: gadget: LPM flow fix
  usb: dwc2: gadget: Fix exiting from clock gating
  usb: dwc2: host: Fix ISOC flow in DDMA mode
  usb: dwc2: host: Fix hibernation flow
  usb: dwc2: host: Fix remote wakeup from hibernation
  USB: core: Fix deadlock in port "disable" sysfs attribute
  USB: core: Add hub_get() and hub_put() routines
  USB: core: Fix deadlock in usb_deauthorize_interface()
  usb: dwc3: Properly set system wakeup
  genirq: Introduce IRQF_COND_ONESHOT and use it in pinctrl-amd
  staging: vc04_services: fix information leak in create_component()
  staging: vc04_services: changen strncpy() to strscpy_pad()
  scsi: core: Fix unremoved procfs host directory regression
  scsi: sd: Fix TCG OPAL unlock on system resume
  scsi: ufs: qcom: Provide default cycles_in_1us value
  ALSA: sh: aica: reorder cleanup operations to avoid UAF bugs
  btrfs: fix extent map leak in unexpected scenario at unpin_extent_cache()
  ring-buffer: Make wake once of ring_buffer_wait() more robust
  vfio/pds: Make sure migration file isn't accessed after reset
  USB: UAS: return ENODEV when submit urbs fail with device not attached
  usb: misc: ljca: Fix double free in error handling path
  usb: cdc-wdm: close race between read and workqueue
  Revert "usb: phy: generic: Get the vbus supply"
  mtd: spinand: Add support for 5-byte IDs
  Bluetooth: hci_sync: Fix not checking error on hci_cmd_sync_cancel_sync
  drm/amd/display: Fix bounds check for dcn35 DcfClocks
  drm/i915/gt: Reset queue_priority_hint on parking
  drm/i915: Pre-populate the cursor physical dma address
  drm/i915: Do not match JSL in ehl_combo_pll_div_frac_wa_needed()
  drm/i915/dsb: Fix DSB vblank waits when using VRR
  drm/i915/dsi: Go back to the previous INIT_OTP/DISPLAY_ON order, mostly
  drm/i915/vrr: Generate VRR "safe window" for DSB
  drm/i915/bios: Tolerate devdata==NULL in 
intel_bios_encoder_supports_dp_dual_mode()
  drm/i915/vma: Fix UAF on destroy against retire race
  drm/i915/hwmon: Fix locking inversion in sysfs getter
  drm/amd/display: Set DCN351 BB and IP the same as DCN35
  drm/amd/display: 

[Kernel-packages] [Bug 2061953] Re: intel_rapl_common: Add support for ARL and LNL

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Noble)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2061953

Title:
  intel_rapl_common: Add support for ARL and LNL

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-6.8 package in Ubuntu:
  Fix Released
Status in linux source package in Noble:
  Fix Committed
Status in linux-oem-6.8 source package in Noble:
  Fix Released

Bug description:
  [Impact]

  The installer doesn't work without blacklisting intel_rapl_common
  (snap mounts fail), unless these commits are added.

  Needs a oneliner fix for both platforms:

  4add6e841a3e079 powercap: intel_rapl: Add support for Arrow Lake
  876ed77fbed4450 powercap: intel_rapl: Add support for Lunar Lake-M paltform

  [Test case]

  Check that snaps work.

  [Regression potential]

  Can't regress other platforms, and if these would then fail in other
  ways, it's still likely better than before.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2061953/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2058557] Re: Kernel panic during checkbox stress_ng_test on Grace running noble 6.8 (arm64+largemem) kernel

[Roxana Nicolescu]

** Also affects: linux (Ubuntu Noble)
   Importance: Undecided
 Assignee: Mitchell Augustin (mitchellaugustin)
   Status: In Progress

** Changed in: linux (Ubuntu Noble)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2058557

Title:
  Kernel panic during checkbox stress_ng_test on Grace running noble 6.8
  (arm64+largemem) kernel

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Noble:
  Fix Committed

Bug description:
  A kernel oops and panic occurred during 22.04 SoC certification on
  Gunyolk (Grace/Grace) with 6.8 kernel, arm64+largemem variant

  Steps to reproduce:
  Run (as root) the following commands:

  add-apt-repository -y ppa:checkbox-dev/stable
  apt-add-repository -y ppa:firmware-testing-team/ppa-fwts-stable
  apt update
  apt install -y canonical-certification-server
  /usr/lib/checkbox-provider-base/bin/stress_ng_test.py disk --device dm-0 
--base-time 240

  stress_ng_test caused a kernel panic after about 5 minutes. I have
  attached dmesg output from my reproducer to this report.

  Initially, this was identified via a panic during the above test,
  which was running as part of a run of certify-soc-22.04.

  Attached is a tarball containing:

  - apport.linux-image-6.8.0-11-generic-64k.kzsondji.apport: The output of 
`ubuntu-bug linux` on the machine (after reboot)
  - reproduced-dmesg.202403201942: The dmesg output captured by kdump when I 
reproduced my original issue by running only the single stress_ng_test.py 
command above (not the entire cert suite)
  - original-dmesg.txt: The dmesg output I captured when the stress_ng_test 
originally failed during the full cert suite run

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2063096] Re: RTL8852BE fw security fail then lost WIFI function during suspend/resume cycle

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Jammy)
   Status: New => Fix Committed

** Changed in: linux (Ubuntu Mantic)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2063096

Title:
  RTL8852BE fw security fail then lost WIFI function during
  suspend/resume cycle

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.5 source package in Jammy:
  New
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  New
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]

  On a Dell laptop, When we do suspend/resume test, we found the
  realtek wifi couldn't work after resume, from the dmesg, we found
  the error log as below:
  Log:
  三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: fw security 
fail
  三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: download 
firmware fail
  三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: [ERR]fwdl 
0x1E0 = 0x62
  三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: [ERR]fwdl 
0x83F2 = 0x8

  [Fix]

  Backport a commit from mainline kernel (linux-next), this will retry firmware
  loading for 5 times.

  [Test Case]

  run suspend/resume test case for over 100 times, the wifi still
  works.

  [Where problems could occur]

  This commit comes from mailine kernel, and it doesn't change existing
  driver except loading firmware a couple of more times if there is an error.
  In theory this will not introduce regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2063096/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2063067] Re: Fix bluetooth connections with 3.0 device

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Mantic)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Jammy)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2063067

Title:
  Fix bluetooth connections with 3.0 device

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  Bluetooth keyboard cannot be connected to Realtek BT controller.

  [Fix]
  It's a regression from Ubuntu-6.5.0-20.20 and Ubuntu-oem-6.5-6.5.0-1016.17
  The bad commit:
  c7f59461f5a78 ("Bluetooth: Fix a refcnt underflow problem for hci_conn")
  Fix:
  7e74aa53a68bf ("Bluetooth: hci_event: Fix handling of HCI_EV_IO_CAPA_REQUEST")

  [Test]
  Tested on hardware, the bt3.0 keyboard connects to host well.

  [Where problems could occur]
  It may break bluetooth.

  The commit is already in v6.8-rc7,
  SRU Jammy, oem-6.5 and Mantic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2063067/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2061986] Re: Mount CIFS fails with Permission denied

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Jammy)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2061986

Title:
  Mount CIFS fails with Permission denied

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * Mounting SMB share from server without Key Exchange capability is
  failing with Access Denied error

   * Even though SMB server during Session Setup Response in NTLMSSP_CHALLANGE 
message does not advertise
 Key Exchange capabilities SMB client < 5.16 will forcefully use it leading 
to error response during
 TCON requests.

   * Issue can be reproduced on 5.15 or older Kernels, there is no reproduction 
on 6.5 Kernel
   
   * This scenario was fixed in upstream commit 
9de0737d5ba0425c3154d5d83da12a8fa8595c0f
   
   * An example of server without Key Exchange capability is Oracle Solaris 
11.4 SMB zfs, meaning
 mounting share from that server will result in ACCESS_DENIED error.
   
  [ Test Plan ]

   * So far issue was reported only with Oracle Solaris 11.04 smb server
  and Ubuntu with Kernel <= 5.15

   * To reproduce, setup Oracle Solaris SMB server and try to mount share on 
22.04/20.04 (5.15/5.04)
 Steps to configure SMB server:
  1. Download the ISO for Oracle Solaris Common Build Edition [1]
  2. Create a VM with at least 16 GB of memory - I have experienced 
installation issues with less memory
  3. Install Oracle Solaris using the downloaded ISO
  a. Make sure to create a test user
  4. Log into the VM as the root user
  5. Create a test directory for the share:
  a. mkdir /smbshare && chmod 777 /smbshare 
  6. Disable the normal Samba daemon: [2]
  a. svcadm disable svc:/network/samba
  b. svcadm disable svc:/network/wins
  7 Configure the server to serve Samba shares using ZFS in Workgroup mode [3]
  a. svcadm enable -r smb/server
  b. smbadm join -w workgroup
  8 Update the /etc/pam.d/other file to require authentication by adding the 
following line:
  a. password requiredpam_smb_passwd.so.1nowarn
  9. Reset the password for the test user so that it is updated in the SMB 
password database
  10. Create the pool and share it using Samba: [4]
  a. zfs create -o mountpoint=/smbshare/ rpool/smbshare
  b. zfs share -o share.smb=on rpool/smbshare%share

  [1] 

  [2] 

  [3] 

  [4] 


   * With server configured, mount share using ubuntu SMB client
 Expected result: mount operation should succeed
 Actual result: mount returns following error:
  root@ubuntu20:/mnt# mount -t cifs -o username=rmalz //192.168.50.217/smbshare 
test
  Password for rmalz@//192.168.50.217/smbshare:  
  mount error(13): Permission denied
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log 
messages (dmesg) 

  [ Where problems could occur ]

   * Upstream patch is changing smb client behavior based on server 
NTLMSSP_CHALLENGE Negotiate Flags,
 if server does not advertise Key Exchange Capability but requires it from 
client communication might
 be broken. It is unknown if such servers are used, such instance should be 
treated as a server bug.

   * Patch is available in upstream kernel since 5.16, any issues associated 
with it should be already
 detected.

   * Patch adds additional requirement checks on server NTLM flags, although it 
is possible to hit
 these checks, I was not able to find any instances of that occurring.

   * To lower regression potential, upstream patch backported to Ubuntu 5.15 
and 5.04 Kernels have been
 tested in following environments:
 smb server: Oracle Solaris 11.04, Ubuntu 22.04 HWE
 smb client: Ubuntu 22.04, Ubuntu 20.04
 During testing no issues have been detected.

  [ Other Info ]
   
   * Error message coming from SMB client is the same as providing incorrect 
credentials, which might
 confuse users. 
   * Attaching tcpdump pcaps with SMB operations from 5.15 Kernel with and 
without patch.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : 

[Kernel-packages] [Bug 2040948] Re: USB stick can't be detected

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Focal)
   Status: Triaged => Fix Committed

** Changed in: linux (Ubuntu Jammy)
   Status: Triaged => Fix Committed

** Changed in: linux (Ubuntu Mantic)
   Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2040948

Title:
  USB stick can't be detected

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Focal:
  Fix Committed
Status in linux-signed-hwe-5.15 source package in Focal:
  New
Status in linux-signed-oem-6.1 source package in Focal:
  New
Status in linux source package in Jammy:
  Fix Committed
Status in linux-signed-hwe-5.15 source package in Jammy:
  New
Status in linux-signed-oem-6.1 source package in Jammy:
  New
Status in linux source package in Mantic:
  Fix Committed
Status in linux-signed-hwe-5.15 source package in Mantic:
  New
Status in linux-signed-oem-6.1 source package in Mantic:
  New
Status in linux source package in Noble:
  Triaged
Status in linux-signed-hwe-5.15 source package in Noble:
  Won't Fix
Status in linux-signed-oem-6.1 source package in Noble:
  Won't Fix

Bug description:
  [Summary]

  During SRU testing, I found some of devices failed to run the usb
  test, when I re-plugged the usb stick, it can be detected, but after
  rebooting, usb stick is gone again.

  I did some further checks and found that If I power cycle the device,
  it can be detected again.

  It seems to happen on the device plugged with a Sandisk usb stick.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.1.0-1025-oem 6.1.0-1025.25
  ProcVersionSignature: Ubuntu 6.1.0-1025.25-oem 6.1.57
  Uname: Linux 6.1.0-1025-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5json:
   {
 "result": "skip"
   }
  Date: Thu Oct 26 10:37:58 2023
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-lapras+X64
  InstallationDate: Installed on 2023-09-04 (51 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
somerville-jammy-amd64-20220504-33
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-oem-6.1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2060919] Re: cifs: Copying file to same directory results in page fault

[Roxana Nicolescu]

Hi all,

This fix should be released in ~2 weeks.

** Changed in: linux (Ubuntu Mantic)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2060919

Title:
  cifs: Copying file to same directory results in page fault

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/2060919

  [Impact]

  Copying or modifying a file to the same directory within a cifs mount
  results in a page fault, and the process that initiated the copy being
  killed. This could be cp, nautilus, etc.

  This results in the following oops:

  BUG: unable to handle page fault for address: fffe
  #PF: supervisor read access in kernel mode
  #PF: error_code(0x) - not-present page
  PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 0
  Oops:  [#1] PREEMPT SMP NOPTI
  CPU: 0 PID: 28103 Comm: Thread (pooled) Tainted: P OE 6.5.0-27-generic 
#28-Ubuntu
  RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs]
  Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 0c 53 48 83 ec 08 48 8b 7f 30 44 
89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 db 74 77 <48> 8b 13 b8 00 10 00 00 
f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3
  RSP: 0018:aab6865ffbf8 EFLAGS: 00010282
  RAX:  RBX: fffe RCX: 
  RDX:  RSI:  RDI: 
  RBP: aab6865ffc28 R08: 0001 R09: 
  R10: 00023854 R11:  R12: 
  R13: aab6865ffc78 R14: 906675d8aed0 R15: aab6865ffc70
  FS: 7bd4d594b6c0() GS:90753f80() knlGS:
  CS: 0010 DS:  ES:  CR0: 80050033
  CR2: fffe CR3: 00017022a000 CR4: 00750ef0
  PKRU: 5554
  Call Trace:
  
  ? show_regs+0x6d/0x80
  ? __die+0x24/0x80
  ? page_fault_oops+0x99/0x1b0
  ? kernelmode_fixup_or_oops+0xb2/0x140
  ? __bad_area_nosemaphore+0x1a5/0x2c0
  ? bad_area_nosemaphore+0x16/0x30
  ? do_kern_addr_fault+0x7b/0xa0
  ? exc_page_fault+0x1a4/0x1b0
  ? asm_exc_page_fault+0x27/0x30
  ? cifs_flush_folio+0x41/0xf0 [cifs]
  ? cifs_flush_folio+0x37/0xf0 [cifs]
  cifs_remap_file_range+0x172/0x660 [cifs]
  do_clone_file_range+0x101/0x2d0
  vfs_clone_file_range+0x3f/0x150
  ioctl_file_clone+0x52/0xc0
  do_vfs_ioctl+0x68f/0x910
  ? __fget_light+0xa5/0x120
  __x64_sys_ioctl+0x7d/0xf0
  do_syscall_64+0x59/0x90
  ? kmem_cache_free+0x22/0x3e0
  ? putname+0x5b/0x80
  ? exit_to_user_mode_prepare+0x30/0xb0
  ? syscall_exit_to_user_mode+0x37/0x60
  ? do_syscall_64+0x68/0x90
  ? do_syscall_64+0x68/0x90
  ? do_syscall_64+0x68/0x90

  There is no known workaround.

  [Fix]

  The stacktrace is very similar to a regression reported to upstream
  6.1.y:

  https://lore.kernel.org/linux-
  mm/a76b370f93cb928c049b94e1fde0d2da506dfcb2.ca...@amazon.com/T/

  The thread mentions that:

  commit 7b2404a886f8b91250c31855d287e632123e1746
  Author: David Howells 
  Date: Fri Dec 1 00:22:00 2023 +
  Subject: cifs: Fix flushing, invalidation and file size with copy_file_range()
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7b2404a886f8b91250c31855d287e632123e1746

  introduced the issue to Debian's 6.1 kernel.

  This got backported to Ubuntu in:

  commit 3adbe2ccd8b9b8fde93e03958d6176945794d288
  Author: David Howells 
  Date: Fri Dec 1 00:22:00 2023 +
  Subject: cifs: Fix flushing, invalidation and file size with copy_file_range()

  $ git describe --contains 3adbe2ccd8b9b8fde93e03958d6176945794d288
  Ubuntu-6.5.0-20.20~107

  Which we have been using for some time now, and is not the culprit.

  Reading the regression mailing list thread, they mention that things
  work differently in 6.1:

  > Yeah.  __filemap_get_folio() works differently in v6.1.y. There it returns a
  > folio or NULL.  In 6.7 it returns a folio or a negative error code.  The 
error
  > check in cifs_flush_folio() needs to change to something like:
  >
  > folio = filemap_get_folio(inode->i_mapping, index);
  > if (!folio)
  > return -ENOMEM;
  >
  > David 

  6.1.y then got a specific patch to fix the issue in 6.1, which is:

  commit 21bb2ba4f1ac1e3a57594be62dd74e7b1401b2b1
  Author: Steve French 
  Date: Fri Jan 12 23:08:51 2024 -0600
  Subject: cifs: fix flushing folio regression for 6.1 backport
  Link: 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/mantic/commit/?id=21bb2ba4f1ac1e3a57594be62dd74e7b1401b2b1

  $ git describe --contains 21bb2ba4f1ac1e3a57594be62dd74e7b1401b2b1
  Ubuntu-6.5.0-27.28~162

  Since the Ubuntu mantic kernel consumes both 6.1.y and 6.7.y / 6.8.y
  stable patches, this patch was applied to mantic's 6.5 kernel by
  mistake, and contains the wrong logic for how __filemap_get_folio()
  works in 6.5.

  The fix 

[Kernel-packages] [Bug 2054487] Re: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Mantic)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2054487

Title:
  There is sound from the speakers and headphones at the same time on
  Oasis 14 and 16 platforms

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Fix Released
Status in linux-oem-6.1 source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  While playing audio with headset plugged, the sound play from both headset 
and internal speaker.

  [Fix]
  The commit from v6.8-rc5 fixes the issue
  fddab35fd064 ALSA: hda/realtek: add IDs for Dell dual spk platform

  To avoid conflict pull in one more quirk from v6.8-rc3
  fcfc9f711d1e ALSA: hda/realtek - Add speaker pin verbtable for Dell dual 
speaker platform

  [Test Case]
  1. play an audio file.
  2. plug 3.5mm headset.
  3. select "headset".
  4. sound will play only from headset

  [Where problems could occur]
  It simply added 2 IDs to the table, should have no impact to the existing 
machines.
  The other commit add one more ID to the table and disable speaker passthrough.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2054487/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2063290] Re: Jammy update: v5.15.153 upstream stable release

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Jammy)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2063290

Title:
  Jammy update: v5.15.153 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 v5.15.153 upstream stable release
 from git://git.kernel.org/

  io_uring/unix: drop usage of io_uring socket
  io_uring: drop any code related to SCM_RIGHTS
  rcu-tasks: Provide rcu_trace_implies_rcu_gp()
  bpf: Defer the free of inner map when necessary
  selftests: tls: use exact comparison in recv_partial
  ASoC: rt5645: Make LattePanda board DMI match more precise
  x86/xen: Add some null pointer checking to smp.c
  MIPS: Clear Cause.BD in instruction_pointer_set
  HID: multitouch: Add required quirk for Synaptics 0xcddc device
  gen_compile_commands: fix invalid escape sequence warning
  RDMA/mlx5: Fix fortify source warning while accessing Eth segment
  RDMA/mlx5: Relax DEVX access upon modify commands
  riscv: dts: sifive: add missing #interrupt-cells to pmic
  x86/mm: Move is_vsyscall_vaddr() into asm/vsyscall.h
  x86/mm: Disallow vsyscall page read for copy_from_kernel_nofault()
  net/iucv: fix the allocation size of iucv_path_table array
  parisc/ftrace: add missing CONFIG_DYNAMIC_FTRACE check
  block: sed-opal: handle empty atoms when parsing response
  dm-verity, dm-crypt: align "struct bvec_iter" correctly
  scsi: mpt3sas: Prevent sending diag_reset when the controller is ready
  ALSA: hda/realtek - ALC285 reduce pop noise from Headphone port
  drm/amdgpu: Enable gpu reset for S3 abort cases on Raven series
  Bluetooth: rfcomm: Fix null-ptr-deref in rfcomm_check_security
  firewire: core: use long bus reset on gap count error
  ASoC: Intel: bytcr_rt5640: Add an extra entry for the Chuwi Vi8 tablet
  Input: gpio_keys_polled - suppress deferred probe error for gpio
  ASoC: wm8962: Enable oscillator if selecting WM8962_FLL_OSC
  ASoC: wm8962: Enable both SPKOUTR_ENA and SPKOUTL_ENA in mono mode
  ASoC: wm8962: Fix up incorrect error message in wm8962_set_fll
  do_sys_name_to_handle(): use kzalloc() to fix kernel-infoleak
  s390/dasd: put block allocation in separate function
  s390/dasd: add query PPRC function
  s390/dasd: add copy pair setup
  s390/dasd: add autoquiesce feature
  s390/dasd: Use dev_*() for device log messages
  s390/dasd: fix double module refcount decrement
  fs/select: rework stack allocation hack for clang
  md: Don't clear MD_CLOSING when the raid is about to stop
  lib/cmdline: Fix an invalid format specifier in an assertion msg
  time: test: Fix incorrect format specifier
  rtc: test: Fix invalid format specifier.
  aoe: fix the potential use-after-free problem in aoecmd_cfg_pkts
  timekeeping: Fix cross-timestamp interpolation on counter wrap
  timekeeping: Fix cross-timestamp interpolation corner case decision
  timekeeping: Fix cross-timestamp interpolation for non-x86
  sched/fair: Take the scheduling domain into account in select_idle_core()
  wifi: ath10k: fix NULL pointer dereference in 
ath10k_wmi_tlv_op_pull_mgmt_tx_compl_ev()
  wifi: b43: Stop/wake correct queue in DMA Tx path when QoS is disabled
  wifi: b43: Stop/wake correct queue in PIO Tx path when QoS is disabled
  wifi: b43: Stop correct queue in DMA worker when QoS is disabled
  wifi: b43: Disable QoS for bcm4331
  wifi: wilc1000: fix declarations ordering
  wifi: wilc1000: fix RCU usage in connect path
  wifi: rtl8xxxu: add cancel_work_sync() for c2hcmd_work
  wifi: wilc1000: fix multi-vif management when deleting a vif
  wifi: mwifiex: debugfs: Drop unnecessary error check for debugfs_create_dir()
  cpufreq: brcmstb-avs-cpufreq: add check for cpufreq_cpu_get's return value
  cpufreq: Explicitly include correct DT includes
  cpufreq: mediatek-hw: Wait for CPU supplies before probing
  sock_diag: annotate data-races around sock_diag_handlers[family]
  inet_diag: annotate data-races around inet_diag_table[]
  bpftool: Silence build warning about calloc()
  af_unix: Annotate data-race of gc_in_progress in wait_for_unix_gc().
  cpufreq: mediatek-hw: Don't error out if supply is not found
  arm64: dts: imx8mm-kontron: Disable pullups for I2C signals on SL/BL i.MX8MM
  arm64: dts: imx8mm-kontron: Disable pullups for onboard UART signals on BL 
board
  arm64: dts: imx8mm-kontron: Add support for ultra high speed 

[Kernel-packages] [Bug 2063276] Re: Jammy update: v5.15.152 upstream stable release

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Jammy)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2063276

Title:
  Jammy update: v5.15.152 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 v5.15.152 upstream stable release
 from git://git.kernel.org/

  mmc: mmci: stm32: use a buffer for unaligned DMA requests
  mmc: mmci: stm32: fix DMA API overlapping mappings warning
  net: lan78xx: fix runtime PM count underflow on link stop
  ixgbe: {dis, en}able irqs in ixgbe_txrx_ring_{dis, en}able
  i40e: disable NAPI right after disabling irqs when handling xsk_pool
  tracing/net_sched: Fix tracepoints that save qdisc_dev() as a string
  geneve: make sure to pull inner header in geneve_rx()
  net: sparx5: Fix use after free inside sparx5_del_mact_entry
  net: ice: Fix potential NULL pointer dereference in ice_bridge_setlink()
  net/ipv6: avoid possible UAF in ip6_route_mpath_notify()
  cpumap: Zero-initialise xdp_rxq_info struct before running XDP program
  net/rds: fix WARNING in rds_conn_connect_if_down
  netfilter: nft_ct: fix l3num expectations with inet pseudo family
  netfilter: nf_conntrack_h323: Add protection for bmp length out of range
  erofs: apply proper VMA alignment for memory mapped files on THP
  netrom: Fix a data-race around sysctl_netrom_default_path_quality
  netrom: Fix a data-race around sysctl_netrom_obsolescence_count_initialiser
  netrom: Fix data-races around sysctl_netrom_network_ttl_initialiser
  netrom: Fix a data-race around sysctl_netrom_transport_timeout
  netrom: Fix a data-race around sysctl_netrom_transport_maximum_tries
  netrom: Fix a data-race around sysctl_netrom_transport_acknowledge_delay
  netrom: Fix a data-race around sysctl_netrom_transport_busy_delay
  netrom: Fix a data-race around sysctl_netrom_transport_requested_window_size
  netrom: Fix a data-race around sysctl_netrom_transport_no_activity_timeout
  netrom: Fix a data-race around sysctl_netrom_routing_control
  netrom: Fix a data-race around sysctl_netrom_link_fails_count
  netrom: Fix data-races around sysctl_net_busy_read
  ALSA: usb-audio: Refcount multiple accesses on the single clock
  ALSA: usb-audio: Clear fixed clock rate at closing EP
  ALSA: usb-audio: Split endpoint setups for hw_params and prepare (take#2)
  ALSA: usb-audio: Properly refcounting clock rate
  ALSA: usb-audio: Apply mutex around snd_usb_endpoint_set_params()
  ALSA: usb-audio: Correct the return code from snd_usb_endpoint_set_params()
  ALSA: usb-audio: Avoid superfluous endpoint setup
  ALSA: usb-audio: Add quirk for Tascam Model 12
  ALSA: usb-audio: Add new quirk FIXED_RATE for JBL Quantum810 Wireless
  ALSA: usb-audio: Fix microphone sound on Nexigo webcam.
  ALSA: usb-audio: add quirk for RODE NT-USB+
  drm/amd/display: Fix uninitialized variable usage in core_link_ 'read_dpcd() 
& write_dpcd()' functions
  nfp: flower: add goto_chain_index for ct entry
  nfp: flower: add hardware offload check for post ct entry
  selftests/mm: switch to bash from sh
  selftests: mm: fix map_hugetlb failure on 64K page size systems
  xhci: process isoc TD properly when there was a transaction error mid TD.
  xhci: handle isoc Babble and Buffer Overrun events properly
  serial: max310x: use regmap methods for SPI batch operations
  serial: max310x: use a separate regmap for each port
  serial: max310x: prevent infinite while() loop in port startup
  drm/amd/pm: do not expose the API used internally only in kv_dpm.c
  drm/amdgpu: Reset IH OVERFLOW_CLEAR bit
  selftests: mptcp: decrease BW in simult flows
  hv_netvsc: use netif_is_bond_master() instead of open code
  hv_netvsc: Register VF in netvsc_probe if NET_DEVICE_REGISTER missed
  drm/amd/display: Re-arrange FPU code structure for dcn2x
  drm/amd/display: move calcs folder into DML
  drm/amd/display: remove DML Makefile duplicate lines
  drm/amd/display: Increase frame-larger-than for all display_mode_vba files
  getrusage: add the "signal_struct *sig" local variable
  getrusage: move thread_group_cputime_adjusted() outside of lock_task_sighand()
  getrusage: use __for_each_thread()
  getrusage: use sig->stats_lock rather than lock_task_sighand()
  proc: Use task_is_running() for wchan in /proc/$pid/stat
  fs/proc: do_task_stat: move thread_group_cputime_adjusted() outside of 

[Kernel-packages] [Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic

[Roxana Nicolescu]

@ivan.hu Can you please test if dropping these 2 patches work? This is a
temporary solution to start the next cycle, we'll need to find a proper
one though.

thermal: core: Store trip pointer in struct thermal_instance
thermal: trip: Drop lockdep assertion from thermal_zone_trip_id()

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2061940

Title:
  Some DUTs can't boot up after installing the proposed kernel on Mantic

Status in linux package in Ubuntu:
  In Progress

Bug description:
  During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at 
very early stage of booting process.
  The last messages displayed on the screen are:
  EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
  EFI stub: Measured initrd data into PCR 9

  There are no journal logs existed when it boot with the 6.5.0-33
  kernel.

  Here is the list of the impacted machines that I found so far
  https://certification.canonical.com/hardware/202106-29206/
  https://certification.canonical.com/hardware/202106-29207/
  https://certification.canonical.com/hardware/201912-27623/
  https://certification.canonical.com/hardware/202007-28059/
  https://certification.canonical.com/hardware/202103-28762/
  https://certification.canonical.com/hardware/202012-28510/

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2060727] Re: The keyboard does not work after latest kernel update

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Mantic)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2060727

Title:
  The keyboard does not work after latest kernel update

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  The computer is a ThinkPad L15 Gen 4, its integrated keyboard does not
  work after the latest kernel update and its subsequent reboot of the
  laptop. Nothing else is connected to the laptop.

  --

  In /var/log/apt/history.log , the latest we can see is:

  Start-Date: 2024-04-09  12:37:28
  Commandline: apt full-upgrade
  Install: linux-modules-extra-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27:amd64 (6.5.0-27.28, automatic), 
linux-modules-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-image-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic)
  Upgrade: linux-headers-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), 
linux-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-image-generic:amd64 
(6.5.0.26.26, 6.5.0.27.27), linux-libc-dev:amd64 (6.5.0-26.26, 6.5.0-27.28)
  End-Date: 2024-04-09  12:37:51

  --

  $ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.10
  Release:23.10

  $ # Note: It's Kubuntu 23.10

  --

  $ uname -a
  Linux tp 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar  7 18:21:00 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  SRU Justification:
  ==
  [Impact]
  Keyboard is lost after updated to 6.5.0-27 and oem-6.5-1019 kernel
  versions.

  [Fix]
  Regression commit is found commit:
  936e4d49ecbc ("Input: atkbd - skip ATKBD_CMD_GETID in translated mode")

  Fixes:
  9cf6e24c9fbf1 Input: atkbd - do not skip atkbd_deactivate() when
  skipping ATKBD_CMD_GETID
  683cd8259a9b8 Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping
  ATKBD_CMD_GETID

  [Test]
  Tested on hardware, keyboard works fine after bootup.

  The regression commit is only in 6.5 stable, so SRU for 6.5 only.

  [Where problems could occur]
  It may break keyboard.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2057734] Re: proc_sched_rt01 from ubuntu_ltp failed

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Mantic)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Xenial)
   Status: Confirmed => Won't Fix

** Changed in: linux (Ubuntu Bionic)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2057734

Title:
  proc_sched_rt01 from ubuntu_ltp failed

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Won't Fix
Status in linux source package in Bionic:
  Won't Fix
Status in linux source package in Focal:
  Confirmed
Status in linux source package in Jammy:
  Confirmed
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  [Impact]
  The updated LTP has added proc_sched_rt01 testcase which can't pass
  since several commits are missed from kernel side.

  Test log:
  INFO: Test start time: Tue Mar 12 11:52:21 UTC 2024
  COMMAND: /opt/ltp/bin/ltp-pan -q -e -S -a 163430 -n 163430 -f 
/tmp/ltp-X3Nz2HWCQe/alltests -l /dev/null -C /dev/null -T /dev/null
  LOG File: /dev/null
  FAILED COMMAND File: /dev/null
  TCONF COMMAND File: /dev/null
  Running tests...
  tst_kconfig.c:87: TINFO: Parsing kernel config 
'/lib/modules/6.5.0-27-generic/build/.config'
  tst_test.c:1741: TINFO: LTP version: 20230929-406-gcbc2d0568
  tst_test.c:1625: TINFO: Timeout per run is 0h 00m 30s
  proc_sched_rt01.c:45: TFAIL: Expect: timeslice_ms > 0 after reset to default
  proc_sched_rt01.c:51: TPASS: echo 0 > /proc/sys/kernel/sched_rt_period_us : 
EINVAL (22)
  proc_sched_rt01.c:53: TFAIL: echo -1 > /proc/sys/kernel/sched_rt_period_us 
invalid retval 2: SUCCESS (0)
  proc_sched_rt01.c:59: TPASS: echo -2 > /proc/sys/kernel/sched_rt_runtime_us : 
EINVAL (22)
  proc_sched_rt01.c:72: TFAIL: echo rt_period_us+1 > 
/proc/sys/kernel/sched_rt_runtime_us invalid retval 1: SUCCESS (0)

  HINT: You _MAY_ be missing kernel fixes:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c1fc6484e1fb
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=079be8fc6309

  [Fix]
  There are 3 relevant commits from upstream.

  1. 079be8fc6309 sched/rt: Disallow writing invalid values to 
sched_rt_period_us
  2. c1fc6484e1fb sched/rt: sysctl_sched_rr_timeslice show default timeslice 
after reset
  3. c7fcb99877f9 sched/rt: Fix sysctl_sched_rr_timeslice intial value

  Mantic: the 3rd is already in master-next.
  Jammy: stable v5.15.150 includes the three commits.
  Focal: master-next has include them after update to v5.4.270
  Bionic: all the three commits are needed.

  [Test case]
  Run LTP update 20240312 to check the log of proc_sched_rt01.

  [Regression potential]
  Low risk since these content are existed in upstream for a while.

  Cyril Hrubis (2):
sched/rt: sysctl_sched_rr_timeslice show default timeslice after reset
sched/rt: Disallow writing invalid values to sched_rt_period_us

   kernel/sched/rt.c | 12 
   1 file changed, 8 insertions(+), 4 deletions(-)

  
  [Original Bug Description]
  This is a new test case, issue found on M/J/F/B when testing LTP update 
20240312

  Test log:
  INFO: Test start time: Tue Mar 12 11:52:21 UTC 2024
  COMMAND:/opt/ltp/bin/ltp-pan -q  -e -S   -a 163430 -n 163430  -f 
/tmp/ltp-X3Nz2HWCQe/alltests -l /dev/null  -C /dev/null -T /dev/null
  LOG File: /dev/null
  FAILED COMMAND File: /dev/null
  TCONF COMMAND File: /dev/null
  Running tests...
  tst_kconfig.c:87: TINFO: Parsing kernel config 
'/lib/modules/6.5.0-27-generic/build/.config'
  tst_test.c:1741: TINFO: LTP version: 20230929-406-gcbc2d0568
  tst_test.c:1625: TINFO: Timeout per run is 0h 00m 30s
  proc_sched_rt01.c:45: TFAIL: Expect: timeslice_ms > 0 after reset to default
  proc_sched_rt01.c:51: TPASS: echo 0 > /proc/sys/kernel/sched_rt_period_us : 
EINVAL (22)
  proc_sched_rt01.c:53: TFAIL: echo -1 > /proc/sys/kernel/sched_rt_period_us 
invalid retval 2: SUCCESS (0)
  proc_sched_rt01.c:59: TPASS: echo -2 > /proc/sys/kernel/sched_rt_runtime_us : 
EINVAL (22)
  proc_sched_rt01.c:72: TFAIL: echo rt_period_us+1 > 
/proc/sys/kernel/sched_rt_runtime_us invalid retval 1: SUCCESS (0)

  HINT: You _MAY_ be missing kernel fixes:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c1fc6484e1fb
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=079be8fc6309

  Summary:
  passed   2
  failed   3
  broken   0
  skipped  0
  warnings 0
  INFO: ltp-pan reported some tests FAIL
  LTP Version: 20230929-406-gcbc2d0568
  INFO: Test end time: Tue Mar 12 11:52:21 UTC 2024

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2057734/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : 

[Kernel-packages] [Bug 2058477] Re: [Ubuntu 22.04.4/linux-image-6.5.0-26-generic] Kernel output "UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-34pCLi/linux-hwe-6.5-6.5.0/drivers/net/hyperv/

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Focal)
   Status: Confirmed => Fix Committed

** Changed in: linux (Ubuntu Jammy)
   Status: Confirmed => Fix Committed

** Changed in: linux (Ubuntu Mantic)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2058477

Title:
  [Ubuntu 22.04.4/linux-image-6.5.0-26-generic] Kernel output "UBSAN:
  array-index-out-of-bounds in /build/linux-hwe-6.5-34pCLi/linux-
  hwe-6.5-6.5.0/drivers/net/hyperv/netvsc.c:1445:41" multiple times,
  especially during boot.

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  Overview:

  A newly installed Ubuntu Server 22.04.4 on a Hyper-V virtual machine
  outputs error message "UBSAN: array-index-out-of-bounds in
  /build/linux-hwe-6.5-34pCLi/linux-
  hwe-6.5-6.5.0/drivers/net/hyperv/netvsc.c:1446:41" multiple times,
  especially during boot.

  Reproducing steps:
  1. Download ubuntu-22.04.4-live-server-amd64.iso
  2. Create a Hyper-V virtual machine.
  3. Install Ubuntu 22.04.4 Server on the VM with the downloaded iso normally.
  4. Boot the machine.

  Additional Information:
  - Host machine: Windows 10 Pro 22H2 OS Build 19045.3758
  - Hyper-V configuration version: 9.0
  - The error message "UBSAN: array-index-out-of-bounds" is similar to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008157, but the drivers 
are different.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2060422] Re: Avoid creating non-working backlight sysfs knob from ASUS board

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Jammy)
   Status: Confirmed => Fix Committed

** Changed in: linux (Ubuntu Mantic)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2060422

Title:
  Avoid creating non-working backlight sysfs knob from ASUS board

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  Confirmed

Bug description:
  [Impact]
  Backlight sysfs knobs created by asus-wmi don't really work, hence
  systemd-backlight services are in failed state.

  [Fix]
  Ensure the backlight device are really present

  [Test]
  With the fix applied, the backlight sysfs knobs are not longer present
  under /sys/class/backlight, so there's no more failed systemd-backlight
  service.

  [Where problems could occur]
  Though highly unlikely, but if there's working device that is created
  even when the WMI read is 0x, the device will be missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2060422/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2042546] Re: Include cifs.ko in linux-modules package

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Mantic)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2042546

Title:
  Include cifs.ko in linux-modules package

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  In Progress

Bug description:
  [Impact]

  Commit: "smb: move client and server files to common directory fs/smb" moved 
the fs/cifs directory to fs/sb/client. The inclusion list for linux-modules was 
not updated, it still contains the old path. This means that the cifs.ko module 
cannot be loaded if only linux-modules package is installed, now being part of 
linux-modules-extra.
  For the main kernels this is not a problem because linux-modules-extra is 
always installed, but for derivatives like aws, azure etc, this module cannot 
be loaded without explicitly installing linux-modules-extra.

  [How to reproduce it]:
  1. Install the latest azure kernel 6.5.0-1017.17
  2. Load cifs module
  $ modprobe cifs
  modprobe: FATAL: Module cifs not found in directory 
/lib/modules/6.5.0-1017-azure
  If modules-extra is installed, this works.

  [Fix]

  Replace fs/cifs/* with fs/smb/client/* in
  debian./control.d/.inclusion-list. First the
  main kernels are addressed, derivatives will be fixed via cranky fix.

  [Test Plan]

  1. Apply the fix to one of the derivative (azure), build a new kernel and 
install it
  2. Load cifs module
  $ modprobe cifs
  It should work without installing modules-extra.

  [Regression potential]

  Very low, it's a straightforward fix.

  [Other Info]
  Sending a patch for every derivative takes time and each derivative will be 
fixed once this proposal is acked via cranky fix.

  Original for lunar only
  SRU Justification:

  [Impact]

  Commit: "smb: move client and server files to common directory fs/smb" 
introduced in 2023.09.04 moved the fs/cifs directory to fs/sb/client. The 
inclusion list for linux-modules was not updated, it still contains the old 
path. This means that the cifs.ko module cannot be loaded if only linux-modules 
package is installed, now being part of linux-modules-extra.
  For lunar:main this is not a problem because linux-modules-extra is always 
installed, but for derivatives like aws, azure etc, this module cannot be 
loaded without explicitly installing linux-modules-extra.

  [How to reproduce it]:
  1. Install the latest azure kernel 6.2.0-1016.16
  2. Load cifs module
  $ modprobe cifs
  modprobe: FATAL: Module cifs not found in directory 
/lib/modules/6.2.0-1016-azure
  If modules-extra is installed, this works.

  [Fix]

  Replace fs/cifs/* with fs/smb/client/* in 
debian./control.d/.inclusiojn-list
  This is going to be done in s2023.10.02 cycle for derivatives.

  [Test Plan]

  1. Apply the fix to one of the derivative (azure), build a new kernel and 
install it
  2. Load cifs module
  $ modprobe cifs
  It should work without installing modules-extra.

  [Regression potential]

  Very low, it's a straightforward fix.

  [Other Info]
  Sending a patch for every derivative takes time and each derivative will be 
fixed once this proposal is acked.
  There is also the possibility to do it via cranky fix, but owners may omit it 
during security updates and it's hard to enforce it. Plus, it is a one-time 
change.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2059263] Re: Fix acpi_power_meter accessing IPMI region before it's ready

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Mantic)
   Status: Confirmed => Fix Committed

** Changed in: linux (Ubuntu Noble)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2059263

Title:
  Fix acpi_power_meter accessing IPMI region before it's ready

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Fix Committed
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  ACPI error can be found in kernel message:
  [3.717920] ACPI Error: No handler for Region [SYSI] (ab9e62c5) 
[IPMI] (20230628/evregion-130)

  [Fix]
  On Dell systems that have IPI0001 device, ensure IPMI region is ready
  before acpi_power_meter invokes any ACPI method.

  [Test]
  With the patch applied, no such error can be found in kernel message.
  acpi_power_meter sysfs also works correctly.

  [Where problems could occur]
  If asynchronous probe is disabled, the device drivers that probe after
  acpi_power_meter needs to wait until the completion is done, hence the
  boot time might be slower.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2059263/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2060209] Re: Jammy update: v5.15.151 upstream stable release

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Jammy)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2060209

Title:
  Jammy update: v5.15.151 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 v5.15.151 upstream stable release
 from git://git.kernel.org/

  netfilter: nf_tables: disallow timeout for anonymous sets
  mtd: spinand: gigadevice: Fix the get ecc status issue
  netlink: Fix kernel-infoleak-after-free in __skb_datagram_iter
  net: ip_tunnel: prevent perpetual headroom growth
  tun: Fix xdp_rxq_info's queue_index when detaching
  cpufreq: intel_pstate: fix pstate limits enforcement for adjust_perf call back
  net: veth: clear GRO when clearing XDP even when down
  ipv6: fix potential "struct net" leak in inet6_rtm_getaddr()
  lan78xx: enable auto speed configuration for LAN7850 if no EEPROM is detected
  net: enable memcg accounting for veth queues
  veth: try harder when allocating queue memory
  net: usb: dm9601: fix wrong return value in dm9601_mdio_read
  uapi: in6: replace temporary label with rfc9486
  stmmac: Clear variable when destroying workqueue
  Bluetooth: Avoid potential use-after-free in hci_error_reset
  Bluetooth: hci_event: Fix wrongly recorded wakeup BD_ADDR
  Bluetooth: hci_event: Fix handling of HCI_EV_IO_CAPA_REQUEST
  netfilter: nf_tables: allow NFPROTO_INET in nft_(match/target)_validate()
  netfilter: nfnetlink_queue: silence bogus compiler warning
  netfilter: core: move ip_ct_attach indirection to struct nf_ct_hook
  netfilter: make function op structures const
  netfilter: let reset rules clean out conntrack entries
  netfilter: bridge: confirm multicast packets before passing them up the stack
  rtnetlink: fix error logic of IFLA_BRIDGE_FLAGS writing back
  igb: extend PTP timestamp adjustments to i211
  tls: rx: don't store the record type in socket context
  tls: rx: don't store the decryption status in socket context
  tls: rx: don't issue wake ups when data is decrypted
  tls: rx: refactor decrypt_skb_update()
  tls: hw: rx: use return value of tls_device_decrypted() to carry status
  tls: rx: drop unnecessary arguments from tls_setup_from_iter()
  tls: rx: don't report text length from the bowels of decrypt
  tls: rx: wrap decryption arguments in a structure
  tls: rx: factor out writing ContentType to cmsg
  tls: rx: don't track the async count
  tls: rx: move counting TlsDecryptErrors for sync
  tls: rx: assume crypto always calls our callback
  tls: rx: use async as an in-out argument
  tls: decrement decrypt_pending if no async completion will be called
  efi/capsule-loader: fix incorrect allocation size
  power: supply: bq27xxx-i2c: Do not free non existing IRQ
  ALSA: Drop leftover snd-rtctimer stuff from Makefile
  fbcon: always restore the old font data in fbcon_do_set_font()
  afs: Fix endless loop in directory parsing
  riscv: Sparse-Memory/vmemmap out-of-bounds fix
  tomoyo: fix UAF write bug in tomoyo_write_control()
  ALSA: firewire-lib: fix to check cycle continuity
  gtp: fix use-after-free and null-ptr-deref in gtp_newlink()
  wifi: nl80211: reject iftype change with mesh ID change
  btrfs: dev-replace: properly validate device names
  dmaengine: fsl-qdma: fix SoC may hang on 16 byte unaligned read
  dmaengine: ptdma: use consistent DMA masks
  dmaengine: fsl-qdma: init irq after reg initialization
  mmc: core: Fix eMMC initialization with 1-bit bus connection
  mmc: sdhci-xenon: add timeout for PHY init complete
  mmc: sdhci-xenon: fix PHY init clock stability
  pmdomain: qcom: rpmhpd: Fix enabled_corner aggregation
  x86/cpu/intel: Detect TME keyid bits before setting MTRR mask registers
  mptcp: move __mptcp_error_report in protocol.c
  mptcp: process pending subflow error on close
  mptcp: rename timer related helper to less confusing names
  selftests: mptcp: add missing kconfig for NF Filter
  selftests: mptcp: add missing kconfig for NF Filter in v6
  mptcp: clean up harmless false expressions
  mptcp: add needs_id for netlink appending addr
  mptcp: push at DSS boundaries
  mptcp: fix possible deadlock in subflow diag
  cachefiles: fix memory leak in cachefiles_add_cache()
  fs,hugetlb: fix NULL pointer dereference in hugetlbs_fill_super
  Revert "drm/bridge: lt8912b: Register and attach our DSI device at probe"
  af_unix: Drop oob_skb 

[Kernel-packages] [Bug 2060142] Re: Jammy update: v5.15.150 upstream stable release

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Jammy)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2060142

Title:
  Jammy update: v5.15.150 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 v5.15.150 upstream stable release
 from git://git.kernel.org/

  net/sched: Retire CBQ qdisc
  UBUNTU: [Config] updateconfigs for NET_SCH_CBQ
  net/sched: Retire ATM qdisc
  UBUNTU: [Config] updateconfigs for NET_SCH_ATM
  net/sched: Retire dsmark qdisc
  UBUNTU: [Config] updateconfigs for NET_SCH_DSMARK
  smb: client: fix potential OOBs in smb2_parse_contexts()
  smb: client: fix parsing of SMB3.1.1 POSIX create context
  sched/rt: sysctl_sched_rr_timeslice show default timeslice after reset
  PCI: dwc: Fix a 64bit bug in dw_pcie_ep_raise_msix_irq()
  bpf: Merge printk and seq_printf VARARG max macros
  bpf: Add struct for bin_args arg in bpf_bprintf_prepare
  bpf: Do cleanup in bpf_bprintf_cleanup only when needed
  bpf: Remove trace_printk_lock
  userfaultfd: fix mmap_changing checking in mfill_atomic_hugetlb
  zonefs: Improve error handling
  x86/fpu: Stop relying on userspace for info to fault in xsave buffer
  sched/rt: Fix sysctl_sched_rr_timeslice intial value
  sched/rt: Disallow writing invalid values to sched_rt_period_us
  scsi: target: core: Add TMF to tmr_list handling
  dmaengine: shdma: increase size of 'dev_id'
  dmaengine: fsl-qdma: increase size of 'irq_name'
  wifi: cfg80211: fix missing interfaces when dumping
  wifi: mac80211: fix race condition on enabling fast-xmit
  fbdev: savage: Error out if pixclock equals zero
  fbdev: sis: Error out if pixclock equals zero
  spi: hisi-sfc-v3xx: Return IRQ_NONE if no interrupts were detected
  ahci: asm1166: correct count of reported ports
  ahci: add 43-bit DMA address quirk for ASMedia ASM1061 controllers
  MIPS: reserve exception vector space ONLY ONCE
  platform/x86: touchscreen_dmi: Add info for the TECLAST X16 Plus tablet
  ext4: avoid dividing by 0 in mb_update_avg_fragment_size() when block bitmap 
corrupt
  ext4: avoid allocating blocks from corrupted group in ext4_mb_try_best_found()
  ext4: avoid allocating blocks from corrupted group in ext4_mb_find_by_goal()
  dmaengine: ti: edma: Add some null pointer checks to the edma_probe
  regulator: pwm-regulator: Add validity checks in continuous .get_voltage
  nvmet-tcp: fix nvme tcp ida memory leak
  ALSA: usb-audio: Check presence of valid altsetting control
  ASoC: sunxi: sun4i-spdif: Add support for Allwinner H616
  spi: sh-msiof: avoid integer overflow in constants
  Input: xpad - add Lenovo Legion Go controllers
  netfilter: conntrack: check SCTP_CID_SHUTDOWN_ACK for vtag setting in sctp_new
  ALSA: usb-audio: Ignore clock selector errors for single connection
  nvme-fc: do not wait in vain when unloading module
  nvmet-fcloop: swap the list_add_tail arguments
  nvmet-fc: release reference on target port
  nvmet-fc: defer cleanup using RCU properly
  nvmet-fc: hold reference on hostport match
  nvmet-fc: abort command when there is no binding
  nvmet-fc: avoid deadlock on delete association path
  nvmet-fc: take ref count on tgtport before delete assoc
  ext4: correct the hole length returned by ext4_map_blocks()
  Input: i8042 - add Fujitsu Lifebook U728 to i8042 quirk table
  fs/ntfs3: Modified fix directory element type detection
  fs/ntfs3: Improve ntfs_dir_count
  fs/ntfs3: Correct hard links updating when dealing with DOS names
  fs/ntfs3: Print warning while fixing hard links count
  fs/ntfs3: Fix detected field-spanning write (size 8) of single field 
"le->name"
  fs/ntfs3: Add NULL ptr dereference checking at the end of 
attr_allocate_frame()
  fs/ntfs3: Disable ATTR_LIST_ENTRY size check
  fs/ntfs3: use non-movable memory for ntfs3 MFT buffer cache
  fs/ntfs3: Prevent generic message "attempt to access beyond end of device"
  fs/ntfs3: Correct function is_rst_area_valid
  fs/ntfs3: Update inode->i_size after success write into compressed file
  fs/ntfs3: Fix oob in ntfs_listxattr
  wifi: mac80211: adding missing drv_mgd_complete_tx() call
  efi: runtime: Fix potential overflow of soft-reserved region size
  efi: Don't add memblocks for soft-reserved memory
  hwmon: (coretemp) Enlarge per package core count limit
  scsi: lpfc: Use unsigned type for num_sge
  firewire: core: send 

[Kernel-packages] [Bug 2061814] Re: Mantic update: upstream stable patchset 2024-04-16

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Mantic)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2061814

Title:
  Mantic update: upstream stable patchset 2024-04-16

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 upstream stable patchset 2024-04-16

  Ported from the following upstream stable releases:
  v6.1.79, v6.6.18

 from git://git.kernel.org/

  btrfs: add and use helper to check if block group is used
  btrfs: do not delete unused block group if it may be used soon
  btrfs: forbid creating subvol qgroups
  btrfs: forbid deleting live subvol qgroup
  btrfs: send: return EOPNOTSUPP on unknown flags
  btrfs: don't reserve space for checksums when writing to nocow files
  btrfs: reject encoded write if inode has nodatasum flag set
  btrfs: don't drop extent_map for free space inode on write error
  driver core: Fix device_link_flag_is_sync_state_only()
  of: unittest: Fix compile in the non-dynamic case
  KVM: selftests: Fix a semaphore imbalance in the dirty ring logging test
  wifi: iwlwifi: Fix some error codes
  wifi: iwlwifi: uninitialized variable in iwl_acpi_get_ppag_table()
  of: property: Improve finding the supplier of a remote-endpoint property
  net: openvswitch: limit the number of recursions from action sets
  lan966x: Fix crash when adding interface under a lag
  spi: ppc4xx: Drop write-only variable
  ASoC: rt5645: Fix deadlock in rt5645_jack_detect_work()
  net: sysfs: Fix /sys/class/net/ path for statistics
  nouveau/svm: fix kvcalloc() argument order
  MIPS: Add 'memory' clobber to csum_ipv6_magic() inline assembler
  i40e: Do not allow untrusted VF to remove administratively set MAC
  i40e: Fix waiting for queues of all VSIs to be disabled
  scs: add CONFIG_MMU dependency for vfree_atomic()
  tracing/trigger: Fix to return error if failed to alloc snapshot
  mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again
  scsi: storvsc: Fix ring buffer size calculation
  dm-crypt, dm-verity: disable tasklets
  ASoC: amd: yc: Add DMI quirk for MSI Bravo 15 C7VF
  parisc: Prevent hung tasks when printing inventory on serial console
  ALSA: hda/realtek: Fix the external mic not being recognised for Acer Swift 1 
SF114-32
  ALSA: hda/realtek: Enable Mute LED on HP Laptop 14-fq0xxx
  HID: i2c-hid-of: fix NULL-deref on failed power up
  HID: wacom: generic: Avoid reporting a serial of '0' to userspace
  HID: wacom: Do not register input devices until after hid_hw_start
  iio: hid-sensor-als: Return 0 for HID_USAGE_SENSOR_TIME_TIMESTAMP
  usb: ucsi: Add missing ppm_lock
  usb: ulpi: Fix debugfs directory leak
  usb: ucsi_acpi: Fix command completion handling
  USB: hub: check for alternate port before enabling A_ALT_HNP_SUPPORT
  usb: f_mass_storage: forbid async queue when shutdown happen
  usb: dwc3: gadget: Fix NULL pointer dereference in dwc3_gadget_suspend
  interconnect: qcom: sc8180x: Mark CO0 BCM keepalive
  media: ir_toy: fix a memleak in irtoy_tx
  driver core: fw_devlink: Improve detection of overlapping cycles
  powerpc/kasan: Fix addr error caused by page alignment
  cifs: fix underflow in parse_server_interfaces()
  i2c: qcom-geni: Correct I2C TRE sequence
  irqchip/loongson-eiointc: Use correct struct type in eiointc_domain_alloc()
  powerpc/kasan: Limit KASAN thread size increase to 32KB
  i2c: pasemi: split driver into two separate modules
  i2c: i801: Fix block process call transactions
  modpost: trim leading spaces when processing source files list
  mptcp: get rid of msk->subflow
  mptcp: fix data re-injection from stale subflow
  selftests: mptcp: add missing kconfig for NF Filter
  selftests: mptcp: add missing kconfig for NF Filter in v6
  selftests: mptcp: add missing kconfig for NF Mangle
  selftests: mptcp: increase timeout to 30 min
  mptcp: drop the push_pending field
  mptcp: check addrs list in userspace_pm_get_local_id
  scsi: Revert "scsi: fcoe: Fix potential deadlock on >ctlr_lock"
  Revert "drm/amd: flush any delayed gfxoff on suspend entry"
  drm/virtio: Set segment size for virtio_gpu device
  lsm: fix the logic in security_inode_getsecctx()
  firewire: core: correct documentation of fw_csr_string() kernel API
  ALSA: hda/realtek: Apply headset jack quirk for non-bass alc287 thinkpads
  kbuild: Fix changing ELF file 

[Kernel-packages] [Bug 2059991] Re: Mantic update: upstream stable patchset 2024-04-02

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Mantic)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2059991

Title:
  Mantic update: upstream stable patchset 2024-04-02

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 upstream stable patchset 2024-04-02

  Ported from the following upstream stable releases:
  v6.1.78, v6.6.17

 from git://git.kernel.org/

  ext4: regenerate buddy after block freeing failed if under fc replay
  dmaengine: fsl-dpaa2-qdma: Fix the size of dma pools
  dmaengine: ti: k3-udma: Report short packet errors
  dmaengine: fsl-qdma: Fix a memory leak related to the status queue DMA
  dmaengine: fsl-qdma: Fix a memory leak related to the queue command DMA
  phy: renesas: rcar-gen3-usb2: Fix returning wrong error code
  dmaengine: fix is_slave_direction() return false when DMA_DEV_TO_DEV
  phy: ti: phy-omap-usb2: Fix NULL pointer dereference for SRP
  cifs: failure to add channel on iface should bump up weight
  drm/msms/dp: fixed link clock divider bits be over written in BPC unknown case
  drm/msm/dp: return correct Colorimetry for DP_TEST_DYNAMIC_RANGE_CEA case
  drm/msm/dpu: check for valid hw_pp in dpu_encoder_helper_phys_cleanup
  net: stmmac: xgmac: fix handling of DPP safety error for DMA channels
  wifi: mac80211: fix waiting for beacons logic
  netdevsim: avoid potential loop in nsim_dev_trap_report_work()
  net: atlantic: Fix DMA mapping for PTP hwts ring
  selftests: net: cut more slack for gro fwd tests.
  selftests: net: avoid just another constant wait
  tunnels: fix out of bounds access when building IPv6 PMTU error
  atm: idt77252: fix a memleak in open_card_ubr0
  octeontx2-pf: Fix a memleak otx2_sq_init
  hwmon: (aspeed-pwm-tacho) mutex for tach reading
  hwmon: (coretemp) Fix out-of-bounds memory access
  hwmon: (coretemp) Fix bogus core_id to attr name mapping
  inet: read sk->sk_family once in inet_recv_error()
  drm/i915/gvt: Fix uninitialized variable in handle_mmio()
  rxrpc: Fix response to PING RESPONSE ACKs to a dead call
  tipc: Check the bearer type before calling tipc_udp_nl_bearer_add()
  af_unix: Call kfree_skb() for dead unix_(sk)->oob_skb in GC.
  ppp_async: limit MRU to 64K
  selftests: cmsg_ipv6: repeat the exact packet
  netfilter: nft_compat: narrow down revision to unsigned 8-bits
  netfilter: nft_compat: reject unused compat flag
  netfilter: nft_compat: restrict match/target protocol to u16
  drm/amd/display: Implement bounds check for stream encoder creation in DCN301
  netfilter: nft_ct: reject direction for ct id
  netfilter: nft_set_pipapo: store index in scratch maps
  netfilter: nft_set_pipapo: add helper to release pcpu scratch area
  netfilter: nft_set_pipapo: remove scratch_aligned pointer
  fs/ntfs3: Fix an NULL dereference bug
  scsi: core: Move scsi_host_busy() out of host lock if it is for per-command
  blk-iocost: Fix an UBSAN shift-out-of-bounds warning
  ALSA: usb-audio: Add delay quirk for MOTU M Series 2nd revision
  ALSA: usb-audio: Add a quirk for Yamaha YIT-W12TX transmitter
  ALSA: usb-audio: add quirk for RODE NT-USB+
  USB: serial: qcserial: add new usb-id for Dell Wireless DW5826e
  USB: serial: option: add Fibocom FM101-GL variant
  USB: serial: cp210x: add ID for IMST iM871A-USB
  usb: dwc3: host: Set XHCI_SG_TRB_CACHE_SIZE_QUIRK
  usb: host: xhci-plat: Add support for XHCI_SG_TRB_CACHE_SIZE_QUIRK
  hrtimer: Report offline hrtimer enqueue
  Input: i8042 - fix strange behavior of touchpad on Clevo NS70PU
  Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping ATKBD_CMD_GETID
  io_uring/net: fix sr->len for IORING_OP_RECV with MSG_WAITALL and buffers
  net: stmmac: xgmac: use #define for string constants
  ALSA: usb-audio: Sort quirk table entries
  net: stmmac: xgmac: fix a typo of register name in DPP safety handling
  perf evlist: Fix evlist__new_default() for > 1 core PMU
  cifs: avoid redundant calls to disable multichannel
  rust: arc: add explicit `drop()` around `Box::from_raw()`
  rust: task: remove redundant explicit link
  rust: print: use explicit link in documentation
  MAINTAINERS: add Catherine as xfs maintainer for 6.6.y
  xfs: bump max fsgeom struct version
  xfs: hoist freeing of rt data fork extent mappings
  xfs: prevent rt growfs when quota is enabled
  xfs: rt stubs should 

[Kernel-packages] [Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

[Roxana Nicolescu]

Hi! Thanks for reporting this.
We will do our best to release new kernels in 1-2 days. In the meantime, the 
meta package will be deleted so that other people do not upgrade to 5.15.0-102.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2060780

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  Hi,

  updated some Ubuntu 22.04 systems to lastest available state this
  morning, which caused CIFS mounts (from various fileservers) to stop
  working. Kernel was updated to version 5.15.0-102-generic.

  I can mount the shares without problems (mount -t cifs), but then, df for 
example tells me: df: /mnt: Resource temporarily unavailable.
  I'm able to list and browse all the files, but accessing them (even readonly) 
is very unstable. Sometimes it works and sometimes it just gives me i/o errors. 

  Switching back to  5.15.0-101-generic or 5.15.0-100-generic solves the
  problem and everything works again as expected.

  Seems like some bug has been implemented in 5.15.0-102-generic...

  To reproduce the problem, I started a while loop on one server to
  write to some file on a specific mounted CIFS share and read it from
  another one

  root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; 
sleep 1 ; done
  -bash: /mnt/hallo.txt: Input/output error
  -bash: /mnt/hallo.txt: Input/output error
  ^C

  root@:~$ tail -f /mnt/hallo.txt
  Tue Apr  9 04:10:52 PM CEST 2024 hallo
  Tue Apr  9 04:10:53 PM CEST 2024 hallo
  Tue Apr  9 04:10:54 PM CEST 2024 hallo
  Tue Apr  9 04:10:55 PM CEST 2024 hallo
  Tue Apr  9 04:10:56 PM CEST 2024 hallo
  Tue Apr  9 04:10:57 PM CEST 2024 hallo
  Tue Apr  9 04:10:58 PM CEST 2024 hallo
  Tue Apr  9 04:10:59 PM CEST 2024 hallo
  Tue Apr  9 04:11:00 PM CEST 2024 hallo
  Tue Apr  9 04:11:01 PM CEST 2024 hallo
  tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: 
Resource temporarily unavailable
  Tue Apr  9 04:11:04 PM CEST 2024 hallo
  Tue Apr  9 04:11:05 PM CEST 2024 hallo
  Tue Apr  9 04:11:06 PM CEST 2024 hallo
  Tue Apr  9 04:11:07 PM CEST 2024 hallo
  Tue Apr  9 04:11:08 PM CEST 2024 hallo
  Tue Apr  9 04:11:09 PM CEST 2024 hallo
  Tue Apr  9 04:11:10 PM CEST 2024 hallo

  While doing this, both servers tell me, the resource is unavailable

  root@:~# df -h /mnt
  df: /mnt: Resource temporarily unavailable

  root@:~$ df -h /mnt
  df: /mnt: Resource temporarily unavailable

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2056373] Re: Problems with HVCS and hotplugging

[Roxana Nicolescu]

** Tags removed: verification-needed-focal-linux-iot 
verification-needed-focal-linux-kvm verification-needed-focal-linux-oracle 
verification-needed-focal-linux-raspi verification-needed-jammy-linux
** Tags added: verification-done-focal-linux-iot 
verification-done-focal-linux-kvm verification-done-focal-linux-oracle 
verification-done-focal-linux-raspi verification-done-jammy-linux

** Tags removed: verification-needed-focal-linux-bluefield 
verification-needed-focal-linux-fips verification-needed-focal-linux-gcp 
verification-needed-focal-linux-gkeop verification-needed-focal-linux-ibm
** Tags added: verification-done-focal-linux-bluefield 
verification-done-focal-linux-fips verification-done-focal-linux-gcp 
verification-done-focal-linux-gkeop verification-done-focal-linux-ibm

** Tags removed: verification-needed-bionic-linux-hwe-5.4 
verification-needed-focal-linux-aws verification-needed-focal-linux-azure
** Tags added: verification-done-bionic-linux-hwe-5.4 
verification-done-focal-linux-aws verification-done-focal-linux-azure

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2056373

Title:
  Problems with HVCS and hotplugging

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Invalid

Bug description:
  SRU Justification:
  ==

  [Impact]

   * HVCS (Hypervisor Virtual Console Server) is broken because the
 virtual terminal mkvterm fails, caused by pvmutil failing.

   * When mkvterm is ran, it ultimately fails because it calls pvmutil
 which fails.
 pvmutil calls drmgr, and drmgr is adding a slot correctly.
 However, when drmgr writes the slot information to ?/add_slot,
 the return is -ENODEV.

   * This leads to HVCS never having probe() called.

   * In addition, HVCS is missing patches/fixes, and is broken without
  them.

  [Fix]

   * Fix one and two is required for focal only, all other for focal and
  jammy:

   * 57409d4fb12c 57409d4fb12c185b2c0689e0496878c8f6bb5b58
 "powerpc/pseries: Fix bad drc_index_start value parsing of drc-info entry"

   * c5e76fa05b2d c5e76fa05b2df519b9f08571cc57e623c1569faa
 "powerpc/pseries: Fix of_read_drc_info_cell() to point at next record"

   * 6a9a733edd46 6a9a733edd46732e906d976dc21a42dd361e53cc
 "hvcs: Fix hvcs port reference counting"

   * 760aa5e81f33 760aa5e81f33e0da82512c4288489739a6d1c556
 "hvcs: Use dev_groups to manage hvcs device attributes"

   * 503a90dd619d 503a90dd619d52dcac2cc68bd742aa914c7cd47a
 "hvcs: Use driver groups to manage driver attributes"

   * 3a8d3b366ce4 3a8d3b366ce47024bf274eac783f8af5df2780f5
 "hvcs: Get reference to tty in remove"

   * d432228bc7b1 d432228bc7b1b3f0ed06510278ff5a77b3749fe6
 "hvcs: Use vhangup in hotplug remove"

   * 28d49f8cbe9c 28d49f8cbe9c7966f91ee1b5ec2f997f6e55bf9f
 "hvcs: Synchronize hotplug remove with port free"

  [Test Plan]

   * The high level test plan is to run mkvterm with an id.
   
   * mkvterm will fail because /dev/hvcs* device nodes are missing.

   * Details see https://bugs.launchpad.net/bugs/2023243 for more information.
 Especially the script provided by IBM
 (see original bug description: `---Steps to Reproduce---`).

   * IBM will (stress) test the updated kernel(s) provided in -proposed.

  [Where problems could occur]

   * The first two commits affect arch/powerpc/platforms/pseries/of_helpers.c
 and are needed to fix the hotplugging issue seen when drmgr goes to write
 the slot information to /sys/bus/pci/slots/control/add_slot.
 In case of issues here hotplugging with drmgr might break.

   * The issue lies in rpadlpar_io and rpaphp calling an of helper function
 of_read_drc_info_cell(). Without these commits, the value stored
 drc_index_start is incorrect.
 This ultimately results in the entire SLOT string being incorrect,
 and rpaphp never finding the newly added slot by drmgr.
 rpadlpar then returns -ENODEV.
 Therefore, HVCS is never probed, and the device nodes are never created.

   * HVCS, rpadlpar_io, and rpaphp should ideally not even need to be loaded
 prior to drmgr adding a vio slot.
 If rpadlpar_io and rpaphp are not loaded, drmgr will load them.
 In addition, if rpadlpar_io and rpaphp register the new slot correctly,
 rpadlpar_io will call dlpar_add_vio_slot(),
 which calls vio_register_device_node() with the device node.
 This is what tells the driver core to init and probe HVCS
 (which is needed to create the device nodes).

   * The remaning 6 commits are needed for HVCS, that is essentially
 broken without them.
 Overall, issues they fix are race 

[Kernel-packages] [Bug 2056418] Re: Fix headphone mic detection issue on ALC897

[Roxana Nicolescu]

** Tags removed: verification-needed-jammy-linux 
verification-needed-mantic-linux
** Tags added: verification-done-jammy-linux verification-done-mantic-linux

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2056418

Title:
  Fix headphone mic detection issue on ALC897

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  Headphone mic is lost after resume from S3 or reboot with plugin.

  [Fix]
  Restore the headphone mic detect logic for ALC897 after lost power.

  [Test]
  Tested on hardware, the headphone mic appears as plugin after boot or
  resume from S3, and works fine.

  [Where problems could occur]
  It may break ALC897 sound input.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2056418/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2055083] Re: Drop fips-checks script from trees

[Roxana Nicolescu]

** Tags removed: verification-needed-focal-linux 
verification-needed-jammy-linux verification-needed-mantic-linux
** Tags added: verification-done-focal-linux verification-done-jammy-linux 
verification-done-mantic-linux

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2055083

Title:
  Drop fips-checks script from trees

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  Fix Committed

Bug description:
  [Impact]

  When producing a new version of some kernels, we need to check for
  changes that might affect FIPS certs and justify why a commit was
  kept. For that, we have a fips-checks script that lives under debian/
  in Focal, Jammy, Mantic and Noble.

  This script has been moved to `cranky`[1], so now there is no need to
  have this script in the kernel Git trees as well.

  [1] https://git.launchpad.net/~canonical-kernel/+git/kteam-
  tools/commit/?id=2ab9364d4b4c18bee7d835787d7dd11990103bca

  [Fix]

  Remove the fips-checks script and its calls.

  [Test Plan]

  Prepare a kernel and ensure that the `cranky close` step runs without
  any errors.

  [Where problems could occur]

  This only affects the preparation of FIPS kernels and not the kernel final 
binary. Moreover, I've prepared some FIPS kernels from the 2024.03.04 cycle 
relying on `cranky check-fips` to ensure that
  we have it working well on the cranky side too.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2059143] Re: Remove getabis scripts

[Roxana Nicolescu]

** Tags removed: verification-needed-bionic-linux 
verification-needed-focal-linux verification-needed-jammy-linux 
verification-needed-xenial-linux
** Tags added: verification-done-bionic-linux verification-done-focal-linux 
verification-done-jammy-linux verification-done-xenial-linux

** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic-linux

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2059143

Title:
  Remove getabis scripts

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]
  With ABI checks removed from the tree (#LP2055685), there's no need to
  download the buildinfo from a previous version.

  [Fix]
  This is needed only in the main kernels.
  1. remove the common getabis script
  2. remove per kernel getabis file (this will be done with cranky fix)

  [Test]
  Build test on cbd. No issue found. Also cranked the kernels in advance to see 
if there were issues, but no issue was found.

  [Regression potential]
  In the current cycle, the ABI checks have been removed and this is not used 
anymore. No issues have been found. Now we're just removing an unused feature, 
therefore the regression potential is none.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2060142] Re: Jammy update: v5.15.150 upstream stable release

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Jammy)
   Status: Fix Committed => In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2060142

Title:
  Jammy update: v5.15.150 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 v5.15.150 upstream stable release
 from git://git.kernel.org/

  net/sched: Retire CBQ qdisc
  UBUNTU: [Config] updateconfigs for NET_SCH_CBQ
  net/sched: Retire ATM qdisc
  UBUNTU: [Config] updateconfigs for NET_SCH_ATM
  net/sched: Retire dsmark qdisc
  UBUNTU: [Config] updateconfigs for NET_SCH_DSMARK
  smb: client: fix potential OOBs in smb2_parse_contexts()
  smb: client: fix parsing of SMB3.1.1 POSIX create context
  sched/rt: sysctl_sched_rr_timeslice show default timeslice after reset
  PCI: dwc: Fix a 64bit bug in dw_pcie_ep_raise_msix_irq()
  bpf: Merge printk and seq_printf VARARG max macros
  bpf: Add struct for bin_args arg in bpf_bprintf_prepare
  bpf: Do cleanup in bpf_bprintf_cleanup only when needed
  bpf: Remove trace_printk_lock
  userfaultfd: fix mmap_changing checking in mfill_atomic_hugetlb
  zonefs: Improve error handling
  x86/fpu: Stop relying on userspace for info to fault in xsave buffer
  sched/rt: Fix sysctl_sched_rr_timeslice intial value
  sched/rt: Disallow writing invalid values to sched_rt_period_us
  scsi: target: core: Add TMF to tmr_list handling
  dmaengine: shdma: increase size of 'dev_id'
  dmaengine: fsl-qdma: increase size of 'irq_name'
  wifi: cfg80211: fix missing interfaces when dumping
  wifi: mac80211: fix race condition on enabling fast-xmit
  fbdev: savage: Error out if pixclock equals zero
  fbdev: sis: Error out if pixclock equals zero
  spi: hisi-sfc-v3xx: Return IRQ_NONE if no interrupts were detected
  ahci: asm1166: correct count of reported ports
  ahci: add 43-bit DMA address quirk for ASMedia ASM1061 controllers
  MIPS: reserve exception vector space ONLY ONCE
  platform/x86: touchscreen_dmi: Add info for the TECLAST X16 Plus tablet
  ext4: avoid dividing by 0 in mb_update_avg_fragment_size() when block bitmap 
corrupt
  ext4: avoid allocating blocks from corrupted group in ext4_mb_try_best_found()
  ext4: avoid allocating blocks from corrupted group in ext4_mb_find_by_goal()
  dmaengine: ti: edma: Add some null pointer checks to the edma_probe
  regulator: pwm-regulator: Add validity checks in continuous .get_voltage
  nvmet-tcp: fix nvme tcp ida memory leak
  ALSA: usb-audio: Check presence of valid altsetting control
  ASoC: sunxi: sun4i-spdif: Add support for Allwinner H616
  spi: sh-msiof: avoid integer overflow in constants
  Input: xpad - add Lenovo Legion Go controllers
  netfilter: conntrack: check SCTP_CID_SHUTDOWN_ACK for vtag setting in sctp_new
  ALSA: usb-audio: Ignore clock selector errors for single connection
  nvme-fc: do not wait in vain when unloading module
  nvmet-fcloop: swap the list_add_tail arguments
  nvmet-fc: release reference on target port
  nvmet-fc: defer cleanup using RCU properly
  nvmet-fc: hold reference on hostport match
  nvmet-fc: abort command when there is no binding
  nvmet-fc: avoid deadlock on delete association path
  nvmet-fc: take ref count on tgtport before delete assoc
  ext4: correct the hole length returned by ext4_map_blocks()
  Input: i8042 - add Fujitsu Lifebook U728 to i8042 quirk table
  fs/ntfs3: Modified fix directory element type detection
  fs/ntfs3: Improve ntfs_dir_count
  fs/ntfs3: Correct hard links updating when dealing with DOS names
  fs/ntfs3: Print warning while fixing hard links count
  fs/ntfs3: Fix detected field-spanning write (size 8) of single field 
"le->name"
  fs/ntfs3: Add NULL ptr dereference checking at the end of 
attr_allocate_frame()
  fs/ntfs3: Disable ATTR_LIST_ENTRY size check
  fs/ntfs3: use non-movable memory for ntfs3 MFT buffer cache
  fs/ntfs3: Prevent generic message "attempt to access beyond end of device"
  fs/ntfs3: Correct function is_rst_area_valid
  fs/ntfs3: Update inode->i_size after success write into compressed file
  fs/ntfs3: Fix oob in ntfs_listxattr
  wifi: mac80211: adding missing drv_mgd_complete_tx() call
  efi: runtime: Fix potential overflow of soft-reserved region size
  efi: Don't add memblocks for soft-reserved memory
  hwmon: (coretemp) Enlarge per package core count limit
  scsi: lpfc: Use unsigned type for num_sge
  firewire: core: send bus 

[Kernel-packages] [Bug 2060216] Re: Focal update: v5.4.271 upstream stable release

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2060216

Title:
  Focal update: v5.4.271 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 v5.4.271 upstream stable release
 from git://git.kernel.org/

  netlink: Fix kernel-infoleak-after-free in __skb_datagram_iter
  net: ip_tunnel: prevent perpetual headroom growth
  tun: Fix xdp_rxq_info's queue_index when detaching
  ipv6: fix potential "struct net" leak in inet6_rtm_getaddr()
  lan78xx: enable auto speed configuration for LAN7850 if no EEPROM is detected
  net: usb: dm9601: fix wrong return value in dm9601_mdio_read
  Bluetooth: Avoid potential use-after-free in hci_error_reset
  Bluetooth: hci_event: Fix handling of HCI_EV_IO_CAPA_REQUEST
  Bluetooth: Enforce validation on max value of connection interval
  netfilter: nf_tables: allow NFPROTO_INET in nft_(match/target)_validate()
  rtnetlink: fix error logic of IFLA_BRIDGE_FLAGS writing back
  efi/capsule-loader: fix incorrect allocation size
  power: supply: bq27xxx-i2c: Do not free non existing IRQ
  ALSA: Drop leftover snd-rtctimer stuff from Makefile
  afs: Fix endless loop in directory parsing
  gtp: fix use-after-free and null-ptr-deref in gtp_newlink()
  wifi: nl80211: reject iftype change with mesh ID change
  btrfs: dev-replace: properly validate device names
  dmaengine: fsl-qdma: fix SoC may hang on 16 byte unaligned read
  dmaengine: fsl-qdma: init irq after reg initialization
  mmc: core: Fix eMMC initialization with 1-bit bus connection
  x86/cpu/intel: Detect TME keyid bits before setting MTRR mask registers
  cachefiles: fix memory leak in cachefiles_add_cache()
  fs,hugetlb: fix NULL pointer dereference in hugetlbs_fill_super
  gpio: 74x164: Enable output pins after registers are reset
  Linux 5.4.271
  UBUNTU: Upstream stable to v5.4.271

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2060019] Re: Focal update: v5.4.270 upstream stable release

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2060019

Title:
  Focal update: v5.4.270 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 v5.4.270 upstream stable release
 from git://git.kernel.org/

  KVM: arm64: vgic-its: Test for valid IRQ in its_sync_lpi_pending_table()
  KVM: arm64: vgic-its: Test for valid IRQ in MOVALL handler
  net/sched: Retire CBQ qdisc
  UBUNTU: [Config] updateconfigs for NET_SCH_CBQ
  net/sched: Retire ATM qdisc
  UBUNTU: [Config] updateconfigs for NET_SCH_ATM
  net/sched: Retire dsmark qdisc
  UBUNTU: [Config] updateconfigs for NET_SCH_DSMARK
  sched/rt: sysctl_sched_rr_timeslice show default timeslice after reset
  memcg: add refcnt for pcpu stock to avoid UAF problem in drain_all_stock()
  nilfs2: replace WARN_ONs for invalid DAT metadata block requests
  userfaultfd: fix mmap_changing checking in mfill_atomic_hugetlb
  sched/rt: Fix sysctl_sched_rr_timeslice intial value
  sched/rt: Disallow writing invalid values to sched_rt_period_us
  scsi: target: core: Add TMF to tmr_list handling
  dmaengine: shdma: increase size of 'dev_id'
  dmaengine: fsl-qdma: increase size of 'irq_name'
  wifi: cfg80211: fix missing interfaces when dumping
  wifi: mac80211: fix race condition on enabling fast-xmit
  fbdev: savage: Error out if pixclock equals zero
  fbdev: sis: Error out if pixclock equals zero
  ahci: asm1166: correct count of reported ports
  ahci: add 43-bit DMA address quirk for ASMedia ASM1061 controllers
  ext4: avoid allocating blocks from corrupted group in ext4_mb_try_best_found()
  ext4: avoid allocating blocks from corrupted group in ext4_mb_find_by_goal()
  regulator: pwm-regulator: Add validity checks in continuous .get_voltage
  nvmet-tcp: fix nvme tcp ida memory leak
  ASoC: sunxi: sun4i-spdif: Add support for Allwinner H616
  netfilter: conntrack: check SCTP_CID_SHUTDOWN_ACK for vtag setting in sctp_new
  nvmet-fc: abort command when there is no binding
  hwmon: (coretemp) Enlarge per package core count limit
  scsi: lpfc: Use unsigned type for num_sge
  firewire: core: send bus reset promptly on gap count error
  virtio-blk: Ensure no requests in virtqueues before deleting vqs.
  s390/qeth: Fix potential loss of L3-IP@ in case of network issues
  pmdomain: renesas: r8a77980-sysc: CR7 must be always on
  tcp: factor out __tcp_close() helper
  tcp: return EPOLLOUT from tcp_poll only when notsent_bytes is half the limit
  tcp: add annotations around sk->sk_shutdown accesses
  pinctrl: pinctrl-rockchip: Fix a bunch of kerneldoc misdemeanours
  pinctrl: rockchip: Fix refcount leak in rockchip_pinctrl_parse_groups
  spi: mt7621: Fix an error message in mt7621_spi_probe()
  net: bridge: clear bridge's private skb space on xmit
  selftests/bpf: Avoid running unprivileged tests with alignment requirements
  Revert "drm/sun4i: dsi: Change the start delay calculation"
  drm/amdgpu: Check for valid number of registers to read
  x86/alternatives: Disable KASAN in apply_alternatives()
  dm-integrity: don't modify bio's immutable bio_vec in integrity_metadata()
  iomap: Set all uptodate bits for an Uptodate page
  drm/amdgpu: Fix type of second parameter in trans_msg() callback
  arm64: dts: qcom: msm8916: Fix typo in pronto remoteproc node
  PCI: tegra: Fix reporting GPIO error value
  PCI: tegra: Fix OF node reference leak
  IB/hfi1: Fix sdma.h tx->num_descs off-by-one error
  dm-crypt: don't modify the data when using authenticated encryption
  gtp: fix use-after-free and null-ptr-deref in gtp_genl_dump_pdp()
  PCI/MSI: Prevent MSI hardware interrupt number truncation
  l2tp: pass correct message length to ip6_append_data
  ARM: ep93xx: Add terminator to gpiod_lookup_table
  usb: cdns3: fixed memory use after free at cdns3_gadget_ep_disable()
  usb: cdns3: fix memory double free when handle zero packet
  usb: gadget: ncm: Avoid dropping datagrams of properly parsed NTBs
  usb: roles: don't get/set_role() when usb_role_switch is unregistered
  IB/hfi1: Fix a memleak in init_credit_return
  RDMA/bnxt_re: Return error for SRQ resize
  RDMA/srpt: Make debug output more detailed
  RDMA/srpt: fix function pointer cast warnings
  scripts/bpf: teach bpf_helpers_doc.py to dump BPF helper definitions
  bpf, scripts: Correct 

[Kernel-packages] [Bug 2060142] Re: Jammy update: v5.15.150 upstream stable release

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Jammy)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2060142

Title:
  Jammy update: v5.15.150 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 v5.15.150 upstream stable release
 from git://git.kernel.org/

  net/sched: Retire CBQ qdisc
  UBUNTU: [Config] updateconfigs for NET_SCH_CBQ
  net/sched: Retire ATM qdisc
  UBUNTU: [Config] updateconfigs for NET_SCH_ATM
  net/sched: Retire dsmark qdisc
  UBUNTU: [Config] updateconfigs for NET_SCH_DSMARK
  smb: client: fix potential OOBs in smb2_parse_contexts()
  smb: client: fix parsing of SMB3.1.1 POSIX create context
  sched/rt: sysctl_sched_rr_timeslice show default timeslice after reset
  PCI: dwc: Fix a 64bit bug in dw_pcie_ep_raise_msix_irq()
  bpf: Merge printk and seq_printf VARARG max macros
  bpf: Add struct for bin_args arg in bpf_bprintf_prepare
  bpf: Do cleanup in bpf_bprintf_cleanup only when needed
  bpf: Remove trace_printk_lock
  userfaultfd: fix mmap_changing checking in mfill_atomic_hugetlb
  zonefs: Improve error handling
  x86/fpu: Stop relying on userspace for info to fault in xsave buffer
  sched/rt: Fix sysctl_sched_rr_timeslice intial value
  sched/rt: Disallow writing invalid values to sched_rt_period_us
  scsi: target: core: Add TMF to tmr_list handling
  dmaengine: shdma: increase size of 'dev_id'
  dmaengine: fsl-qdma: increase size of 'irq_name'
  wifi: cfg80211: fix missing interfaces when dumping
  wifi: mac80211: fix race condition on enabling fast-xmit
  fbdev: savage: Error out if pixclock equals zero
  fbdev: sis: Error out if pixclock equals zero
  spi: hisi-sfc-v3xx: Return IRQ_NONE if no interrupts were detected
  ahci: asm1166: correct count of reported ports
  ahci: add 43-bit DMA address quirk for ASMedia ASM1061 controllers
  MIPS: reserve exception vector space ONLY ONCE
  platform/x86: touchscreen_dmi: Add info for the TECLAST X16 Plus tablet
  ext4: avoid dividing by 0 in mb_update_avg_fragment_size() when block bitmap 
corrupt
  ext4: avoid allocating blocks from corrupted group in ext4_mb_try_best_found()
  ext4: avoid allocating blocks from corrupted group in ext4_mb_find_by_goal()
  dmaengine: ti: edma: Add some null pointer checks to the edma_probe
  regulator: pwm-regulator: Add validity checks in continuous .get_voltage
  nvmet-tcp: fix nvme tcp ida memory leak
  ALSA: usb-audio: Check presence of valid altsetting control
  ASoC: sunxi: sun4i-spdif: Add support for Allwinner H616
  spi: sh-msiof: avoid integer overflow in constants
  Input: xpad - add Lenovo Legion Go controllers
  netfilter: conntrack: check SCTP_CID_SHUTDOWN_ACK for vtag setting in sctp_new
  ALSA: usb-audio: Ignore clock selector errors for single connection
  nvme-fc: do not wait in vain when unloading module
  nvmet-fcloop: swap the list_add_tail arguments
  nvmet-fc: release reference on target port
  nvmet-fc: defer cleanup using RCU properly
  nvmet-fc: hold reference on hostport match
  nvmet-fc: abort command when there is no binding
  nvmet-fc: avoid deadlock on delete association path
  nvmet-fc: take ref count on tgtport before delete assoc
  ext4: correct the hole length returned by ext4_map_blocks()
  Input: i8042 - add Fujitsu Lifebook U728 to i8042 quirk table
  fs/ntfs3: Modified fix directory element type detection
  fs/ntfs3: Improve ntfs_dir_count
  fs/ntfs3: Correct hard links updating when dealing with DOS names
  fs/ntfs3: Print warning while fixing hard links count
  fs/ntfs3: Fix detected field-spanning write (size 8) of single field 
"le->name"
  fs/ntfs3: Add NULL ptr dereference checking at the end of 
attr_allocate_frame()
  fs/ntfs3: Disable ATTR_LIST_ENTRY size check
  fs/ntfs3: use non-movable memory for ntfs3 MFT buffer cache
  fs/ntfs3: Prevent generic message "attempt to access beyond end of device"
  fs/ntfs3: Correct function is_rst_area_valid
  fs/ntfs3: Update inode->i_size after success write into compressed file
  fs/ntfs3: Fix oob in ntfs_listxattr
  wifi: mac80211: adding missing drv_mgd_complete_tx() call
  efi: runtime: Fix potential overflow of soft-reserved region size
  efi: Don't add memblocks for soft-reserved memory
  hwmon: (coretemp) Enlarge per package core count limit
  scsi: lpfc: Use unsigned type for num_sge
  firewire: core: send 

[Kernel-packages] [Bug 2042546] Re: Include cifs.ko in linux-modules package

[Roxana Nicolescu]

** Description changed:

+ [Impact]
+ 
+ Commit: "smb: move client and server files to common directory fs/smb" moved 
the fs/cifs directory to fs/sb/client. The inclusion list for linux-modules was 
not updated, it still contains the old path. This means that the cifs.ko module 
cannot be loaded if only linux-modules package is installed, now being part of 
linux-modules-extra.
+ For the main kernels this is not a problem because linux-modules-extra is 
always installed, but for derivatives like aws, azure etc, this module cannot 
be loaded without explicitly installing linux-modules-extra.
+ 
+ [How to reproduce it]:
+ 1. Install the latest azure kernel 6.5.0-1016.16
+ 2. Load cifs module
+ $ modprobe cifs
+ modprobe: FATAL: Module cifs not found in directory 
/lib/modules/6.5.0-1016-azure
+ If modules-extra is installed, this works.
+ 
+ [Fix]
+ 
+ Replace fs/cifs/* with fs/smb/client/* in
+ debian./control.d/.inclusion-list
+ 
+ [Test Plan]
+ 
+ 1. Apply the fix to one of the derivative (azure), build a new kernel and 
install it
+ 2. Load cifs module
+ $ modprobe cifs
+ It should work without installing modules-extra.
+ 
+ [Regression potential]
+ 
+ Very low, it's a straightforward fix.
+ 
+ [Other Info]
+ Sending a patch for every derivative takes time and each derivative will be 
fixed once this proposal is acked via cranky fix.
+ 
+ Original for lunar only
  SRU Justification:
  
  [Impact]
  
  Commit: "smb: move client and server files to common directory fs/smb" 
introduced in 2023.09.04 moved the fs/cifs directory to fs/sb/client. The 
inclusion list for linux-modules was not updated, it still contains the old 
path. This means that the cifs.ko module cannot be loaded if only linux-modules 
package is installed, now being part of linux-modules-extra.
  For lunar:main this is not a problem because linux-modules-extra is always 
installed, but for derivatives like aws, azure etc, this module cannot be 
loaded without explicitly installing linux-modules-extra.
  
  [How to reproduce it]:
  1. Install the latest azure kernel 6.2.0-1016.16
  2. Load cifs module
  $ modprobe cifs
  modprobe: FATAL: Module cifs not found in directory 
/lib/modules/6.2.0-1016-azure
  If modules-extra is installed, this works.
  
  [Fix]
  
  Replace fs/cifs/* with fs/smb/client/* in 
debian./control.d/.inclusiojn-list
  This is going to be done in s2023.10.02 cycle for derivatives.
  
  [Test Plan]
  
  1. Apply the fix to one of the derivative (azure), build a new kernel and 
install it
  2. Load cifs module
  $ modprobe cifs
  It should work without installing modules-extra.
  
  [Regression potential]
  
  Very low, it's a straightforward fix.
  
  [Other Info]
  Sending a patch for every derivative takes time and each derivative will be 
fixed once this proposal is acked.
  There is also the possibility to do it via cranky fix, but owners may omit it 
during security updates and it's hard to enforce it. Plus, it is a one-time 
change.

** Description changed:

  [Impact]
  
  Commit: "smb: move client and server files to common directory fs/smb" moved 
the fs/cifs directory to fs/sb/client. The inclusion list for linux-modules was 
not updated, it still contains the old path. This means that the cifs.ko module 
cannot be loaded if only linux-modules package is installed, now being part of 
linux-modules-extra.
  For the main kernels this is not a problem because linux-modules-extra is 
always installed, but for derivatives like aws, azure etc, this module cannot 
be loaded without explicitly installing linux-modules-extra.
  
  [How to reproduce it]:
- 1. Install the latest azure kernel 6.5.0-1016.16
+ 1. Install the latest azure kernel 6.5.0-1017.17
  2. Load cifs module
  $ modprobe cifs
- modprobe: FATAL: Module cifs not found in directory 
/lib/modules/6.5.0-1016-azure
+ modprobe: FATAL: Module cifs not found in directory 
/lib/modules/6.5.0-1017-azure
  If modules-extra is installed, this works.
  
  [Fix]
  
  Replace fs/cifs/* with fs/smb/client/* in
  debian./control.d/.inclusion-list
  
  [Test Plan]
  
  1. Apply the fix to one of the derivative (azure), build a new kernel and 
install it
  2. Load cifs module
  $ modprobe cifs
  It should work without installing modules-extra.
  
  [Regression potential]
  
  Very low, it's a straightforward fix.
  
  [Other Info]
  Sending a patch for every derivative takes time and each derivative will be 
fixed once this proposal is acked via cranky fix.
  
  Original for lunar only
  SRU Justification:
  
  [Impact]
  
  Commit: "smb: move client and server files to common directory fs/smb" 
introduced in 2023.09.04 moved the fs/cifs directory to fs/sb/client. The 
inclusion list for linux-modules was not updated, it still contains the old 
path. This means that the cifs.ko module cannot be loaded if only linux-modules 
package is installed, now being part of linux-modules-extra.
  For lunar:main this is not a problem because linux-modules-extra is always 

[Kernel-packages] [Bug 2042546] Re: Include cifs.ko in linux-modules package

[Roxana Nicolescu]

** Also affects: linux (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Noble)
   Importance: Undecided
   Status: Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2042546

Title:
  Include cifs.ko in linux-modules package

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  New
Status in linux source package in Noble:
  Invalid

Bug description:
  SRU Justification:

  [Impact]

  Commit: "smb: move client and server files to common directory fs/smb" 
introduced in 2023.09.04 moved the fs/cifs directory to fs/sb/client. The 
inclusion list for linux-modules was not updated, it still contains the old 
path. This means that the cifs.ko module cannot be loaded if only linux-modules 
package is installed, now being part of linux-modules-extra.
  For lunar:main this is not a problem because linux-modules-extra is always 
installed, but for derivatives like aws, azure etc, this module cannot be 
loaded without explicitly installing linux-modules-extra.

  [How to reproduce it]:
  1. Install the latest azure kernel 6.2.0-1016.16
  2. Load cifs module
  $ modprobe cifs
  modprobe: FATAL: Module cifs not found in directory 
/lib/modules/6.2.0-1016-azure
  If modules-extra is installed, this works.

  [Fix]

  Replace fs/cifs/* with fs/smb/client/* in 
debian./control.d/.inclusiojn-list
  This is going to be done in s2023.10.02 cycle for derivatives.

  [Test Plan]

  1. Apply the fix to one of the derivative (azure), build a new kernel and 
install it
  2. Load cifs module
  $ modprobe cifs
  It should work without installing modules-extra.

  [Regression potential]

  Very low, it's a straightforward fix.

  [Other Info]
  Sending a patch for every derivative takes time and each derivative will be 
fixed once this proposal is acked.
  There is also the possibility to do it via cranky fix, but owners may omit it 
during security updates and it's hard to enforce it. Plus, it is a one-time 
change.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2042546] Re: Include cifs.ko in linux-modules package

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Mantic)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Noble)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Mantic)
 Assignee: (unassigned) => Roxana Nicolescu (roxanan)

** Changed in: linux (Ubuntu Noble)
 Assignee: (unassigned) => Roxana Nicolescu (roxanan)

** Changed in: linux (Ubuntu Mantic)
   Status: New => In Progress

** Changed in: linux (Ubuntu Noble)
   Status: Invalid => In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2042546

Title:
  Include cifs.ko in linux-modules package

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  In Progress
Status in linux source package in Noble:
  In Progress

Bug description:
  [Impact]

  Commit: "smb: move client and server files to common directory fs/smb" moved 
the fs/cifs directory to fs/sb/client. The inclusion list for linux-modules was 
not updated, it still contains the old path. This means that the cifs.ko module 
cannot be loaded if only linux-modules package is installed, now being part of 
linux-modules-extra.
  For the main kernels this is not a problem because linux-modules-extra is 
always installed, but for derivatives like aws, azure etc, this module cannot 
be loaded without explicitly installing linux-modules-extra.

  [How to reproduce it]:
  1. Install the latest azure kernel 6.5.0-1017.17
  2. Load cifs module
  $ modprobe cifs
  modprobe: FATAL: Module cifs not found in directory 
/lib/modules/6.5.0-1017-azure
  If modules-extra is installed, this works.

  [Fix]

  Replace fs/cifs/* with fs/smb/client/* in
  debian./control.d/.inclusion-list. First the
  main kernels are addressed, derivatives will be fixed via cranky fix.

  [Test Plan]

  1. Apply the fix to one of the derivative (azure), build a new kernel and 
install it
  2. Load cifs module
  $ modprobe cifs
  It should work without installing modules-extra.

  [Regression potential]

  Very low, it's a straightforward fix.

  [Other Info]
  Sending a patch for every derivative takes time and each derivative will be 
fixed once this proposal is acked via cranky fix.

  Original for lunar only
  SRU Justification:

  [Impact]

  Commit: "smb: move client and server files to common directory fs/smb" 
introduced in 2023.09.04 moved the fs/cifs directory to fs/sb/client. The 
inclusion list for linux-modules was not updated, it still contains the old 
path. This means that the cifs.ko module cannot be loaded if only linux-modules 
package is installed, now being part of linux-modules-extra.
  For lunar:main this is not a problem because linux-modules-extra is always 
installed, but for derivatives like aws, azure etc, this module cannot be 
loaded without explicitly installing linux-modules-extra.

  [How to reproduce it]:
  1. Install the latest azure kernel 6.2.0-1016.16
  2. Load cifs module
  $ modprobe cifs
  modprobe: FATAL: Module cifs not found in directory 
/lib/modules/6.2.0-1016-azure
  If modules-extra is installed, this works.

  [Fix]

  Replace fs/cifs/* with fs/smb/client/* in 
debian./control.d/.inclusiojn-list
  This is going to be done in s2023.10.02 cycle for derivatives.

  [Test Plan]

  1. Apply the fix to one of the derivative (azure), build a new kernel and 
install it
  2. Load cifs module
  $ modprobe cifs
  It should work without installing modules-extra.

  [Regression potential]

  Very low, it's a straightforward fix.

  [Other Info]
  Sending a patch for every derivative takes time and each derivative will be 
fixed once this proposal is acked.
  There is also the possibility to do it via cranky fix, but owners may omit it 
during security updates and it's hard to enforce it. Plus, it is a one-time 
change.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1971699] Re: disable Intel DMA remapping by default

[Roxana Nicolescu]

With no test case, I'll mark this as verified

** Tags removed: verification-needed-focal-linux-aws-5.15 
verification-needed-focal-linux-nvidia-tegra-5.15 
verification-needed-jammy-linux verification-needed-jammy-linux-aws-fips 
verification-needed-jammy-linux-nvidia-tegra
** Tags added: verification-done-focal-linux-aws-5.15 
verification-done-focal-linux-nvidia-tegra-5.15 verification-done-jammy-linux 
verification-done-jammy-linux-aws-fips 
verification-done-jammy-linux-nvidia-tegra

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1971699

Title:
  disable Intel DMA remapping by default

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  It seems that enabling Intel IOMMU can cause some weird gfx problems, see for 
example:
  
   https://bugs.launchpad.net/bugs/1971146
   https://bugs.launchpad.net/bugs/1965882

  [Test case]

  We don't have any specific test case, only other bug reports that
  tracked down the origin of the issue as being introduced when
  CONFIG_INTEL_IOMMU_DEFAULT_ON has been enabled by default.

  [Fix]

  Revert "UBUNTU: [Config] enable Intel DMA remapping options by
  default"

  [Regression potential]

  DMA remapping device not present at boot by default, users that
  require this feature will need to specifically add intel_iommu=on to
  the kernel boot parameters to enable it.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2052005] Re: Validate connection interval to pass Bluetooth Test Suite

[Roxana Nicolescu]

** Tags removed: verification-needed-focal-linux-aws-5.15 
verification-needed-focal-linux-nvidia-tegra-5.15 
verification-needed-jammy-linux-aws-fips 
verification-needed-jammy-linux-nvidia-tegra
** Tags added: verification-done-focal-linux-aws-5.15 
verification-done-focal-linux-nvidia-tegra-5.15 
verification-done-jammy-linux-aws-fips 
verification-done-jammy-linux-nvidia-tegra

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2052005

Title:
  Validate connection interval to pass Bluetooth Test Suite

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  Fix Released

Bug description:
  [Impact]
  Ubuntu doesn't pass Bluetooth Test Suite to get Bluetooth certified.

  [Fix]
  Validate max connection interval to pass test case
  "GAP/CONN/CPUP/BV-05-C 'Connection Parameter Update Procedure Invalid
  Parameters Central Responder'" 

  [Test]
  Run the test suite. With the patch applied the case is passed.

  [Where problems could occur]
  If any device requires setting a wrong interval to function properly,
  this might affect those devices in theory.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2055685] Re: Cranky update-dkms-versions rollout

[Roxana Nicolescu]

** Tags removed: verification-needed-focal-linux-nvidia-tegra-5.15 
verification-needed-jammy-linux-aws-fips 
verification-needed-jammy-linux-nvidia-tegra verification-needed-xenial-linux
** Tags added: verification-done-focal-linux-nvidia-tegra-5.15 
verification-done-jammy-linux-aws-fips 
verification-done-jammy-linux-nvidia-tegra verification-done-xenial-linux

** Tags removed: verification-needed-bionic-linux 
verification-needed-focal-linux-aws-5.15
** Tags added: verification-done-bionic-linux 
verification-done-focal-linux-aws-5.15

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2055685

Title:
  Cranky update-dkms-versions rollout

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]
  Having a common file for dkms-versions between main kernels and derivatives 
causes a lot of conflicts during rebase.
  Solution is to have a dkms-versions per kernels, under 
debian./dkms-version.

  While at it, instead of running ./update-dkms-version script, cranky
  update-dkms-versions was introduced. This is not used in xenial,
  therefore for xenial we only replaced debian/dkms-versions with
  debian./dkms-versions

  [Fix]
  This is needed only in the main kernels.
  1. remove update-dkms-version script (where needed), in xenial:linux we don't 
have it
  2. rename debian/dkms-version with debian.master/dkms-versions
  3. Replace debian/dkms-versions references in debian scripts and rules with 
$(DEBIAN)/dkms-versions

  Note for derivatives: These changes will be inherited from the parent during 
cranky rebase.
  The only change to the cranky process is: instead of using 
./update-dkms-versions
  script, cranky-update-dkms-versions should be used

  [Test]
  Build test on cbd. No issue found.

  [Regression pottential]
  Owners have tried this last cycle in derivatives and no issues were found.
  We may see build failures due to wrong dkms versions, but it will be fixed 
along the way.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2056143] Re: block/loop: No longer allows to create partitions

[Roxana Nicolescu]

** Tags removed: verification-needed-focal-linux-aws-5.15 
verification-needed-focal-linux-nvidia-tegra-5.15 
verification-needed-jammy-linux-aws-fips 
verification-needed-jammy-linux-nvidia-tegra
** Tags added: verification-done-focal-linux-aws-5.15 
verification-done-focal-linux-nvidia-tegra-5.15 
verification-done-jammy-linux-aws-fips 
verification-done-jammy-linux-nvidia-tegra

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2056143

Title:
  block/loop: No longer allows to create partitions

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  == SRU Justification ==

  -- Impact --
  In 22.04/Jammy with the GA 5.15 kernel there was an upstream change 
preventing partition table operations when GENHD_FL_NO_PART is set.
   1a721de8489f "block: don't add or resize partition on the disk with 
GENHD_FL_NO_PART"
  Beside of changing return codes and breaking some user-space that way this 
also causes loop block devices to no longer be able to have partitions manually 
created. This is because the loop block driver uses GENHD_FL_NO_PART to prevent 
active partition scans.

  -- Fix --
  This was changed in 5.19 (and thus Mantic is not affected) by introducing a 
separate flag to prevent those scans:
   b9684a71fca7 "block, loop: support partitions without scanning"
  The fix depends on a larger rewrite so it cannot be simply picked. The 
biggest change from the original is moving the check for the new flag into a 
helper function in genhd.h which checks whether a disk should be scanned for 
partitions. That function was dropped with the upstream rewrite and checking 
moved into the loop driver directly. But it felt like adjusting the helper was 
the better approach.

  Note: The upstream patch has a follow-up change submitted:
748008e1da92 "block: don't add partitions if GD_SUPPRESS_PART_SCAN is set"
  We do _NOT_ need that in Jammy/5.15 because block/partitions/core.c:
  blk_add_partitions() checks disk_part_scan_enabled() which was where we added 
the check for the backport instead of modifying disk_scan_partitions() directly.

  -- Testcase --
  $ fallocate -l 1G /tmp/blob
  $ LOOPDEV=$(sudo losetup --find --show /tmp/blob)
  $ sudo /usr/sbin/parted -s -m -a optimal $LOOPDEV -- unit KiB mklabel gpt 
mkpart primary 0% 100%

  -- Regression Potential --
  If things go wrong it might be other devices which no longer get scanned 
automatically or other issues with the loop block driver.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2052827] Re: performance: mm/memcontrol.c: remove the redundant updating of stats_flush_threshold

[Roxana Nicolescu]

** Tags removed: verification-needed-focal-linux-nvidia-tegra-5.15 
verification-needed-jammy-linux-nvidia-tegra
** Tags added: verification-passed-focal-linux-nvidia-tegra-5.15 
verification-passed-jammy-linux-nvidia-tegra

** Tags removed: verification-passed-focal-linux-aws-5.15 
verification-passed-focal-linux-nvidia-tegra-5.15 
verification-passed-jammy-linux verification-passed-jammy-linux-aws-fips 
verification-passed-jammy-linux-nvidia-tegra
** Tags added: verification-done-focal-linux-aws-5.15 
verification-done-focal-linux-nvidia-tegra-5.15 verification-done-jammy-linux 
verification-done-jammy-linux-aws-fips 
verification-done-jammy-linux-nvidia-tegra

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2052827

Title:
  performance: mm/memcontrol.c: remove the redundant updating of
  stats_flush_threshold

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  This is a public version of https://bugs.launchpad.net/bugs/2034981

  Backport upstream commit:
 
  873f64b791a2 mm/memcontrol.c: remove the redundant updating of 
stats_flush_threshold

  to jammy.

  
  [Impact]

  
Remove the redundant updating of stats_flush_threshold. If the global var 
stats_flush_threshold has exceeded the trigger value for 
__mem_cgroup_flush_stats, further increment is unnecessary.

  This is targeting Sapphire Rapids platforms.

  
  [Fix]

  Upstream commit 873f64b791a2 fixes this issue.  The fix involves not
  updating the status after a certain threshold has been hit as it is
  unnecessary.

  [Test Plan]

  I have tested the changes, and hit no regressions.

  [Where problems could occur]

  As the change has been upstream since 6.0-rc1, and is reducing a stats
  update which isn't needed, the change for regressions should be
  minimal.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2051727] Re: tcp: Add memory barrier to tcp_push()

[Roxana Nicolescu]

** Tags removed: verification-passed-focal-linux-aws 
verification-passed-focal-linux-aws-5.15 
verification-passed-jammy-linux-aws-fips verification-passed-mantic-linux-aws
** Tags added: verification-done-focal-linux-aws 
verification-done-focal-linux-aws-5.15 verification-done-jammy-linux-aws-fips 
verification-done-mantic-linux-aws

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2051727

Title:
  tcp: Add memory barrier to tcp_push()

Status in linux package in Ubuntu:
  Invalid
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-aws source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Invalid
Status in linux-aws source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Invalid
Status in linux-aws source package in Mantic:
  Fix Committed

Bug description:
  Recently a patch has been accepted on the Linux Kernel regarding the
  TCP stack which fix an additional +40ms latency on ARM64 CPU
  architecture without impacting other CPU types.

  More information can be find in here:
  https://lore.kernel.org/netdev/20240119190133.43698-1-dipi...@amazon.com/

  Would be possible to include the following patch as part of Linux
  image on the most recent and LTS maintained Ubuntu versions?

  
  Patch:
  ```
  ---
   net/ipv4/tcp.c | 1 +
   1 file changed, 1 insertion(+)

  diff --git a/net/ipv4/tcp.c b/net/ipv4/tcp.c
  index ff6838ca2e58..7bce79beca2b 100644
  --- a/net/ipv4/tcp.c
  +++ b/net/ipv4/tcp.c
  @@ -722,6 +722,7 @@ void tcp_push(struct sock *sk, int flags, int mss_now,
if (!test_bit(TSQ_THROTTLED, >sk_tsq_flags)) {
NET_INC_STATS(sock_net(sk), LINUX_MIB_TCPAUTOCORKING);
set_bit(TSQ_THROTTLED, >sk_tsq_flags);
  + smp_mb__after_atomic();
}
/* It is possible TX completion already happened
 * before we set TSQ_THROTTLED.
  -- 
  ```

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2052817] Re: cpufreq: intel_pstate: Enable HWP IO boost for all servers

[Roxana Nicolescu]

** Tags removed: verification-needed-focal-linux-nvidia-tegra-5.15 
verification-needed-jammy-linux-nvidia-tegra
** Tags added: verification-passed-focal-linux-nvidia-tegra-5.15 
verification-passed-jammy-linux-nvidia-tegra

** Tags removed: verification-passed-focal-linux-aws-5.15 
verification-passed-focal-linux-nvidia-tegra-5.15 
verification-passed-jammy-linux verification-passed-jammy-linux-aws-fips 
verification-passed-jammy-linux-nvidia-tegra
** Tags added: verification-done-focal-linux-aws-5.15 
verification-done-focal-linux-nvidia-tegra-5.15 verification-done-jammy-linux 
verification-done-jammy-linux-aws-fips 
verification-done-jammy-linux-nvidia-tegra

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2052817

Title:
  cpufreq: intel_pstate: Enable HWP IO boost for all servers

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  
  This is a public version of https://bugs.launchpad.net/bugs/2009321

  Backport cpufreq: intel_pstate: Enable HWP IO boost for all servers
  [upstream 1f5e62f5fb217f2c1e003236be7d03cf606c26c4 (merged in 6.4)] to
  jammy.

  [Impact]

  Currently there is a CPU model check for Skylake desktop and server
  along with the ACPI PM profile for performance and enterprise servers
  to enable IO boost. Patch removes the CPU model check, so that all
  current server models enable HWP IO boost by default.

  The HWP IO boost results in improvements for IO performance on both
  Ice Lake and Sapphire Rapid servers.

  Phoronix review: https://www.phoronix.com/news/Intel-ICL-SPR-IO-Perf-
  Boost

  Upstream review Link: https://lore.kernel.org/linux-
  pm/20230303041411.3161780-1-srinivas.pandruv...@linux.intel.com/

  [Fix]

  Upstream patch:
   cpufreq: intel_pstate: Enable HWP IO boost for all servers 
1f5e62f5fb217f2c1e003236be7d03cf606c26c4

  was merged to fix this.  This will be back porting it to jammy.

  [Test Plan]

  I have tested this code, as has Intel.

  [Where problems could occur]

  The risk for regression is low.   The change is fairly narrow, and has
  been upstreamed for some time.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2053069] Re: performance: address_space: add padding for i_map and i_mmap_rwsem to mitigate a false sharing

[Roxana Nicolescu]

** Tags removed: verification-needed-focal-linux-nvidia-tegra-5.15 
verification-needed-jammy-linux-nvidia-tegra 
verification-passed-focal-linux-aws-5.15 verification-passed-jammy-linux 
verification-passed-jammy-linux-aws-fips
** Tags added: verification-done-focal-linux-aws-5.15 
verification-done-focal-linux-nvidia-tegra-5.15 verification-done-jammy-linux 
verification-done-jammy-linux-aws-fips 
verification-done-jammy-linux-nvidia-tegra

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2053069

Title:
  performance: address_space: add padding for i_map and i_mmap_rwsem to
  mitigate a false sharing

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  This is a public version of https://bugs.launchpad.net/bugs/2034983

  [Description]
When running UnixBench/shell1 cases, we observed high false 
sharing for accessing i_mmap against i_mmap_rwsem.
The patch places the i_mmap and i_mmap_rwsem in separate cache lines to 
avoid this false sharing problem.

  [Hardware Information]
Architecture:
  Intel / AMD (x86_64)
Platform(s):
  DNP
Date HW is expected at Canonical:

Component(s):
  Performance and Scalability

  [Software Information]
Target Version:
  23.10
Target Kernel:
  TBD
Commit IDs:
  aee79d4e5271 fs/address_space: add alignment padding for i_map and 
i_mmap_rwsem to mitigate a false sharing.
External Links:

  [Business Justification]

  [Testing guidance]

  [External ID]
OSVE-5159

  
  Here's the commit ID: aee79d4e5271cee4ffa89ed830189929a6272eb8

  
https://github.com/torvalds/linux/commit/aee79d4e5271cee4ffa89ed830189929a6272eb8

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2054699] Re: x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform

[Roxana Nicolescu]

** Tags removed: verification-needed-jammy-linux-nvidia-tegra 
verification-passed-focal-linux-aws-5.15 verification-passed-jammy-linux 
verification-passed-jammy-linux-aws-fips verification-passed-mantic-linux
** Tags added: verification-done-focal-linux-aws-5.15 
verification-done-jammy-linux verification-done-jammy-linux-aws-fips 
verification-done-jammy-linux-nvidia-tegra verification-done-mantic-linux

** Tags removed: verification-needed-focal-linux-nvidia-tegra-5.15
** Tags added: verification-done-focal-linux-nvidia-tegra-5.15

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2054699

Title:
  x86: performance: tsc: Extend watchdog check exemption to 4-Sockets
  platform

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  This is a public version of https://bugs.launchpad.net/bugs/2044822

  
  SRU Justification:

  [Impact]
Fix tsc clocksource on 4 sockets x86 servers was wrongly judged as 
'unstable' by 'jiffies' and other watchdogs, and disabled

  
  [Fix]
  cherry-pick 
  233756a640be x86/tsc: Extend watchdog check exemption to 4-Sockets 
platform
  from upstream fixes this 

  [Test Plan]
  This has been tested by intel, and has been upstreamed for a while. 

  
  [Where problems could occur]
  This is a fairly narrow change, and extends a behaviour correction to cover 
up to 4-socket machines, rather than just 2 socket machines

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2056475] Re: aws: Backport latest ENA driver in upstream Linux to enable IRQ moderation

[Roxana Nicolescu]

** Tags removed: verification-passed-focal-linux-aws 
verification-passed-focal-linux-aws-5.15 
verification-passed-jammy-linux-aws-fips verification-passed-mantic-linux-aws
** Tags added: verification-done-focal-linux-aws 
verification-done-focal-linux-aws-5.15 verification-done-jammy-linux-aws-fips 
verification-done-mantic-linux-aws

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2056475

Title:
  aws: Backport latest ENA driver in upstream Linux to enable IRQ
  moderation

Status in linux-aws package in Ubuntu:
  Fix Committed
Status in linux-aws source package in Focal:
  Fix Committed
Status in linux-aws source package in Jammy:
  Fix Committed
Status in linux-aws source package in Mantic:
  Fix Committed
Status in linux-aws source package in Noble:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

  In Ubuntu AMIs for x86 and Graviton based EC2 instances, the standard
  Ubuntu AMI comes without IRQ moderation enabled for ENA, which for our
  latest generation instances with networking heavy workloads is up to a
  25% performance regression (i.e. NGINX in a load-balancing
  configuration).

  
  [Fix]

  
  The mainline Linux kernel will now support IRQ moderation by default for ENA 
in the 6.9 kernel release via this patch: 
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/ethernet/amazon/ena?id=50d7a2660579889fba28b7e4543d4ce85aa2311b

  [Test Plan]

  AWS tested

  [Where problems could occur]

  By enabling adaptive coalescing, the default interrupt behaviour will
  by changed to be more adaptive, which shows improvements on heavy
  network workloads, but my change the behaviour and performance on
  other network workloads differently.   Rather than handling the
  interrupts based off of a fixed amount of time elapsed, it will change
  to an adaptive based approach.   There should be no negative impact on
  light workloads, and a positive impact on heavy work loads.  If there
  is an impact though, this option can be disabled via the ethtool
  command.

  [Other Info]

  SF: 00380449

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2051727] Re: tcp: Add memory barrier to tcp_push()

[Roxana Nicolescu]

This was added to linux-aws, not linux and it messed up the verification
process

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

** Changed in: linux (Ubuntu)
   Status: New => Invalid

** Changed in: linux (Ubuntu Focal)
   Status: Fix Committed => Invalid

** Changed in: linux (Ubuntu Jammy)
   Status: Fix Committed => Invalid

** Changed in: linux (Ubuntu Mantic)
   Status: Fix Committed => Invalid

** Changed in: linux-aws (Ubuntu)
   Status: New => Invalid

** Changed in: linux-aws (Ubuntu Focal)
 Assignee: (unassigned) => Philip Cox (philcox)

** Changed in: linux-aws (Ubuntu Jammy)
 Assignee: (unassigned) => Philip Cox (philcox)

** Changed in: linux-aws (Ubuntu Mantic)
 Assignee: (unassigned) => Philip Cox (philcox)

** Changed in: linux-aws (Ubuntu Focal)
   Status: New => Fix Committed

** Changed in: linux-aws (Ubuntu Jammy)
   Status: New => Fix Committed

** Changed in: linux-aws (Ubuntu Mantic)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2051727

Title:
  tcp: Add memory barrier to tcp_push()

Status in linux package in Ubuntu:
  Invalid
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-aws source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Invalid
Status in linux-aws source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Invalid
Status in linux-aws source package in Mantic:
  Fix Committed

Bug description:
  Recently a patch has been accepted on the Linux Kernel regarding the
  TCP stack which fix an additional +40ms latency on ARM64 CPU
  architecture without impacting other CPU types.

  More information can be find in here:
  https://lore.kernel.org/netdev/20240119190133.43698-1-dipi...@amazon.com/

  Would be possible to include the following patch as part of Linux
  image on the most recent and LTS maintained Ubuntu versions?

  
  Patch:
  ```
  ---
   net/ipv4/tcp.c | 1 +
   1 file changed, 1 insertion(+)

  diff --git a/net/ipv4/tcp.c b/net/ipv4/tcp.c
  index ff6838ca2e58..7bce79beca2b 100644
  --- a/net/ipv4/tcp.c
  +++ b/net/ipv4/tcp.c
  @@ -722,6 +722,7 @@ void tcp_push(struct sock *sk, int flags, int mss_now,
if (!test_bit(TSQ_THROTTLED, >sk_tsq_flags)) {
NET_INC_STATS(sock_net(sk), LINUX_MIB_TCPAUTOCORKING);
set_bit(TSQ_THROTTLED, >sk_tsq_flags);
  + smp_mb__after_atomic();
}
/* It is possible TX completion already happened
 * before we set TSQ_THROTTLED.
  -- 
  ```

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2054094] Re: linux-tools-common: man page of usbip[d] is misplaced

[Roxana Nicolescu]

Tested on mantic, jammy and focal, it works.

** Tags removed: verification-needed-focal-linux 
verification-needed-focal-linux-aws-5.15 verification-needed-jammy-linux 
verification-needed-jammy-linux-aws-fips verification-needed-mantic-linux
** Tags added: verification-done-focal-linux 
verification-done-focal-linux-aws-5.15 verification-done-jammy-linux 
verification-done-jammy-linux-aws-fips verification-done-mantic-linux

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2054094

Title:
  linux-tools-common: man page of usbip[d] is misplaced

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  Fix Released

Bug description:
  [Impact]

  Just try man uspip, it doesn't work, because the man page file is at

  /usr/share/man/man1/usbipd.8.gz
    ^   ^^^

  Looks wrong :)

  [Test Case]

  $ sudo apt install linux-tools-common
  $ man usbip
  No manual entry for usbip

  [Where Problems Could Occur]

  Manpage packaging change, no runtime impact expected.

  [Additional Description]

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-tools-common 5.15.0-94.104
  ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmitry 3196 F pulseaudio
   /dev/snd/pcmC0D0p:   dmitry 3196 F...m pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 16 12:37:42 2024
  InstallationDate: Installed on 2022-04-19 (668 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: Dell Inc. XPS 15 9500
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic 
root=UUID=21336f25-776c-4f5f-b70c-8cf96f1f0d22 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-17-generic N/A
   linux-backports-modules-6.5.0-17-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.26
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-08-21 (543 days ago)
  dmi.bios.date: 08/15/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.24.1
  dmi.board.name: 0XWT2F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.24.1:bd08/15/2023:br1.24:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr:sku097D:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9500
  dmi.product.sku: 097D
  dmi.sys.vendor: Dell Inc.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2056373] Re: Problems with HVCS and hotplugging

[Roxana Nicolescu]

Based on this, I'll set the tag to done. Thanks for testing it

** Tags removed: verification-needed-focal-linux
** Tags added: verification-done-focal-linux

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2056373

Title:
  Problems with HVCS and hotplugging

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Invalid

Bug description:
  SRU Justification:
  ==

  [Impact]

   * HVCS (Hypervisor Virtual Console Server) is broken because the
 virtual terminal mkvterm fails, caused by pvmutil failing.

   * When mkvterm is ran, it ultimately fails because it calls pvmutil
 which fails.
 pvmutil calls drmgr, and drmgr is adding a slot correctly.
 However, when drmgr writes the slot information to ?/add_slot,
 the return is -ENODEV.

   * This leads to HVCS never having probe() called.

   * In addition, HVCS is missing patches/fixes, and is broken without
  them.

  [Fix]

   * Fix one and two is required for focal only, all other for focal and
  jammy:

   * 57409d4fb12c 57409d4fb12c185b2c0689e0496878c8f6bb5b58
 "powerpc/pseries: Fix bad drc_index_start value parsing of drc-info entry"

   * c5e76fa05b2d c5e76fa05b2df519b9f08571cc57e623c1569faa
 "powerpc/pseries: Fix of_read_drc_info_cell() to point at next record"

   * 6a9a733edd46 6a9a733edd46732e906d976dc21a42dd361e53cc
 "hvcs: Fix hvcs port reference counting"

   * 760aa5e81f33 760aa5e81f33e0da82512c4288489739a6d1c556
 "hvcs: Use dev_groups to manage hvcs device attributes"

   * 503a90dd619d 503a90dd619d52dcac2cc68bd742aa914c7cd47a
 "hvcs: Use driver groups to manage driver attributes"

   * 3a8d3b366ce4 3a8d3b366ce47024bf274eac783f8af5df2780f5
 "hvcs: Get reference to tty in remove"

   * d432228bc7b1 d432228bc7b1b3f0ed06510278ff5a77b3749fe6
 "hvcs: Use vhangup in hotplug remove"

   * 28d49f8cbe9c 28d49f8cbe9c7966f91ee1b5ec2f997f6e55bf9f
 "hvcs: Synchronize hotplug remove with port free"

  [Test Plan]

   * The high level test plan is to run mkvterm with an id.
   
   * mkvterm will fail because /dev/hvcs* device nodes are missing.

   * Details see https://bugs.launchpad.net/bugs/2023243 for more information.
 Especially the script provided by IBM
 (see original bug description: `---Steps to Reproduce---`).

   * IBM will (stress) test the updated kernel(s) provided in -proposed.

  [Where problems could occur]

   * The first two commits affect arch/powerpc/platforms/pseries/of_helpers.c
 and are needed to fix the hotplugging issue seen when drmgr goes to write
 the slot information to /sys/bus/pci/slots/control/add_slot.
 In case of issues here hotplugging with drmgr might break.

   * The issue lies in rpadlpar_io and rpaphp calling an of helper function
 of_read_drc_info_cell(). Without these commits, the value stored
 drc_index_start is incorrect.
 This ultimately results in the entire SLOT string being incorrect,
 and rpaphp never finding the newly added slot by drmgr.
 rpadlpar then returns -ENODEV.
 Therefore, HVCS is never probed, and the device nodes are never created.

   * HVCS, rpadlpar_io, and rpaphp should ideally not even need to be loaded
 prior to drmgr adding a vio slot.
 If rpadlpar_io and rpaphp are not loaded, drmgr will load them.
 In addition, if rpadlpar_io and rpaphp register the new slot correctly,
 rpadlpar_io will call dlpar_add_vio_slot(),
 which calls vio_register_device_node() with the device node.
 This is what tells the driver core to init and probe HVCS
 (which is needed to create the device nodes).

   * The remaning 6 commits are needed for HVCS, that is essentially
 broken without them.
 Overall, issues they fix are race conditions, hotplug remove issues,
 as well as memory leaks.

   * Please notice that this is entirely ppc64el architecture-specifc.

  [Other Info]

   * All the commits listed above are included in mantic and noble.
 Hence these are set to Invalid.

   * Meanwhile these requested commits have been added to other
 kernels and distros.
  __

  ---Problem Description---
  Issues with HVCS and hotplugging issues.

  When working on Canonical bug 2023243, it was discovered that mkvterm
  was not working for multiple reasons. This bug will cover the issues
  found in HVCS, and hotplugging issues found when drmgr writes the slot
  information to .../add_slot.

  When mkvterm is ran, it ultimately fails because it calls pvmutil
  which fails. pvmutil calls drmgr, and drmgr is adding a slot
  correctly. However, when drmgr writes the slot information to
  ?/add_slot, the 

[Kernel-packages] [Bug 2054567] Re: Fix bpf selftests build failure after v5.15.139 update

[Roxana Nicolescu]

** Tags removed: verification-needed-focal-linux-aws-5.15 
verification-needed-jammy-linux verification-needed-jammy-linux-aws-fips
** Tags added: verification-done-focal-linux-aws-5.15 
verification-done-jammy-linux verification-done-jammy-linux-aws-fips

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2054567

Title:
  Fix bpf selftests build failure after v5.15.139 update

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  SRU justification

  [Impact]
  Upstream v5.15.139 (#lp2049432) brought commit
  "selftests/bpf: Test tail call counting with bpf2bpf and data on stack"
  that affects one of the bpf kselftests (tailcall_bpf2bpf6).
  because LIBBPF_OPTS macro does not exists, it does not compile. Error below.

  [Fix]
  Initially, I thought cherry-picking commit
  "libbpf: Rename DECLARE_LIBBPF_OPTS into LIBBPF_OPTS" would be the best,
  but upstream stable just reverted the commit that broke it. Hence the fix
  consists of cherry-picking this commit from stable upstream 5.15.49:
  Commit 62900d358c48 (Revert "selftests/bpf: Test tail call counting with 
bpf2bpf and data on stack")

  [Test]
  This should be solved soon, but compileselftests debian rule does not
  compile bpf selftests.
  I tested it by using our regression testing tooling, but same results can
  be achieved by running:
  $ make -C linux/tools/testing/selftests TARGETS=bpf SKIP_TARGETS= clean all 
KDIR=/usr/src/linux-headers-5.15.0--generic
  from the linux tree directory

  Without the fix, it fails to compile:

/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:
 In function ‘test_tailcall_bpf2bpf_6’:

/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:9:
 warning: implicit declaration of function ‘LIBBPF_OPTS’; did you mean 
‘LIBBPF_API’? [-Wimplicit-function-declaration]
  822 | LIBBPF_OPTS(bpf_test_run_opts, topts,
  | ^~~
  | LIBBPF_API

/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:21:
 error: ‘bpf_test_run_opts’ undeclared (first use in this function)
  822 | LIBBPF_OPTS(bpf_test_run_opts, topts,
  | ^

/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:21:
 note: each undeclared identifier is reported only once for each function it 
appears in

/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:40:
 error: ‘topts’ undeclared (first use in this function)
  822 | LIBBPF_OPTS(bpf_test_run_opts, topts,
  | ^

/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:823:17:
 error: expected expression before ‘.’ token
  823 | .data_in = _v4,
  | ^
make[1]: *** [Makefile:471: 
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tailcalls.test.o]
 Error 1
make: *** [Makefile:172: all] Error 2

  With the fix, it compiles.

  [Regression potential]
  The only place this is being used is selftests, so the risk is very low.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2055686] Re: Drop ABI checks from kernel build

[Roxana Nicolescu]

** Tags removed: verification-needed-bionic-linux 
verification-needed-bionic-linux-azure-4.15 
verification-needed-bionic-linux-gcp-4.15 verification-needed-focal-linux 
verification-needed-focal-linux-aws-5.15 verification-needed-jammy-linux 
verification-needed-jammy-linux-aws-fips verification-needed-mantic-linux 
verification-needed-trusty-linux-azure verification-needed-xenial-linux 
verification-needed-xenial-linux-aws verification-needed-xenial-linux-aws-hwe 
verification-needed-xenial-linux-fips verification-needed-xenial-linux-oracle
** Tags added: verification-done-bionic-linux 
verification-done-bionic-linux-azure-4.15 
verification-done-bionic-linux-gcp-4.15 verification-done-focal-linux 
verification-done-focal-linux-aws-5.15 verification-done-jammy-linux 
verification-done-jammy-linux-aws-fips verification-done-mantic-linux 
verification-done-trusty-linux-azure verification-done-xenial-linux 
verification-done-xenial-linux-aws verification-done-xenial-linux-aws-hwe 
verification-done-xenial-linux-fips verification-done-xenial-linux-oracle

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2055686

Title:
  Drop ABI checks from kernel build

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  Drop the internal checks on the kernel ABI, module lists, et al.
  These checks are now applied after the fact by the workflow manager.
  This allows us to validate change after the builds complete so we do
  no waste builds which were correct but not annotated at upload time.

  NOTE: we still record the ABI data and publish it in linux-buildinfo
  files.  These are used to perform the external validation.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2045561] Re: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules

[Roxana Nicolescu]

Tested on jammy and mantic main kernels. Derivatives inherited this
change.

** Tags removed: verification-needed-focal-linux-aws-5.15 
verification-needed-jammy-linux verification-needed-jammy-linux-aws-fips 
verification-needed-mantic-linux
** Tags added: verification-done-focal-linux-aws-5.15 
verification-done-jammy-linux verification-done-jammy-linux-aws-fips 
verification-done-mantic-linux

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2045561

Title:
  linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support)
  from linux-modules-extra to linux-modules

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  Fix Released

Bug description:
  SRU Justification

  [Impact]

  The dmi-sysfs.ko module (CONFIG_DMI_SYSFS) is currently shipped in
  linux-modules-extra. This makes it hard to pull in via the linux-
  virtual package, it can only come from the linux-generic one that also
  pulls in the firmware and everything else needed for baremetal, and
  that serves no purpose in a qemu VM. This stops VMs using these
  kernels from being configurable using qemu or cloud-hypervisor's
  SMBIOS type 11 strings. This feature is supported and used widely by
  systemd:

  https://www.freedesktop.org/software/systemd/man/latest/smbios-type-11.html
  https://systemd.io/CREDENTIALS/

  A user launching a VM using the linux-kvm kernel image is not able to
  specify SMBIOS strings to automatically configured userspace services
  and programs due to the lack of this kconfig. We make extensive use of
  these in systemd's upstream CI, which is running on Github Actions,
  which uses Jammy, so it would be great to have this backported.

  For example:

  qemu-system-x86_64 \
  -machine type=q35,accel=kvm,smm=on \
  -smp 2 \
  -m 1G \
  -cpu host \
  -nographic \
  -nodefaults \
  -serial mon:stdio \
  -drive if=none,id=hd,file=ubuntu_jammy.raw,format=raw \
  -device virtio-scsi-pci,id=scsi \
  -device scsi-hd,drive=hd,bootindex=1 \
  -smbios type=11,value=io.systemd.credential:mycred=supersecret

  [Fix]

  Please consider moving this module to linux-modules.

  These are already enabled in the 'main' kernel config, and in other
  distros. In Debian/Archlinux/Fedora it is a built-in, and on SUSE it
  is a module installed by default.

  To verify this works, it is sufficient to check that the
  /sys/firmware/dmi/entries/ directory in sysfs is present:

  $ ls /sys/firmware/dmi/entries/
  0-0126-1   126-4  126-8  130-0  133-0  136-0  140-2  15-0  18-0  21-1   
221-1  24-0  7-1  8-2  8-6
  1-0126-10  126-5  126-9  131-0  134-0  14-0   140-3  16-0  19-0  219-0  
221-2  3-0   7-2  8-3  9-0
  12-0   126-2   126-6  127-0  131-1  135-0  140-0  140-4  17-0  2-0   22-0   
221-3  4-0   8-0  8-4  9-1
  126-0  126-3   126-7  13-0   132-0  135-1  140-1  14-1   17-1  21-0  221-0  
222-0  7-0   8-1  8-5

  Without this module installed and loaded, the directory won't be
  there. Once enabled, it will be there.

  [Test]

  1. pull built linux-modules packages for architectures with do_extras_package
 set to true;
  2. extract the deb and check if dmi-sysfs kernel module file exists:

 $ dpkg-deb -R linux-modules-*.deb .
 $ find . -name dmi-sysfs.ko\*

  [Regression Potential]

  Moving a module from a less-common to a more-common package should not
  have any negative side effects. The main effect will be a little more
  disk space used by the more common package, whether the module is in
  use or not. There will also be more functionality available in the
  default installation, which means a slightly increased surface and
  possibility of new bugs in case it gets used.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2051947] Re: Sound: Add rtl quirk of M70-Gen5

[Roxana Nicolescu]

** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic-linux

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2051947

Title:
  Sound: Add rtl quirk of M70-Gen5

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  When plugin the headset jack, only speaker is identified.

  [Fix]
  Add ALC283_FIXUP_HEADSET_MIC quirk to make its headset mic work.

  [Test]
  Vendor tested on hardware, headset mic works fine.

  [Where problems could occur]
  It may break audio.

  This commit is merged by stable updates in noble kernel,
  5.15 doesn't support this platform,
  SRU for mantic and oem-6.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2051947/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2059143] [NEW] Remove getabis scripts

[Roxana Nicolescu]

Public bug reported:

SRU Justification

[Impact]
With ABI checks removed from the tree (#LP2055685), there's no need to
download the buildinfo from a previous version.

[Fix]
This is needed only in the main kernels.
1. remove the common getabis script
2. remove per kernel getabis file (this will be done with cranky fix)

[Test]
Build test on cbd. No issue found. Also cranked the kernels in advance to see 
if there were issues, but no issue was found.

[Regression potential]
In the current cycle, the ABI checks have been removed and this is not used 
anymore. No issues have been found. Now we're just removing an unused feature, 
therefore the regression potential is none.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux (Ubuntu Trusty)
 Importance: High
 Assignee: Roxana Nicolescu (roxanan)
 Status: In Progress

** Affects: linux (Ubuntu Xenial)
 Importance: High
 Assignee: Roxana Nicolescu (roxanan)
 Status: In Progress

** Affects: linux (Ubuntu Bionic)
 Importance: High
 Assignee: Roxana Nicolescu (roxanan)
 Status: In Progress

** Affects: linux (Ubuntu Focal)
 Importance: High
 Assignee: Roxana Nicolescu (roxanan)
 Status: In Progress

** Affects: linux (Ubuntu Jammy)
 Importance: High
 Assignee: Roxana Nicolescu (roxanan)
 Status: In Progress

** Affects: linux (Ubuntu Mantic)
 Importance: High
 Assignee: Roxana Nicolescu (roxanan)
 Status: In Progress

** Also affects: linux (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
   Status: New => Invalid

** Changed in: linux (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: linux (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: linux (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux (Ubuntu Focal)
   Status: New => In Progress

** Changed in: linux (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux (Ubuntu Mantic)
   Status: New => In Progress

** Changed in: linux (Ubuntu Trusty)
 Assignee: (unassigned) => Roxana Nicolescu (roxanan)

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Roxana Nicolescu (roxanan)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Roxana Nicolescu (roxanan)

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Roxana Nicolescu (roxanan)

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Roxana Nicolescu (roxanan)

** Changed in: linux (Ubuntu Mantic)
     Assignee: (unassigned) => Roxana Nicolescu (roxanan)

** Changed in: linux (Ubuntu Trusty)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Mantic)
   Importance: Undecided => High

** Description changed:

  SRU Justification
  
  [Impact]
- Having a common file for dkms-versions between main kernels and derivatives 
causes a lot of conflicts during rebase.
- Solution is to have a dkms-versions per kernels, under 
debian./dkms-version.
+ With ABI checks removed from the tree (#LP2055685), there's no need to
+ download the buildinfo from a previous version.
  
- While at it, instead of running ./update-dkms-version script, cranky
- update-dkms-versions was introduced.
  
  [Fix]
  This is needed only in the main kernels.
- 1. remove update-dkms-version script
- 2. rename debian/dkms-version with debian.master/dkms-versions
- 3. Replace debian/dkms-versions references in debian scripts and rules with 
$(DEBIAN)/dkms-versions
- 
- Note for derivatives: These changes will be inherited from the parent during 
cranky rebase.
- The only change to the cranky process is: instead of using 
./update-dkms-versions
- script, cranky-update-dkms-versions should be used
+ 1. remove the common getabis script
+ 2. remove per kernel getabis file (this will be done with cranky fix for 
derivatives)
  
  [Test]
  Build test on cbd. No issue found.
  
- [Regression pottential]
- Owners have tried this last cycle in derivatives and no issues were found.
- We may see build failures due to wrong dkms versions, but it will be fixed 
along the way.
+ [Regression potential]
+ In the current cycle, the A

[Kernel-packages] [Bug 2055685] Re: Cranky update-dkms-versions rollout

[Roxana Nicolescu]

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: linux (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Roxana Nicolescu (roxanan)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Roxana Nicolescu (roxanan)

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Bionic)
   Importance: Undecided => High

** Description changed:

  SRU Justification
  
  [Impact]
  Having a common file for dkms-versions between main kernels and derivatives 
causes a lot of conflicts during rebase.
  Solution is to have a dkms-versions per kernels, under 
debian./dkms-version.
  
  While at it, instead of running ./update-dkms-version script, cranky
  update-dkms-versions was introduced.
  
  [Fix]
  This is needed only in the main kernels.
- 1. remove update-dkms-version script
+ 1. remove update-dkms-version script (where needed), in xenial:linux we don't 
have it
  2. rename debian/dkms-version with debian.master/dkms-versions
  3. Replace debian/dkms-versions references in debian scripts and rules with 
$(DEBIAN)/dkms-versions
  
  Note for derivatives: These changes will be inherited from the parent during 
cranky rebase.
  The only change to the cranky process is: instead of using 
./update-dkms-versions
  script, cranky-update-dkms-versions should be used
  
  [Test]
  Build test on cbd. No issue found.
  
  [Regression pottential]
  Owners have tried this last cycle in derivatives and no issues were found.
  We may see build failures due to wrong dkms versions, but it will be fixed 
along the way.

** Description changed:

  SRU Justification
  
  [Impact]
  Having a common file for dkms-versions between main kernels and derivatives 
causes a lot of conflicts during rebase.
  Solution is to have a dkms-versions per kernels, under 
debian./dkms-version.
  
  While at it, instead of running ./update-dkms-version script, cranky
- update-dkms-versions was introduced.
+ update-dkms-versions was introduced. This is not used in xenial,
+ therefore for xenial we only replaced debian/dkms-versions with
+ debian./dkms-versions
  
  [Fix]
  This is needed only in the main kernels.
  1. remove update-dkms-version script (where needed), in xenial:linux we don't 
have it
  2. rename debian/dkms-version with debian.master/dkms-versions
  3. Replace debian/dkms-versions references in debian scripts and rules with 
$(DEBIAN)/dkms-versions
  
  Note for derivatives: These changes will be inherited from the parent during 
cranky rebase.
  The only change to the cranky process is: instead of using 
./update-dkms-versions
  script, cranky-update-dkms-versions should be used
  
  [Test]
  Build test on cbd. No issue found.
  
  [Regression pottential]
  Owners have tried this last cycle in derivatives and no issues were found.
  We may see build failures due to wrong dkms versions, but it will be fixed 
along the way.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2055685

Title:
  Cranky update-dkms-versions rollout

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]
  Having a common file for dkms-versions between main kernels and derivatives 
causes a lot of conflicts during rebase.
  Solution is to have a dkms-versions per kernels, under 
debian./dkms-version.

  While at it, instead of running ./update-dkms-version script, cranky
  update-dkms-versions was introduced. This is not used in xenial,
  therefore for xenial we only replaced debian/dkms-versions with
  debian./dkms-versions

  [Fix]
  This is needed only in the main kernels.
  1. remove update-dkms-version script (where needed), in xenial:linux we don't 
have it
  2. rename debian/dkms-version with debian.master/dkms-versions
  3. Replace debian/dkms-versions references in debian scripts and rules with 
$(DEBIAN)/dkms-versions

  Note for derivatives: These changes will be inherited from the parent during 
cranky rebase.
  The only change to the cranky process is: instead of using 
./update-dkms-versions
  script, cranky-update-dkms-versions should be used

  [Test]
  Build test on cbd. No issue found.

  [Regression pottential]
  Owners have tried this last cycle in derivatives and no issues were found.
  We may see build failures due to wrong dkms versions, but it will be fixed 
along t

[Kernel-packages] [Bug 2055686] Re: Drop ABI checks from kernel build

[Roxana Nicolescu]

** Also affects: linux (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Trusty)
 Assignee: (unassigned) => Roxana Nicolescu (roxanan)

** Changed in: linux (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: linux (Ubuntu Trusty)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2055686

Title:
  Drop ABI checks from kernel build

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  Drop the internal checks on the kernel ABI, module lists, et al.
  These checks are now applied after the fact by the workflow manager.
  This allows us to validate change after the builds complete so we do
  no waste builds which were correct but not annotated at upload time.

  NOTE: we still record the ABI data and publish it in linux-buildinfo
  files.  These are used to perform the external validation.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2055685] Re: Cranky update-dkms-versions rollout

[Roxana Nicolescu]

Many kernels have been cranked and their dkms mapping looks correct.

** Tags removed: verification-needed-focal-linux 
verification-needed-jammy-linux verification-needed-mantic-linux
** Tags added: verification-done-focal-linux verification-done-jammy-linux 
verification-done-mantic-linux

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2055685

Title:
  Cranky update-dkms-versions rollout

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]
  Having a common file for dkms-versions between main kernels and derivatives 
causes a lot of conflicts during rebase.
  Solution is to have a dkms-versions per kernels, under 
debian./dkms-version.

  While at it, instead of running ./update-dkms-version script, cranky
  update-dkms-versions was introduced.

  [Fix]
  This is needed only in the main kernels.
  1. remove update-dkms-version script
  2. rename debian/dkms-version with debian.master/dkms-versions
  3. Replace debian/dkms-versions references in debian scripts and rules with 
$(DEBIAN)/dkms-versions

  Note for derivatives: These changes will be inherited from the parent during 
cranky rebase.
  The only change to the cranky process is: instead of using 
./update-dkms-versions
  script, cranky-update-dkms-versions should be used

  [Test]
  Build test on cbd. No issue found.

  [Regression pottential]
  Owners have tried this last cycle in derivatives and no issues were found.
  We may see build failures due to wrong dkms versions, but it will be fixed 
along the way.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2056418] Re: Fix headphone mic detection issue on ALC897

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Mantic)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2056418

Title:
  Fix headphone mic detection issue on ALC897

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  Headphone mic is lost after resume from S3 or reboot with plugin.

  [Fix]
  Restore the headphone mic detect logic for ALC897 after lost power.

  [Test]
  Tested on hardware, the headphone mic appears as plugin after boot or
  resume from S3, and works fine.

  [Where problems could occur]
  It may break ALC897 sound input.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2056418/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2057808] Re: [LTS] cryptsetup-initramfs fails when kernel modules are compressed

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Jammy)
   Status: Incomplete => Won't Fix

** Changed in: linux (Ubuntu Jammy)
   Importance: Critical => Medium

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2057808

Title:
  [LTS] cryptsetup-initramfs fails when kernel modules are compressed

Status in cryptsetup package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in cryptsetup source package in Jammy:
  New
Status in linux source package in Jammy:
  Won't Fix

Bug description:
  This is the same cause as the Mantic bug "cryptsetup autopkgtest fails
  with zstd compressed kernel modules"

  https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2035120

  where hooks/cryptroot::add_modules() needs postfix wildcards after
  $glob.ko on 2 lines.

  It affects 22.04 LTS with recent kernel or local kernel built with
  CONFIG_MODULE_COMPRESS_*

  I think the fix needs cherry-picking into LTS release(s).

  https://salsa.debian.org/cryptsetup-
  team/cryptsetup/-/commit/8359ad85a541b76f388cdc28f549229e3d71e750

  At boot-time it results in the cryptic (pun intended) messages:

  device-mapper: table: 253:0 crypt: Error allocating crypto tfm (-ENOENT)
  device-mapper: ioctl: error adding target to table
  device-mapper: reload ioctl on luks_os (253:0) failed: No such file or 
directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2057808/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2057783] Re: hwmon-aaeon: probe of hwmon-aaeon.0 failed with error -22 - kernel 6.8 version

[Roxana Nicolescu]

** Also affects: linux (Ubuntu Noble)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2057783

Title:
  hwmon-aaeon: probe of hwmon-aaeon.0 failed with error -22 - kernel 6.8
  version

Status in linux package in Ubuntu:
  New
Status in linux source package in Noble:
  New

Bug description:
  hwmon-aaeon: probe of hwmon-aaeon.0 failed with error -22 - kernel 6.8
  version

  device is not recognized when using 6.8 kernel version


  
/sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/expensive
  
/sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/guid
  
/sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/instance_count
  
/sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/modalias
  
/sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/object_id
  
/sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/uevent

  
/sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/driver:
  97845ED0-4E6D-11DE-8A39-0800200C9A66
  bind
  module
  uevent
  unbind

  
/sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/gpio-aaeon.0:
  driver
  driver_override
  gpio
  gpiochip1
  modalias
  power
  subsystem
  uevent

  
/sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/hwmon-aaeon.0:
  driver_override
  modalias
  power
  subsystem
  uevent

  
/sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/leds-aaeon.0:
  driver
  driver_override
  leds
  modalias
  power
  subsystem
  uevent

  
/sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/power:
  async
  autosuspend_delay_ms
  control
  runtime_active_kids
  runtime_active_time
  runtime_enabled
  runtime_status
  runtime_suspended_time
  runtime_usage

  
/sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/subsystem:
  devices
  drivers
  drivers_autoprobe
  drivers_probe
  uevent

  
/sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/wdt-aaeon.0:
  driver_override
  modalias
  power
  subsystem
  uevent

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2056227] Re: KVM: arm64: softlockups in stage2_apply_range

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Jammy)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux (Ubuntu)
   Status: New => Invalid

** Changed in: linux (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Krister Johansen (kmjohansen)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2056227

Title:
  KVM: arm64: softlockups in stage2_apply_range

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  Tearing down kvm VMs on arm64 can cause softlockups to appear on console.  
When
  terminating VMs with > 100Gb of memory and 4k pages, the memory unmap times
  often exceed 20 seconds, which can trigger the softlockup detector.  Portions 
of
  the unmap path also have interrupts disabled while tlb invalidation 
instructions
  run, which can further contribute to latency problems.  My team has observed
  networking latency problems if the cpu where the teardown is occurring is also
  mapped to handle a NIC interrupt.

  Fortunately, a solution has been in place since Linux 6.1.  A small pair of
  patches modify stage2_apply_range to operate on smaller memory ranges before
  performing a cond_resched.  With these patches applied, softlockups are no
  longer observed when tearing down VMs with large amounts of memory. 

  Although I also submitted the patches to 5.15 LTS (link to LTS submission in
  "Backport" section), I'd appreciate it if Ubuntu were willing to take this
  submission in parallel since the impact has left us unable to utilize arm64 
for
  kvm until we can either migrate our hypervisors to hugepages, pick up this 
fix,
  or some combination of the two.

  [Backport]

  Backport the following fixes from linux 6.1: 

  3b5c082bbf KVM: arm64: Work out supported block level at compile time
  5994bc9e05 KVM: arm64: Limit stage2_apply_range() batch size to largest block

  The fix is in 5994bc9e05 and 3b5c082bbf is a dependency that was submitted as
  part of the series.  The original submission is here:

  https://lore.kernel.org/all/20221007234151.461779-1-oliver.up...@linux.dev/

  I've also submitted the patches to 5.15 LTS here:

  https://lore.kernel.org/stable/cover.1709665227.git.k...@templeofstupid.com/

  Both fixes cherry picked cleanly and there were no conflicts.

  [Test]
 
  Executed the test from 5994bc9e05 as well as my own run of kvm_page_table_test
  on a VM with 4k pages and a memory size > 100Gb.  Without the patches,
  softlockups were observed in both tests.  With the patches applied, the tests
  ran without incident.

  This was tested against both LTS 5.15.150 and linux-aws-5.15.0-1055.
   
  [Potential Regression]
 
  Regression potential is low.  These patches have been present in Linux since 
6.1
  and appear to have needed no further maintenance.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2056403] Re: Mantic update: upstream stable patchset 2024-03-07

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Mantic)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2056403

Title:
  Mantic update: upstream stable patchset 2024-03-07

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 upstream stable patchset 2024-03-07

  Ported from the following upstream stable releases:
  v6.1.75, v6.6.14

 from git://git.kernel.org/

  x86/lib: Fix overflow when counting digits
  x86/mce/inject: Clear test status value
  EDAC/thunderx: Fix possible out-of-bounds string access
  powerpc: add crtsavres.o to always-y instead of extra-y
  powerpc/44x: select I2C for CURRITUCK
  powerpc/pseries/memhp: Fix access beyond end of drmem array
  selftests/powerpc: Fix error handling in FPU/VMX preemption tests
  powerpc/powernv: Add a null pointer check to scom_debug_init_one()
  powerpc/powernv: Add a null pointer check in opal_event_init()
  powerpc/powernv: Add a null pointer check in opal_powercap_init()
  powerpc/imc-pmu: Add a null pointer check in update_events_in_group()
  spi: spi-zynqmp-gqspi: fix driver kconfig dependencies
  mtd: rawnand: Increment IFC_TIMEOUT_MSECS for nand controller response
  ACPI: video: check for error while searching for backlight device parent
  ACPI: LPIT: Avoid u32 multiplication overflow
  platform/x86/intel/vsec: Fix xa_alloc memory leak
  cpufreq: scmi: process the result of devm_of_clk_add_hw_provider()
  calipso: fix memory leak in netlbl_calipso_add_pass()
  efivarfs: force RO when remounting if SetVariable is not supported
  spi: sh-msiof: Enforce fixed DTDL for R-Car H3
  ACPI: LPSS: Fix the fractional clock divider flags
  ACPI: extlog: Clear Extended Error Log status when RAS_CEC handled the error
  kunit: debugfs: Fix unchecked dereference in debugfs_print_results()
  mtd: Fix gluebi NULL pointer dereference caused by ftl notifier
  selinux: Fix error priority for bind with AF_UNSPEC on PF_INET6 socket
  crypto: virtio - Handle dataq logic with tasklet
  crypto: sa2ul - Return crypto_aead_setkey to transfer the error
  crypto: ccp - fix memleak in ccp_init_dm_workarea
  crypto: af_alg - Disallow multiple in-flight AIO requests
  crypto: safexcel - Add error handling for dma_map_sg() calls
  crypto: sahara - remove FLAGS_NEW_KEY logic
  crypto: sahara - fix cbc selftest failure
  crypto: sahara - fix ahash selftest failure
  crypto: sahara - fix processing requests with cryptlen < sg->length
  crypto: sahara - fix error handling in sahara_hw_descriptor_create()
  crypto: hisilicon/qm - save capability registers in qm init process
  crypto: hisilicon/zip - add zip comp high perf mode configuration
  crypto: hisilicon/qm - add a function to set qm algs
  crypto: hisilicon/hpre - save capability registers in probe process
  crypto: hisilicon/sec2 - save capability registers in probe process
  crypto: hisilicon/zip - save capability registers in probe process
  pstore: ram_core: fix possible overflow in persistent_ram_init_ecc()
  erofs: fix memory leak on short-lived bounced pages
  fs: indicate request originates from old mount API
  gfs2: Fix kernel NULL pointer dereference in gfs2_rgrp_dump
  crypto: virtio - Wait for tasklet to complete on device remove
  crypto: sahara - avoid skcipher fallback code duplication
  crypto: sahara - handle zero-length aes requests
  crypto: sahara - fix ahash reqsize
  crypto: sahara - fix wait_for_completion_timeout() error handling
  crypto: sahara - improve error handling in sahara_sha_process()
  crypto: sahara - fix processing hash requests with req->nbytes < sg->length
  crypto: sahara - do not resize req->src when doing hash operations
  crypto: scomp - fix req->dst buffer overflow
  csky: fix arch_jump_label_transform_static override
  blocklayoutdriver: Fix reference leak of pnfs_device_node
  NFSv4.1/pnfs: Ensure we handle the error NFS4ERR_RETURNCONFLICT
  SUNRPC: fix _xprt_switch_find_current_entry logic
  pNFS: Fix the pnfs block driver's calculation of layoutget size
  wifi: plfxlc: check for allocation failure in plfxlc_usb_wreq_async()
  wifi: rtw88: fix RX filter in FIF_ALLMULTI flag
  bpf, lpm: Fix check prefixlen before walking trie
  bpf: Add crosstask check to __bpf_get_stack
  wifi: ath11k: Defer on rproc_get failure
  wifi: libertas: stop selecting wext
  ARM: dts: 

[Kernel-packages] [Bug 2051924] Re: Mantic update: upstream stable patchset 2024-02-01

[Roxana Nicolescu]

Commit "eventfs: Do not allow NULL parent to eventfs_start_creating()" had to 
be dropped.
This introduced a warning: "WARNING: CPU: 17 PID: 1 at fs/tracefs/inode.c:408 
start_creating+0xe9/0x110" that can be seen during boot testing. The check 
itself would not be an issue, but the commit was removes the following in 
start_creating:
```
-   /* If the parent is not specified, we create it in the root.


  
-* We need the root dentry to do this, which is in the super


  
-* block. A pointer to that is in the struct vfsmount that we   


  
-* have around. 


  
-*/ 


  
-   if (!parent)


  
-   parent = tracefs_mount->mnt_root;   


  
-  
```
This is used a lot for entries that are created in the root directory, 
therefore these entries cannot be created anymore.

```
root@mantic:/home/ubuntu# ll /sys/kernel/tracing/
total 0
drwx--  2 root root 0 Mar  7 14:29 ./
drwxr-xr-x 16 root root 0 Mar  7 14:29 ../
```

I would keep the warning entry, but this would create a bit of confusion
because we'll deviate from upstream. Therefore, I'll drop the commit

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2051924

Title:
  Mantic update: upstream stable patchset 2024-02-01

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2024-02-01

  Ported from the following upstream stable releases:
  v6.1.69, v6.6.8

     from git://git.kernel.org/

  r8152: add vendor/device ID pair for D-Link DUB-E250
  r8152: add vendor/device ID pair for ASUS USB-C2500
  ext4: fix warning in ext4_dio_write_end_io()
  ksmbd: fix memory leak in smb2_lock()
  afs: Fix refcount underflow from error handling race
  HID: lenovo: Restrict detection of patched firmware only to USB cptkbd
  net/mlx5e: Fix possible deadlock on mlx5e_tx_timeout_work
  net: ipv6: support reporting otherwise unknown prefix flags in RTM_NEWPREFIX
  qca_debug: Prevent crash on TX ring changes
  qca_debug: Fix ethtool -G iface tx behavior
  qca_spi: Fix reset behavior
  bnxt_en: Fix wrong return value check in bnxt_close_nic()
  bnxt_en: Fix HWTSTAMP_FILTER_ALL packet timestamp logic
  atm: solos-pci: Fix potential deadlock on _queue_lock
  atm: solos-pci: Fix potential deadlock on _queue_lock
  net: fec: correct queue selection
  octeontx2-af: fix a use-after-free in rvu_nix_register_reporters
  octeontx2-pf: Fix promisc mcam entry action
  octeontx2-af: Update RSS algorithm index
  atm: Fix Use-After-Free in do_vcc_ioctl
  iavf: Introduce new state machines for flow director
  iavf: Handle ntuple on/off based on new state machines for flow director
  qed: Fix a potential use-after-free in qed_cxt_tables_alloc
  net: Remove acked SYN flag from packet in the transmit queue correctly
  net: ena: Destroy correct number of xdp queues upon failure
  net: ena: Fix 

[Kernel-packages] [Bug 2055686] Re: Drop ABI checks from kernel build

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Mantic)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2055686

Title:
  Drop ABI checks from kernel build

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  Drop the internal checks on the kernel ABI, module lists, et al.
  These checks are now applied after the fact by the workflow manager.
  This allows us to validate change after the builds complete so we do
  no waste builds which were correct but not annotated at upload time.

  NOTE: we still record the ABI data and publish it in linux-buildinfo
  files.  These are used to perform the external validation.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2055685] Re: Cranky update-dkms-versions rollout

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Mantic)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2055685

Title:
  Cranky update-dkms-versions rollout

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]
  Having a common file for dkms-versions between main kernels and derivatives 
causes a lot of conflicts during rebase.
  Solution is to have a dkms-versions per kernels, under 
debian./dkms-version.

  While at it, instead of running ./update-dkms-version script, cranky
  update-dkms-versions was introduced.

  [Fix]
  This is needed only in the main kernels.
  1. remove update-dkms-version script
  2. rename debian/dkms-version with debian.master/dkms-versions
  3. Replace debian/dkms-versions references in debian scripts and rules with 
$(DEBIAN)/dkms-versions

  Note for derivatives: These changes will be inherited from the parent during 
cranky rebase.
  The only change to the cranky process is: instead of using 
./update-dkms-versions
  script, cranky-update-dkms-versions should be used

  [Test]
  Build test on cbd. No issue found.

  [Regression pottential]
  Owners have tried this last cycle in derivatives and no issues were found.
  We may see build failures due to wrong dkms versions, but it will be fixed 
along the way.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2044131] Re: i915 regression introduced with 5.5 kernel

[Roxana Nicolescu]

I am gonna mark this as verified. If you find an issue later, please
submit another bug.

** Tags removed: verification-needed-jammy-linux 
verification-needed-jammy-linux-ibm-gt-fips verification-needed-mantic-linux
** Tags added: verification-done-jammy-linux 
verification-done-jammy-linux-ibm-gt-fips verification-done-mantic-linux

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2044131

Title:
  i915 regression introduced with 5.5 kernel

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.15 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-hwe-5.15 source package in Focal:
  Triaged
Status in linux source package in Jammy:
  Fix Committed
Status in linux-hwe-5.15 source package in Jammy:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-hwe-5.15 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Fix Released
Status in linux-hwe-5.15 source package in Noble:
  Invalid

Bug description:
  [ Impact ]
  Commit 8f4b1068e7fc3df1a77ac8151767e56b208cc87f introduced some timing checks 
which have been proven invalid for at least some hardware setups. A user trying 
to run Focal with HWE 5.15 kernel is not able to get any video output.
  After going through bisection between 5.4 and 5.5 this commit was identified. 
Reverting it on top of Focal HWE kernel fixes the issue.

  The issue has been addressed upstream in DRM tree
  (20c2dbff342aec13bf93c2f6c951da198916a455) and has been merge into
  linux-next (e0ef2daa8ca8ce4dbc2fd0959e383b753a87fd7d).

  dmesg and lspci from the affected configuration are attached to this
  bug.

  [ Test Plan ]
  1. Boot the affected hardware with Ubuntu desktop running kernel v5.5 or 
higher.
  2. Wait until boot finishes and see the blank screen.

  Actual result: there is no video output visible.
  Expected result: normal boot process should be visible (e.g. splash), then 
GUI should appear.

  [ Where problem could occur ]
  This bug was a result of assumptions in the checks that turned out to be not 
valid for some hardware. The checks were removed from global intel_mode_valid 
function and moved into connector specific .mode_valid() hooks, entirely 
skiping BXT/GLK DSI connectors.

  This should keep the checks where appropriate and skip for hardware
  that does not comply to them.

  [ Other info ]

  Original bug description:

  There is a regression preventing a user to upgrade from 5.4 kernel to 
anything that's higher than 5.5. When using such kernel the image orientation 
is wrong (rotated by 90°C). Also the kernel log contains:
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Unknown revid 0x06
  wrz 15 09:19:49 desktop kernel: rtw_8821ce :01:00.0: Firmware version 
24.8.0, H2C version 12
  wrz 15 09:19:49 desktop kernel: Console: switching to colour dummy device 
80x25
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: deactivate vga 
console
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] couldn't get memory 
information
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: changed VGA 
decodes: olddecodes=io+mem,decodes=io+mem:o>
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Finished loading DMC 
firmware i915/glk_dmc_ver1_04.bin (v>
  wrz 15 09:19:49 desktop kernel: 

  wrz 15 09:19:49 desktop kernel: UBSAN: array-index-out-of-bounds in 
/build/linux-hwe-5.15-DZkSuT/linux-hwe-5.15-5.>
  wrz 15 09:19:49 desktop kernel: index 5 is out of range for type 'u32 [5]'

  (full stack trace attached)

  The video hardware in use is:
  00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 605 
[8086:3185] (rev 06) (prog-if 00 [VGA controller])
  (...)
  Kernel driver in use: i915
  Kernel modules: i915

  The user wanted to upgrade from bionic to focal with HWE kernel (they
  needed it due to some networking hardware they wanted to have
  supported by the newer kernel).

  The user was testing mainline stable kernels and noticed that the last
  working kernel was the 5.4 series, while anything starting from 5.5
  and above is BROKEN (symptoms as described in the first paragraph
  above).

  Together with the user we have run a bisection between v5.4 and v5.5 on the 
upstream stable kernel and we were able to identify the first broken commit to 
be:
  8f4b1068e7fc3df1a77ac8151767e56b208cc87f drm/i915: Check some transcoder 
timing minimum limits

  To confirm I have reverted this change on top of the HWE kernel for
  focal and the user have confirmed that this resolved the issue (test
  build available at ppa:dgadomski/kernel-sf368743).

  I am not fully sure what the purpose of this patch was, but I assume
  the regression was not intended and the 

[Kernel-packages] [Bug 2049027] Re: The display becomes frozen after some time when a HDMI device is connected.

[Roxana Nicolescu]

Thanks for your help!

** Tags removed: verification-needed-jammy-linux-starfive-6.5 
verification-needed-mantic-linux verification-needed-mantic-linux-lowlatency
** Tags added: verification-done-jammy-linux-starfive-6.5 
verification-done-mantic-linux verification-done-mantic-linux-lowlatency

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2049027

Title:
  The display becomes frozen after some time when a HDMI device is
  connected.

Status in linux package in Ubuntu:
  Invalid
Status in linux-signed-hwe-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-signed-hwe-6.5 source package in Mantic:
  Invalid

Bug description:
  
  SRU Justification:

  [Impact]

  Multiple users have reported frozen displays when external HDMI device
  is connected on systems with intel graphics chipsets.

  [Fix]

  * backport 49e0a85ec344: "drm/i915/dmc: Don't enable any pipe DMC events"
  from 6.6.9

  [Test Plan]

  * Tested on Intel TigerLake with iris Xe Graphics and no issues so far.
  It seems it affects mostly Alder Lake though, but at least it does not
  cause any issues on other models.
  * It has also been tested upstream 
https://gitlab.freedesktop.org/drm/intel/-/issues/8685

  [Where problems could occur]
  * We could see issues on systems with Intel Graphics when HDMI devices
  are connected during power state changes.

  
  Old description:
  It is exactly this bug: https://gitlab.freedesktop.org/drm/intel/-/issues/8685

  It was fixed with that kernel commit:

  commit 648d7be8ecf47b0556e32550145c70db153b16fb
  Author: Ville Syrjälä 
  Date:   Mon Dec 11 23:37:47 2023 +0200

  drm/i915/dmc: Don't enable any pipe DMC events

  
https://lore.kernel.org/stable/20231211213750.27109-2-ville.syrj...@linux.intel.com/

  which was picked for 6.6.9.

  I'd like to ask whether it is possible to apply that patch to the
  current Ubuntu kernel?

  Best
  Sönke

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 11 13:11:59 2024
  InstallationDate: Installed on 2023-03-01 (316 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2049027] Re: The display becomes frozen after some time when a HDMI device is connected.

[Roxana Nicolescu]

Good news. I'll mark this verified.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2049027

Title:
  The display becomes frozen after some time when a HDMI device is
  connected.

Status in linux package in Ubuntu:
  Invalid
Status in linux-signed-hwe-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-signed-hwe-6.5 source package in Mantic:
  Invalid

Bug description:
  
  SRU Justification:

  [Impact]

  Multiple users have reported frozen displays when external HDMI device
  is connected on systems with intel graphics chipsets.

  [Fix]

  * backport 49e0a85ec344: "drm/i915/dmc: Don't enable any pipe DMC events"
  from 6.6.9

  [Test Plan]

  * Tested on Intel TigerLake with iris Xe Graphics and no issues so far.
  It seems it affects mostly Alder Lake though, but at least it does not
  cause any issues on other models.
  * It has also been tested upstream 
https://gitlab.freedesktop.org/drm/intel/-/issues/8685

  [Where problems could occur]
  * We could see issues on systems with Intel Graphics when HDMI devices
  are connected during power state changes.

  
  Old description:
  It is exactly this bug: https://gitlab.freedesktop.org/drm/intel/-/issues/8685

  It was fixed with that kernel commit:

  commit 648d7be8ecf47b0556e32550145c70db153b16fb
  Author: Ville Syrjälä 
  Date:   Mon Dec 11 23:37:47 2023 +0200

  drm/i915/dmc: Don't enable any pipe DMC events

  
https://lore.kernel.org/stable/20231211213750.27109-2-ville.syrj...@linux.intel.com/

  which was picked for 6.6.9.

  I'd like to ask whether it is possible to apply that patch to the
  current Ubuntu kernel?

  Best
  Sönke

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 11 13:11:59 2024
  InstallationDate: Installed on 2023-03-01 (316 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2055685] Re: Cranky update-dkms-versions rollout

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Roxana Nicolescu (roxanan)

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Roxana Nicolescu (roxanan)

** Changed in: linux (Ubuntu Mantic)
 Assignee: (unassigned) => Roxana Nicolescu (roxanan)

** Changed in: linux (Ubuntu Focal)
   Importance: Undecided => Critical

** Changed in: linux (Ubuntu Focal)
   Importance: Critical => High

** Changed in: linux (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Mantic)
   Importance: Undecided => High

** Changed in: linux (Ubuntu)
   Status: New => Invalid

** Changed in: linux (Ubuntu Focal)
   Status: New => In Progress

** Changed in: linux (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux (Ubuntu Mantic)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2055685

Title:
  Cranky update-dkms-versions rollout

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in linux source package in Mantic:
  In Progress

Bug description:
  SRU Justification

  [Impact]
  Having a common file for dkms-versions between main kernels and derivatives 
causes a lot of conflicts during rebase.
  Solution is to have a dkms-versions per kernels, under 
debian./dkms-version.

  While at it, instead of running ./update-dkms-version script, cranky
  update-dkms-versions was introduced.

  [Fix]
  This is needed only in the main kernels.
  1. remove update-dkms-version script
  2. rename debian/dkms-version with debian.master/dkms-versions
  3. Replace debian/dkms-versions references in debian scripts and rules with 
$(DEBIAN)/dkms-versions

  Note for derivatives: These changes will be inherited from the parent during 
cranky rebase.
  The only change to the cranky process is: instead of using 
./update-dkms-versions
  script, cranky-update-dkms-versions should be used

  [Test]
  Build test on cbd. No issue found.

  [Regression pottential]
  Owners have tried this last cycle in derivatives and no issues were found.
  We may see build failures due to wrong dkms versions, but it will be fixed 
along the way.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2055685] Re: Replace debian/dkms-versions with debian./dkms-versions

[Roxana Nicolescu]

** Description changed:

+ SRU Justification
+ 
+ [Impact]
  Having a common file for dkms-versions between main kernels and derivatives 
causes a lot of conflicts during rebase.
  Solution is to have a dkms-versions per kernels, under 
debian./dkms-version.
  
  While at it, instead of running ./update-dkms-version script, cranky
  update-dkms-versions was introduced.
+ 
+ [Fix]
+ This is needed only in the main kernels.
+ 1. remove update-dkms-version script
+ 2. rename debian/dkms-version with debian.master/dkms-versions
+ 3. Replace debian/dkms-versions references in debian scripts and rules with 
$(DEBIAN)/dkms-versions
+ 
+ Note for derivatives: These changes will be inherited from the parent during 
cranky rebase.
+ The only change to the cranky process is: instead of using 
./update-dkms-versions
+ script, cranky-update-dkms-versions should be used
+ 
+ [Test]
+ Build test on cbd. No issue found.
+ 
+ [Regression pottential]
+ Owners have tried this last cycle in derivatives and no issues were found.
+ We may see build failures due to wrong dkms versions, but it will be fixed 
along the way.

** Summary changed:

- Replace debian/dkms-versions with debian./dkms-versions
+ Cranky update-dkms-versions rollout

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2055685

Title:
  Cranky update-dkms-versions rollout

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in linux source package in Mantic:
  In Progress

Bug description:
  SRU Justification

  [Impact]
  Having a common file for dkms-versions between main kernels and derivatives 
causes a lot of conflicts during rebase.
  Solution is to have a dkms-versions per kernels, under 
debian./dkms-version.

  While at it, instead of running ./update-dkms-version script, cranky
  update-dkms-versions was introduced.

  [Fix]
  This is needed only in the main kernels.
  1. remove update-dkms-version script
  2. rename debian/dkms-version with debian.master/dkms-versions
  3. Replace debian/dkms-versions references in debian scripts and rules with 
$(DEBIAN)/dkms-versions

  Note for derivatives: These changes will be inherited from the parent during 
cranky rebase.
  The only change to the cranky process is: instead of using 
./update-dkms-versions
  script, cranky-update-dkms-versions should be used

  [Test]
  Build test on cbd. No issue found.

  [Regression pottential]
  Owners have tried this last cycle in derivatives and no issues were found.
  We may see build failures due to wrong dkms versions, but it will be fixed 
along the way.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2049689] Re: partprobe is broken on empty loopback device

[Roxana Nicolescu]

On Monday we're supposed to release this. This feedback would have been crucial 
1-2 weeks before.
Plus, we already started the next releases..

I'll try to prioritize this, but it's very late to be included in the
next releases (I'll probably respin)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2049689

Title:
  partprobe is broken on empty loopback device

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

  * BLKPG_DEL_PARTITION on an empty loopback device used to return ENXIO
  but now returns EINVAL, breaking partprobe due to commit
  "block: don't add or resize partition on the disk with GENHD_FL_NO_PART"
  introduced in mantic 6.5.0-17 and jammy 5.15.0-94.

  [Fix]

  * backport commit
  "block: Move checking GENHD_FL_NO_PART to bdev_add_partition()"

  [Test Plan]

  * dd if=/dev/zero of=/tmp/foo bs=1M count=50
  * partprobe $(losetup --find --show /tmp/foo)
  Before the fix this fails.
  After the fix it should work.

  [Where problems could occur]

  * We may see issues on disk partitions operations.

  
  Old description:
  This is with the kernel from jammy-proposed (linux-image-5.15.0-94-generic 
5.15.0-94.104).

  Do this:

  # dd if=/dev/zero of=/tmp/file bs=1M count=50
  # partprobe "$(losetup --show --find /tmp/file)"

  Notice this very odd error message:

  Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
  16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32,
  33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49,
  50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on
  /dev/loop2 have been written, but we have been unable to inform the
  kernel of the change, probably because it/they are in use.  As a
  result, the old partition(s) will remain in use.  You should reboot
  now before making further changes.

  That's a result of an ioctl changing its error code in an incompatible
  way between kernel versions 5.15.0.91.88 and 5.15.0.94.91, confusing
  partprobe.

  5.15.0.91.88:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 ENXIO (No such device or 
address)

  5.15.0.94.91:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 EINVAL (Invalid argument)

  This is a userspace API break which impacts GNU parted and util-linux
  (as confirmed by the util-linux maintainer).

  This issue was discovered as part of Cockpit CI here:
  https://github.com/cockpit-project/bots/pull/5793

  This issue is being discussed on LKML here (with a patch likely to
  land soon): https://lkml.org/lkml/2024/1/15/147

  lsb_release -rd:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2055685] [NEW] Replace debian/dkms-versions with debian./dkms-versions

[Roxana Nicolescu]

Public bug reported:

Having a common file for dkms-versions between main kernels and derivatives 
causes a lot of conflicts during rebase.
Solution is to have a dkms-versions per kernels, under 
debian./dkms-version.

While at it, instead of running ./update-dkms-version script, cranky
update-dkms-versions was introduced.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Mantic)
 Importance: Undecided
 Status: New

** Also affects: linux (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2055685

Title:
  Replace debian/dkms-versions with debian./dkms-versions

Status in linux package in Ubuntu:
  New
Status in linux source package in Focal:
  New
Status in linux source package in Jammy:
  New
Status in linux source package in Mantic:
  New

Bug description:
  Having a common file for dkms-versions between main kernels and derivatives 
causes a lot of conflicts during rebase.
  Solution is to have a dkms-versions per kernels, under 
debian./dkms-version.

  While at it, instead of running ./update-dkms-version script, cranky
  update-dkms-versions was introduced.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2054809] Re: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules

[Roxana Nicolescu]

** Also affects: linux (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux (Ubuntu Mantic)
   Status: New => In Progress

** Changed in: linux (Ubuntu Noble)
   Status: New => In Progress

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Daan De Meyer (daandemeyer)

** Changed in: linux (Ubuntu Mantic)
 Assignee: (unassigned) => Daan De Meyer (daandemeyer)

** Changed in: linux (Ubuntu Jammy)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Mantic)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Noble)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2054809

Title:
  linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from
  linux-modules-extra to linux-modules

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in linux source package in Mantic:
  In Progress
Status in linux source package in Noble:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  The erofs.ko module (CONFIG_EROFS) is currently shipped in linux-
  modules-extra. This makes it hard to pull in via the linux-virtual
  package, it can only come from the linux-generic one that also pulls
  in the firmware and everything else needed for baremetal, and that
  serves no purpose in a qemu VM. This stops VMs using these kernels
  from using the erofs filesystem. Erofs is a modern alternative to
  squashfs that supports more features such as ACLs. The following LPC
  presentation has more details on erofs and its advantages over
  squashfs: https://youtu.be/jt-hp_LtSBc.

  A user launching a VM using the linux-virtual kernel image is not able
  to mount erofs filesystems due to the lack of this kconfig. We make
  extensive use of erofs in systemd's upstream CI, which is running on
  Github Actions, which uses Jammy, so it would be great to have this
  backported.

  [Fix]

  Please consider moving this module to linux-modules.

  These are already enabled in the 'main' kernel config, and in other
  distros. In Debian/Archlinux/Fedora it is a (core) module that is
  built by default.

  To verify this works, it is sufficient to create an erofs filesystem
  with mkfs.erofs and verify that it can be mounted:

  $ mkdir sources
  $ echo abcde > sources/file
  $ mkfs.erofs erofs sources
  $ mount erofs mnt --mkdir
  $ ls mnt
  file

  Without this module installed and loaded, the mount will fail. Once
  enabled, it will succeed.

  [Test]

  1. pull built linux-modules packages for architectures with do_extras_package
 set to true;
  2. extract the deb and check if erofs kernel module file exists:

 $ dpkg-deb -R linux-modules-*.deb .
 $ find . -name erofs.ko\*

  [Regression Potential]

  Moving a module from a less-common to a more-common package should not
  have any negative side effects. The main effect will be a little more
  disk space used by the more common package, whether the module is in
  use or not. There will also be more functionality available in the
  default installation, which means a slightly increased surface and
  possibility of new bugs in case it gets used.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2049027] Re: The display becomes frozen after some time when a HDMI device is connected.

[Roxana Nicolescu]

Yes, both contain the fix. We run two cycles in parallel (one for security that 
releases earlier nd contains critical fixes (mostly CVEs) and then the sru 
cycle that is released 2 weeks after.
This seemed critical and we decided to include in the security cycle so it will 
reach end users 2 weeks earlier than usual.
That's why I said it is included in both versions.
Now, please do test  `6.5.0.21.21~22.04.11`, that has reached -updates indeed 
in the meantime so we can mark this as verified.

Note that .11 is the version of the meta package, the actual kernel
package is .1

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2049027

Title:
  The display becomes frozen after some time when a HDMI device is
  connected.

Status in linux package in Ubuntu:
  Invalid
Status in linux-signed-hwe-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-signed-hwe-6.5 source package in Mantic:
  Invalid

Bug description:
  
  SRU Justification:

  [Impact]

  Multiple users have reported frozen displays when external HDMI device
  is connected on systems with intel graphics chipsets.

  [Fix]

  * backport 49e0a85ec344: "drm/i915/dmc: Don't enable any pipe DMC events"
  from 6.6.9

  [Test Plan]

  * Tested on Intel TigerLake with iris Xe Graphics and no issues so far.
  It seems it affects mostly Alder Lake though, but at least it does not
  cause any issues on other models.
  * It has also been tested upstream 
https://gitlab.freedesktop.org/drm/intel/-/issues/8685

  [Where problems could occur]
  * We could see issues on systems with Intel Graphics when HDMI devices
  are connected during power state changes.

  
  Old description:
  It is exactly this bug: https://gitlab.freedesktop.org/drm/intel/-/issues/8685

  It was fixed with that kernel commit:

  commit 648d7be8ecf47b0556e32550145c70db153b16fb
  Author: Ville Syrjälä 
  Date:   Mon Dec 11 23:37:47 2023 +0200

  drm/i915/dmc: Don't enable any pipe DMC events

  
https://lore.kernel.org/stable/20231211213750.27109-2-ville.syrj...@linux.intel.com/

  which was picked for 6.6.9.

  I'd like to ask whether it is possible to apply that patch to the
  current Ubuntu kernel?

  Best
  Sönke

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 11 13:11:59 2024
  InstallationDate: Installed on 2023-03-01 (316 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

[Roxana Nicolescu]

Hi Robert! Thanks for testing this on jammy. I marked the tag as verified 
('verification-done-jammy-linux') to reflect that.
Could you share the results from mantic? we need to release this next week and 
we need a confirmation this works as expected.
If your test looks fine, please remove 'verification-needed-mantic-linux' tag 
and add 'verification-done-mantic-linux'.
Thanks! 

** Tags removed: verification-needed-jammy-linux
** Tags added: verification-done-jammy-linux

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2036239

Title:
  Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  In Progress

Bug description:
  [Impact]
   * Issue is causing transmit hang on E810 ports with bonding enabled.
   * Based on the provided logs, TX hang can last for even a couple of 
minutes, but in most scenarios, the network will be recovered after the ice 
driver performs a PF reset (TX hang handler routine).
   * Originally, the issue was observed during Tempest tests on a newly 
created OpenStack cluster, resulting in a lack of certification.
  
  [Fix]
  * Initially, a workaround has been proposed by Intel engineers to disable 
LAG initialization [1].
This change has been tested in an environment where reproduction is 
easily achieved.
After multiple iterations, no reproduction has been observed.
  * Shortly after, Intel proposed a patch [2] to disable LAG initialization 
if NVM does not expose proper capabilities.
  
  [Test Plan]
  * To reproduce the issue, over a 20-node cluster was used with Ceph-based 
storage. The problem could sometimes manifest while deploying a cluster or 
after the cluster was already deployed during the Tempest test run.
  * The issue could appear on a random node, making reproduction hard to 
achieve.
  * Multiple stress tests on single host with similar configuration did not 
trigger a reproduction.
  
  [Where problems could occur]
  * All ice drivers with ice_lag_event_handler registered can expose the 
issue. This handler is not implemented in 20.04
  * CVL4.2 and older NVM images for E810 does not expose SRIOV LAG 
capabilities (CVL4.3 wasn't checked) meaning at some point NVM with this 
capability will be released.
Although potentialy issue is caused by using features without proper FW 
support [2], we want to take a closer look once NVMs with proper support are 
introduced.

  [1] - 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/40
  [2] - 
https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20231211/038588.html
 4d50fcdc2476eef94c14c6761073af5667bb43b6

  [Other Info]
  * Issue could be reproduced on custom 6.2 jammy-hwe kernel with ice 
driver backported from mainline kernel from before patch [2] was added.
  * Original description of the case below:
  
  

  I'm having issues with an Intel E810-XXV card on a Dell server under
  Ubuntu Jammy.

  Details:

  - hardware --> a1:00.0 Ethernet controller: Intel Corporation Ethernet
  Controller E810-XXV for SFP (rev 02)

  - tested with both GA and HWE kernels (`5.15.0-83-generic #92` and
  `6.2.0-32-generic #32~22.04.1-Ubuntu`) with the same results.

  - using a bond over the two ports of the same card, at 25Gbps to two
  different switches, bond is using LACP with hash layer3+4 and fast
  timeout. But I believe the bug is not directly related to bonding as
  the problem seems to be in the interface.

  - machine installed by maas. No issues during installation, but at
  that time bond is not formed yet, later when linux is booted, the bond
  is formed and works without issues for a while

  - it works for about 2 to 3 hours fine, then the issue starts (may or
  may not be related to network load, but it seems that it is triggered
  by some tests that I run after openstack finishes installing)

  - one of the legs of the bond freezes and everything that would go to
  that lag is discarded, in and out, ping to random external hosts start
  losing every second packet

  - after some time you can see on the kernel log messages about "NETDEV
  WATCHDOG: enp161s0f0 (ice): transmit queue 166 timed out" and a stack
  trace

  - the switch does log that the bond is flapping
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 12 20:05 seq
   crw-rw 1 root audio 116, 33 Sep 12 20:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: 

[Kernel-packages] [Bug 2054567] Re: Fix bpf selftests build failure after v5.15.139 update

[Roxana Nicolescu]

** Description changed:

  Sru justification
  
  [Impact]
- Upstream v5.15.139  (#lp2049432) brought commit "selftests/bpf: Test tail 
call counting with bpf2bpf and data on stack" that affects one of the bpf 
kselftests.
+ Upstream v5.15.139  (#lp2049432) brought commit "selftests/bpf: Test tail 
call counting with bpf2bpf and data on stack" that affects one of the bpf 
kselftests
+ (tailcall_bpf2bpf6).
  because LIBBPF_OPTS macro does not exists, it does not compile. Error below.
  
  [Fix]
  Initially, I thought cherry-pick commit "libbpf: Rename DECLARE_LIBBPF_OPTS 
into LIBBPF_OPTS" would be the best, but upstream stable just reverted the 
commit
  that broke it.
  Commit  62900d358c48 "Revert "selftests/bpf: Test tail call counting with 
bpf2bpf and data on stack"" will be cherry picked.
  
  [Test]
  This should be solved soon, but compileselftests debian rule does not compile 
bpf selftests.
  I tested it by using our regression testing tooling, but same results can be 
achieved by running:
  $ make  -C linux/tools/testing/selftests TARGETS=bpf SKIP_TARGETS= clean all 
KDIR=/usr/src/linux-headers-5.15.0--generic
  from the linux tree directory
  
  Without the fix, it fails to compile:
    
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:
 In function ‘test_tailcall_bpf2bpf_6’:
    
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:9:
 warning: implicit declaration of function ‘LIBBPF_OPTS’; did you mean 
‘LIBBPF_API’? [-Wimplicit-function-declaration]
  822 | LIBBPF_OPTS(bpf_test_run_opts, topts,
  | ^~~
  | LIBBPF_API
    
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:21:
 error: ‘bpf_test_run_opts’ undeclared (first use in this function)
  822 | LIBBPF_OPTS(bpf_test_run_opts, topts,
  | ^
    
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:21:
 note: each undeclared identifier is reported only once for each function it 
appears in
    
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:40:
 error: ‘topts’ undeclared (first use in this function)
  822 | LIBBPF_OPTS(bpf_test_run_opts, topts,
  |^
    
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:823:17:
 error: expected expression before ‘.’ token
  823 | .data_in = _v4,
  | ^
    make[1]: *** [Makefile:471: 
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tailcalls.test.o]
 Error 1
    make: *** [Makefile:172: all] Error 2
  
  With the fix, it compiles.
  
  [Regression potential]
  The only place this is being used is selftests, so the risk is very low.

** Description changed:

- Sru justification
+ SRU justification
  
  [Impact]
- Upstream v5.15.139  (#lp2049432) brought commit "selftests/bpf: Test tail 
call counting with bpf2bpf and data on stack" that affects one of the bpf 
kselftests
- (tailcall_bpf2bpf6).
+ Upstream v5.15.139 (#lp2049432) brought commit
+ "selftests/bpf: Test tail call counting with bpf2bpf and data on stack"
+ that affects one of the bpf kselftests (tailcall_bpf2bpf6).
  because LIBBPF_OPTS macro does not exists, it does not compile. Error below.
  
  [Fix]
- Initially, I thought cherry-pick commit "libbpf: Rename DECLARE_LIBBPF_OPTS 
into LIBBPF_OPTS" would be the best, but upstream stable just reverted the 
commit
- that broke it.
- Commit  62900d358c48 "Revert "selftests/bpf: Test tail call counting with 
bpf2bpf and data on stack"" will be cherry picked.
+ Initially, I thought cherry-picking commit
+ "libbpf: Rename DECLARE_LIBBPF_OPTS into LIBBPF_OPTS" would be the best,
+ but upstream stable just reverted the commit that broke it. Hence the fix
+ consists of cherry-picking this commit from stable upstream 5.15.49:
+ Commit 62900d358c48 (Revert "selftests/bpf: Test tail call counting with 
bpf2bpf and data on stack")
  
  [Test]
- This should be solved soon, but compileselftests debian rule does not compile 
bpf selftests.
- I tested it by using our regression testing tooling, but same results can be 
achieved by running:
- $ make  -C linux/tools/testing/selftests TARGETS=bpf SKIP_TARGETS= clean all 
KDIR=/usr/src/linux-headers-5.15.0--generic
+ This should be solved soon, but compileselftests debian rule does not
+ compile bpf selftests.
+ I tested it by using our regression testing tooling, but same results can
+ be achieved by running:
+ $ make -C linux/tools/testing/selftests TARGETS=bpf SKIP_TARGETS= clean all 
KDIR=/usr/src/linux-headers-5.15.0--generic
  from the linux tree directory
  
  Without the fix, it fails to compile:
-   

[Kernel-packages] [Bug 2054809] Re: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules

[Roxana Nicolescu]

hi,

In which kernel series you're interested in?
Focal, jammy, mantic, noble?

Please update the ticket to reflect it.
Click on 'Target to series'

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2054809

Title:
  linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from
  linux-modules-extra to linux-modules

Status in linux package in Ubuntu:
  New

Bug description:
  SRU Justification

  [Impact]

  The erofs.ko module (CONFIG_EROFS) is currently shipped in linux-
  modules-extra. This makes it hard to pull in via the linux-virtual
  package, it can only come from the linux-generic one that also pulls
  in the firmware and everything else needed for baremetal, and that
  serves no purpose in a qemu VM. This stops VMs using these kernels
  from using the erofs filesystem. Erofs is a modern alternative to
  squashfs that supports more features such as ACLs. The following LPC
  presentation has more details on erofs and its advantages over
  squashfs: https://youtu.be/jt-hp_LtSBc.

  A user launching a VM using the linux-virtual kernel image is not able
  to mount erofs filesystems due to the lack of this kconfig. We make
  extensive use of erofs in systemd's upstream CI, which is running on
  Github Actions, which uses Jammy, so it would be great to have this
  backported.

  [Fix]

  Please consider moving this module to linux-modules.

  These are already enabled in the 'main' kernel config, and in other
  distros. In Debian/Archlinux/Fedora it is a (core) module that is
  built by default.

  To verify this works, it is sufficient to create an erofs filesystem
  with mkfs.erofs and verify that it can be mounted:

  $ mkdir sources
  $ echo abcde > sources/file
  $ mkfs.erofs erofs sources
  $ mount erofs mnt --mkdir
  $ ls mnt
  file

  Without this module installed and loaded, the mount will fail. Once
  enabled, it will succeed.

  [Test]

  1. pull built linux-modules packages for architectures with do_extras_package
 set to true;
  2. extract the deb and check if erofs kernel module file exists:

 $ dpkg-deb -R linux-modules-*.deb .
 $ find . -name erofs.ko\*

  [Regression Potential]

  Moving a module from a less-common to a more-common package should not
  have any negative side effects. The main effect will be a little more
  disk space used by the more common package, whether the module is in
  use or not. There will also be more functionality available in the
  default installation, which means a slightly increased surface and
  possibility of new bugs in case it gets used.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2054567] Re: Fix bpf selftests build failure after v5.15.139 update

[Roxana Nicolescu]

I missed that the test itself was removed in v5.15.149. We should do the same.
Considering the last one applied to our tree is 140 (I think), I'll push this 
sooner.

** Description changed:

  Sru justification
  
  [Impact]
  Upstream v5.15.139  (#lp2049432) brought commit "selftests/bpf: Test tail 
call counting with bpf2bpf and data on stack" that affects one of the bpf 
kselftests.
  because LIBBPF_OPTS macro does not exists, it does not compile. Error below.
  
  [Fix]
- Cherry-pick commit "libbpf: Rename DECLARE_LIBBPF_OPTS into LIBBPF_OPTS"
+ Initially, I thought cherry-pick commit "libbpf: Rename DECLARE_LIBBPF_OPTS 
into LIBBPF_OPTS" would be the best, but upstream stable just reverted the 
commit
+ that broke it.
+ Commit  62900d358c48 "Revert "selftests/bpf: Test tail call counting with 
bpf2bpf and data on stack"" will be cherry picked.
  
  [Test]
  This should be solved soon, but compileselftests debian rule does not compile 
bpf selftests.
  I tested it by using our regression testing tooling, but same results can be 
achieved by running:
  $ make  -C linux/tools/testing/selftests TARGETS=bpf SKIP_TARGETS= clean all 
KDIR=/usr/src/linux-headers-5.15.0--generic
  from the linux tree directory
  
  Without the fix, it fails to compile:
    
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:
 In function ‘test_tailcall_bpf2bpf_6’:
    
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:9:
 warning: implicit declaration of function ‘LIBBPF_OPTS’; did you mean 
‘LIBBPF_API’? [-Wimplicit-function-declaration]
  822 | LIBBPF_OPTS(bpf_test_run_opts, topts,
  | ^~~
  | LIBBPF_API
    
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:21:
 error: ‘bpf_test_run_opts’ undeclared (first use in this function)
  822 | LIBBPF_OPTS(bpf_test_run_opts, topts,
  | ^
    
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:21:
 note: each undeclared identifier is reported only once for each function it 
appears in
    
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:40:
 error: ‘topts’ undeclared (first use in this function)
  822 | LIBBPF_OPTS(bpf_test_run_opts, topts,
  |^
    
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:823:17:
 error: expected expression before ‘.’ token
  823 | .data_in = _v4,
  | ^
    make[1]: *** [Makefile:471: 
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tailcalls.test.o]
 Error 1
    make: *** [Makefile:172: all] Error 2
  
  With the fix, it compiles.
  
  [Regression potential]
  The only place this is being used is selftests, so the risk is very low.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2054567

Title:
  Fix bpf selftests build failure after v5.15.139 update

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress

Bug description:
  Sru justification

  [Impact]
  Upstream v5.15.139  (#lp2049432) brought commit "selftests/bpf: Test tail 
call counting with bpf2bpf and data on stack" that affects one of the bpf 
kselftests.
  because LIBBPF_OPTS macro does not exists, it does not compile. Error below.

  [Fix]
  Initially, I thought cherry-pick commit "libbpf: Rename DECLARE_LIBBPF_OPTS 
into LIBBPF_OPTS" would be the best, but upstream stable just reverted the 
commit
  that broke it.
  Commit  62900d358c48 "Revert "selftests/bpf: Test tail call counting with 
bpf2bpf and data on stack"" will be cherry picked.

  [Test]
  This should be solved soon, but compileselftests debian rule does not compile 
bpf selftests.
  I tested it by using our regression testing tooling, but same results can be 
achieved by running:
  $ make  -C linux/tools/testing/selftests TARGETS=bpf SKIP_TARGETS= clean all 
KDIR=/usr/src/linux-headers-5.15.0--generic
  from the linux tree directory

  Without the fix, it fails to compile:
    
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:
 In function ‘test_tailcall_bpf2bpf_6’:
    
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:9:
 warning: implicit declaration of function ‘LIBBPF_OPTS’; did you mean 
‘LIBBPF_API’? [-Wimplicit-function-declaration]
  822 | LIBBPF_OPTS(bpf_test_run_opts, topts,
  | ^~~
  | LIBBPF_API
    

[Kernel-packages] [Bug 2049634] Re: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Mantic)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2049634

Title:
  smb: wsize blocks of bytes followed with binary zeros on copy,
  destroying data

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  In Progress

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/2049634

  [Impact]

  Upon installing the 6.5 HWE kernel on Jammy, users with a custom wsize
  set will see data destruction when copying files from their systems
  onto a cifs smb mount.

  wsize defaults to 65535 bytes, but when set to smaller values, like
  16850, users will see blocks of 16850 bytes copied over, followed by
  3900 binary zeros, followed by the next block of data followed by more
  binary zeros. This destroys what you are copying, and the data
  corruption is completely silent.

  A workaround is to set wsize to a multiple of PAGE_SIZE.

  [Fix]

  This was fixed upstream in 6.8-rc5 by the following:

  commit 4860abb91f3d7fbaf8147d54782149bb1fc45892
  Author: Steve French 
  Date: Tue Feb 6 16:34:22 2024 -0600
  Subject: smb: Fix regression in writes when non-standard maximum write size 
negotiated
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4860abb91f3d7fbaf8147d54782149bb1fc45892

  This patch has been selected for upstream stable.

  The patch looks at wsize negotiation from the server, and also what is set on 
the mount command line, and if not a multiple of PAGE_SIZE, rounds it down, 
taking care to not be 0.
  The real corruption bug still exists in netfs/folios subsystems and we are 
looking for it still, but this solves the immediate data corruption issues on 
smb.

  [Testcase]

  Start two VMs, one for the server, and the other, the client.

  Server
  --

  $ sudo apt update
  $ sudo apt upgrade
  $ sudo apt install samba
  $ sudo vim /etc/samba/smb.conf 
  server min protocol = NT1
  [sambashare]
  comment = Samba on Ubuntu
  path = /home/ubuntu/sambashare
  read only = no
  browsable = yes
  $ mkdir ~/sambashare
  $ sudo smbpasswd -a ubuntu

  Client
  --

  $ sudo apt update
  $ sudo apt install cifs-utils
  $ mkdir ~/share
  $ sudo mount -t cifs -o username=ubuntu,vers=1.0,wsize=16850 
//192.168.122.172/sambashare ~/share
  $ ( set -o pipefail && head --bytes=$(( 55 * 1000 )) /dev/zero | openssl enc 
-aes-128-ctr -nosalt -pass "pass:my-seed" -iter 1 | hexdump --no-squeezing 
--format '40/1 "%02x"' --format '"\n"' >"testdata.txt" )
  $ sha256sum testdata.txt 
  9ec09af020dce3270ea76531141940106f173c7243b7193a553480fb8500b3f2  testdata.txt

  Now copy the file to the share.

  Client
  --
  $ cp testdata.txt share/

  Server
  --
  $ sha256sum sambashare/testdata.txt 
  9e573a0aa795f9cd4de4ac684a1c056dbc7d2ba5494d02e71b6225ff5f0fd866  
sambashare/testdata.txt

  The SHA256 hash is different. If you view the file with less, you will
  find a block of wsize=16850 bytes, then 3900 bytes of binary zeros,
  followed by another wsize=16850 bytes, then 3900 bytes of binary
  zeros, etc.

  An example of a broken file is:
  https://launchpadlibrarian.net/712573213/testdata-back-from-server.txt

  [Where problems could occur]

  We are changing the wsize that the SMB server negotiates or the user
  explicitly sets on the mount command line to a safe value, if the
  asked for value was not a multiple of PAGE_SIZE.

  It is unlikely that any users will notice any difference. If the wsize
  happens to be rounded down to a significantly smaller number, there
  may be a small performance impact, e.g. you set wsize=8094 for some
  reason, it would round down to wsize=4096, and lead to double the
  writes. At least you have data integrity though.

  Most users default to wsize=65535, and will have no impact at all.
  Only those with very old smb 1.0 servers that negotiate down to 16850
  will see any difference.

  If a regression were to occur, it could result in user's wsize being
  incorrectly set, leading to the underlying netfs/folios data
  corruption being triggered and causing data corruption.

  [Other info]

  The issue was introduced in 6.3-rc1 by:

  commit d08089f649a0cfb2099c8551ac47eef0cc23fdf2
  Author: David Howells 
  Date: Mon Jan 24 21:13:24 2022 +
  Subject: cifs: Change the I/O paths to use an iterator rather than a page list
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d08089f649a0cfb2099c8551ac47eef0cc23fdf2

  Upstream mailing list discussion:

  https://lore.kernel.org/linux-
  
cifs/6a65b2d1-7596-438a-8ade-2f7526b15...@rd10.de/T/#m22cd9b7289f87cd945978bd7995bcaf1beebfe67

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

[Kernel-packages] [Bug 2054411] Re: Jammy update: v5.15.147 upstream stable release

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Jammy)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2054411

Title:
  Jammy update: v5.15.147 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 v5.15.147 upstream stable release
 from git://git.kernel.org/

  block: Don't invalidate pagecache for invalid falloc modes
  ALSA: hda/realtek: Fix mute and mic-mute LEDs for HP ProBook 440 G6
  Revert "PCI/ASPM: Remove pcie_aspm_pm_state_change()"
  wifi: iwlwifi: pcie: don't synchronize IRQs from IRQ
  drm/bridge: ti-sn65dsi86: Never store more than msg->size bytes in AUX xfer
  nfc: llcp_core: Hold a ref to llcp_local->dev when holding a ref to llcp_local
  octeontx2-af: Fix marking couple of structure as __packed
  drm/i915/dp: Fix passing the correct DPCD_REV for drm_dp_set_phy_test_pattern
  i40e: Fix filter input checks to prevent config with invalid values
  igc: Report VLAN EtherType matching back to user
  igc: Check VLAN TCI mask
  igc: Check VLAN EtherType mask
  ASoC: fsl_rpmsg: Fix error handler with pm_runtime_enable
  mlxbf_gige: fix receive packet race condition
  net: sched: em_text: fix possible memory leak in em_text_destroy()
  r8169: Fix PCI error on system resume
  net: Implement missing getsockopt(SO_TIMESTAMPING_NEW)
  can: raw: add support for SO_TXTIME/SCM_TXTIME
  can: raw: add support for SO_MARK
  net-timestamp: extend SOF_TIMESTAMPING_OPT_ID to HW timestamps
  ARM: sun9i: smp: Fix array-index-out-of-bounds read in sunxi_mc_smp_init
  sfc: fix a double-free bug in efx_probe_filters
  net: bcmgenet: Fix FCS generation for fragmented skbuffs
  netfilter: nft_immediate: drop chain reference counter on error
  net: Save and restore msg_namelen in sock_sendmsg
  i40e: fix use-after-free in i40e_aqc_add_filters()
  ASoC: meson: g12a-toacodec: Validate written enum values
  ASoC: meson: g12a-tohdmitx: Validate written enum values
  ASoC: meson: g12a-toacodec: Fix event generation
  ASoC: meson: g12a-tohdmitx: Fix event generation for S/PDIF mux
  i40e: Restore VF MSI-X state during PCI reset
  igc: Fix hicredit calculation
  net/qla3xxx: fix potential memleak in ql_alloc_buffer_queues
  octeontx2-af: Don't enable Pause frames by default
  octeontx2-af: Set NIX link credits based on max LMAC
  octeontx2-af: Always configure NIX TX link credits based on max frame size
  octeontx2-af: Re-enable MAC TX in otx2_stop processing
  asix: Add check for usbnet_get_endpoints
  bnxt_en: Remove mis-applied code from bnxt_cfg_ntp_filters()
  net: Implement missing SO_TIMESTAMPING_NEW cmsg support
  selftests: secretmem: floor the memory size to the multiple of page_size
  mm/memory-failure: check the mapcount of the precise page
  firewire: ohci: suppress unexpected system reboot in AMD Ryzen machines and 
ASM108x/VT630x PCIe cards
  x86/kprobes: fix incorrect return address calculation in 
kprobe_emulate_call_indirect
  i2c: core: Fix atomic xfer check for non-preempt config
  mm: fix unmap_mapping_range high bits shift bug
  mmc: meson-mx-sdhc: Fix initialization frozen issue
  mmc: rpmb: fixes pause retune on all RPMB partitions.
  mmc: core: Cancel delayed work before releasing host
  mmc: sdhci-sprd: Fix eMMC init failure after hw reset
  ipv6: remove max_size check inline with ipv4
  perf inject: Fix GEN_ELF_TEXT_OFFSET for jit
  kallsyms: Make module_kallsyms_on_each_symbol generally available
  tracing/kprobes: Fix symbol counting logic by looking at modules as well
  net: usb: ax88179_178a: remove redundant init code
  net: usb: ax88179_178a: move priv to driver_priv
  Linux 5.15.147
  UBUNTU: Upstream stable to v5.15.147

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2053251] Re: performance: Scheduler: ratelimit updating of load_avg

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Jammy)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2053251

Title:
  performance: Scheduler: ratelimit updating of load_avg

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  This is a public version of https://bugs.launchpad.net/bugs/2040026

  [Description]
    Improve cache bouncing on tg->load_avg

  [Hardware Information]
    Architecture:
  Intel / AMD (x86_64)
    Platform(s):
  Sapphire Rapids
    Date HW is expected at Canonical:

    Component(s):
  Perf-Scalability
  Scheduler

  [Software Information]
    Target Version:
  24.04
    Target Kernel:
  TBD
    Commit IDs:
  1528c661c24b sched/fair: Ratelimit update to tg->load_avg
    External Links:

  [Business Justification]

  [Testing guidance]

  [External ID]
    LFE-7154

  Here's the commit ID:1528c661c24b407e92194426b0adbb43de859ce0

  
https://github.com/torvalds/linux/commit/1528c661c24b407e92194426b0adbb43de859c0

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2054406] Re: Focal update: v5.4.267 upstream stable release

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2054406

Title:
  Focal update: v5.4.267 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 v5.4.267 upstream stable release
 from git://git.kernel.org/

  nfc: llcp_core: Hold a ref to llcp_local->dev when holding a ref to llcp_local
  i40e: Fix filter input checks to prevent config with invalid values
  net: sched: em_text: fix possible memory leak in em_text_destroy()
  can: raw: add support for SO_TXTIME/SCM_TXTIME
  can: raw: add support for SO_MARK
  net-timestamp: extend SOF_TIMESTAMPING_OPT_ID to HW timestamps
  ARM: sun9i: smp: Fix array-index-out-of-bounds read in sunxi_mc_smp_init
  net: bcmgenet: Fix FCS generation for fragmented skbuffs
  net: Save and restore msg_namelen in sock_sendmsg
  i40e: fix use-after-free in i40e_aqc_add_filters()
  ASoC: meson: g12a: extract codec-to-codec utils
  UBUNTU: [Config] Update annotations for CONFIG_SND_MESON_CODEC_GLUE
  ASoC: meson: g12a-tohdmitx: Validate written enum values
  ASoC: meson: g12a-tohdmitx: Fix event generation for S/PDIF mux
  i40e: Restore VF MSI-X state during PCI reset
  net/qla3xxx: switch from 'pci_' to 'dma_' API
  net/qla3xxx: fix potential memleak in ql_alloc_buffer_queues
  asix: Add check for usbnet_get_endpoints
  bnxt_en: Remove mis-applied code from bnxt_cfg_ntp_filters()
  net: Implement missing SO_TIMESTAMPING_NEW cmsg support
  mm/memory-failure: check the mapcount of the precise page
  firewire: ohci: suppress unexpected system reboot in AMD Ryzen machines and 
ASM108x/VT630x PCIe cards
  i2c: core: Fix atomic xfer check for non-preempt config
  mm: fix unmap_mapping_range high bits shift bug
  mmc: rpmb: fixes pause retune on all RPMB partitions.
  mmc: core: Cancel delayed work before releasing host
  mmc: sdhci-sprd: Fix eMMC init failure after hw reset
  ath10k: Wait until copy complete is actually done before completing
  ath10k: Add interrupt summary based CE processing
  ath10k: Keep track of which interrupts fired, don't poll them
  ath10k: Get rid of "per_ce_irq" hw param
  PCI: Extract ATS disabling to a helper function
  PCI: Disable ATS for specific Intel IPU E2000 devices
  net/dst: use a smaller percpu_counter batch for dst entries accounting
  ipv6: make ip6_rt_gc_expire an atomic_t
  ipv6: remove max_size check inline with ipv4
  ASoC: meson: codec-glue: fix pcm format cast warning
  Linux 5.4.267
  UBUNTU: Upstream stable to v5.4.267

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2054567] Re: ubuntu_bpf selftests fail to build

[Roxana Nicolescu]

Also sent en email to stable upstream to include the fix in 5.15 branch.


** Changed in: linux (Ubuntu Jammy)
   Status: Confirmed => In Progress

** Summary changed:

- ubuntu_bpf selftests fail to build 
+ fix bpf selftests build failure after v5.15.139 update

** Summary changed:

- fix bpf selftests build failure after v5.15.139 update
+ Fix bpf selftests build failure after v5.15.139 update

** Description changed:

  Sru justification
  
  [Impact]
  Upstream v5.15.139  (#lp2049432) brought commit "selftests/bpf: Test tail 
call counting with bpf2bpf and data on stack" that affects one of the bpf 
kselftests.
  because LIBBPF_OPTS macro does not exists, it does not compile. Error below.
  
  [Fix]
  Cherry-pick commit "libbpf: Rename DECLARE_LIBBPF_OPTS into LIBBPF_OPTS"
  
  [Test]
  This should be solved soon, but compileselftests debian rule does not compile 
bpf selftests.
  I tested it by using our regression testing tooling, but same results can be 
achieved by running:
  $ make  -C linux/tools/testing/selftests TARGETS=bpf SKIP_TARGETS= clean all 
KDIR=/usr/src/linux-headers-5.15.0--generic
  from the linux tree directory
  
  Without the fix, it fails to compile:
-   
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:
 In function ‘test_tailcall_bpf2bpf_6’:
-   
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:9:
 warning: implicit declaration of function ‘LIBBPF_OPTS’; did you mean 
‘LIBBPF_API’? [-Wimplicit-function-declaration]
- 822 | LIBBPF_OPTS(bpf_test_run_opts, topts,
- | ^~~
- | LIBBPF_API
-   
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:21:
 error: ‘bpf_test_run_opts’ undeclared (first use in this function)
- 822 | LIBBPF_OPTS(bpf_test_run_opts, topts,
- | ^
-   
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:21:
 note: each undeclared identifier is reported only once for each function it 
appears in
-   
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:40:
 error: ‘topts’ undeclared (first use in this function)
- 822 | LIBBPF_OPTS(bpf_test_run_opts, topts,
- |^
-   
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:823:17:
 error: expected expression before ‘.’ token
- 823 | .data_in = _v4,
- | ^
-   make[1]: *** [Makefile:471: 
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tailcalls.test.o]
 Error 1
-   make: *** [Makefile:172: all] Error 2
+   
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:
 In function ‘test_tailcall_bpf2bpf_6’:
+   
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:9:
 warning: implicit declaration of function ‘LIBBPF_OPTS’; did you mean 
‘LIBBPF_API’? [-Wimplicit-function-declaration]
+ 822 | LIBBPF_OPTS(bpf_test_run_opts, topts,
+ | ^~~
+ | LIBBPF_API
+   
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:21:
 error: ‘bpf_test_run_opts’ undeclared (first use in this function)
+ 822 | LIBBPF_OPTS(bpf_test_run_opts, topts,
+ | ^
+   
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:21:
 note: each undeclared identifier is reported only once for each function it 
appears in
+   
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:40:
 error: ‘topts’ undeclared (first use in this function)
+ 822 | LIBBPF_OPTS(bpf_test_run_opts, topts,
+ |^
+   
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:823:17:
 error: expected expression before ‘.’ token
+ 823 | .data_in = _v4,
+ | ^
+   make[1]: *** [Makefile:471: 
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tailcalls.test.o]
 Error 1
+   make: *** [Makefile:172: all] Error 2
  
  With the fix, it compiles.
+ 
+ [Regression potential]
+ The only place this is being used is selftests, so the risk is very low.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2054567

Title:
  Fix bpf selftests build failure after v5.15.139 update

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  

[Kernel-packages] [Bug 2054567] Re: ubuntu_bpf selftests fail to build

[Roxana Nicolescu]

** Changed in: linux (Ubuntu)
   Status: New => Invalid

** Changed in: linux (Ubuntu Jammy)
   Status: New => Confirmed

** Changed in: linux (Ubuntu Jammy)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Roxana Nicolescu (roxanan)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2054567

Title:
  ubuntu_bpf selftests fail to build

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Confirmed

Bug description:
  Sru justification

  [Impact]
  Upstream v5.15.139  (#lp2049432) brought commit "selftests/bpf: Test tail 
call counting with bpf2bpf and data on stack" that affects one of the bpf 
kselftests.
  because LIBBPF_OPTS macro does not exists, it does not compile. Error below.

  [Fix]
  Cherry-pick commit "libbpf: Rename DECLARE_LIBBPF_OPTS into LIBBPF_OPTS"

  [Test]
  This should be solved soon, but compileselftests debian rule does not compile 
bpf selftests.
  I tested it by using our regression testing tooling, but same results can be 
achieved by running:
  $ make  -C linux/tools/testing/selftests TARGETS=bpf SKIP_TARGETS= clean all 
KDIR=/usr/src/linux-headers-5.15.0--generic
  from the linux tree directory

  Without the fix, it fails to compile:

/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:
 In function ‘test_tailcall_bpf2bpf_6’:

/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:9:
 warning: implicit declaration of function ‘LIBBPF_OPTS’; did you mean 
‘LIBBPF_API’? [-Wimplicit-function-declaration]
  822 | LIBBPF_OPTS(bpf_test_run_opts, topts,
  | ^~~
  | LIBBPF_API

/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:21:
 error: ‘bpf_test_run_opts’ undeclared (first use in this function)
  822 | LIBBPF_OPTS(bpf_test_run_opts, topts,
  | ^

/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:21:
 note: each undeclared identifier is reported only once for each function it 
appears in

/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:40:
 error: ‘topts’ undeclared (first use in this function)
  822 | LIBBPF_OPTS(bpf_test_run_opts, topts,
  |^

/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:823:17:
 error: expected expression before ‘.’ token
  823 | .data_in = _v4,
  | ^
make[1]: *** [Makefile:471: 
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tailcalls.test.o]
 Error 1
make: *** [Makefile:172: all] Error 2

  With the fix, it compiles.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2049027] Re: The display becomes frozen after some time when a HDMI device is connected.

[Roxana Nicolescu]

Hi all,

This fix was also propagated to jammy:linux-hwe-6.5 kernel.
The version (6.5.0-25.25~22.04.1) is not in proposed yet, it should be there in 
a day or 2. 
But we have released (6.5.0-21.21~22.04.1) to proposed#2 (we use 2 separate 
streams because we run a smaller security cycle in parallel with the sru cycle)

So if you use
add-apt-repository ppa:canonical-kernel-team/proposed2

You should see 6.5.0-21.21~22.04.1 version there if you run
apt install linux-image-generic-hwe-22.04

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2049027

Title:
  The display becomes frozen after some time when a HDMI device is
  connected.

Status in linux package in Ubuntu:
  Invalid
Status in linux-signed-hwe-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-signed-hwe-6.5 source package in Mantic:
  Invalid

Bug description:
  
  SRU Justification:

  [Impact]

  Multiple users have reported frozen displays when external HDMI device
  is connected on systems with intel graphics chipsets.

  [Fix]

  * backport 49e0a85ec344: "drm/i915/dmc: Don't enable any pipe DMC events"
  from 6.6.9

  [Test Plan]

  * Tested on Intel TigerLake with iris Xe Graphics and no issues so far.
  It seems it affects mostly Alder Lake though, but at least it does not
  cause any issues on other models.
  * It has also been tested upstream 
https://gitlab.freedesktop.org/drm/intel/-/issues/8685

  [Where problems could occur]
  * We could see issues on systems with Intel Graphics when HDMI devices
  are connected during power state changes.

  
  Old description:
  It is exactly this bug: https://gitlab.freedesktop.org/drm/intel/-/issues/8685

  It was fixed with that kernel commit:

  commit 648d7be8ecf47b0556e32550145c70db153b16fb
  Author: Ville Syrjälä 
  Date:   Mon Dec 11 23:37:47 2023 +0200

  drm/i915/dmc: Don't enable any pipe DMC events

  
https://lore.kernel.org/stable/20231211213750.27109-2-ville.syrj...@linux.intel.com/

  which was picked for 6.6.9.

  I'd like to ask whether it is possible to apply that patch to the
  current Ubuntu kernel?

  Best
  Sönke

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 11 13:11:59 2024
  InstallationDate: Installed on 2023-03-01 (316 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2045561] Re: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules

[Roxana Nicolescu]

lunar is EOL

** Changed in: linux (Ubuntu Lunar)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2045561

Title:
  linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support)
  from linux-modules-extra to linux-modules

Status in linux package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  New
Status in linux source package in Noble:
  New

Bug description:
  SRU Justification

  [Impact]

  The dmi-sysfs.ko module (CONFIG_DMI_SYSFS) is currently shipped in
  linux-modules-extra. This makes it hard to pull in via the linux-
  virtual package, it can only come from the linux-generic one that also
  pulls in the firmware and everything else needed for baremetal, and
  that serves no purpose in a qemu VM. This stops VMs using these
  kernels from being configurable using qemu or cloud-hypervisor's
  SMBIOS type 11 strings. This feature is supported and used widely by
  systemd:

  https://www.freedesktop.org/software/systemd/man/latest/smbios-type-11.html
  https://systemd.io/CREDENTIALS/

  A user launching a VM using the linux-kvm kernel image is not able to
  specify SMBIOS strings to automatically configured userspace services
  and programs due to the lack of this kconfig. We make extensive use of
  these in systemd's upstream CI, which is running on Github Actions,
  which uses Jammy, so it would be great to have this backported.

  For example:

  qemu-system-x86_64 \
  -machine type=q35,accel=kvm,smm=on \
  -smp 2 \
  -m 1G \
  -cpu host \
  -nographic \
  -nodefaults \
  -serial mon:stdio \
  -drive if=none,id=hd,file=ubuntu_jammy.raw,format=raw \
  -device virtio-scsi-pci,id=scsi \
  -device scsi-hd,drive=hd,bootindex=1 \
  -smbios type=11,value=io.systemd.credential:mycred=supersecret

  [Fix]

  Please consider moving this module to linux-modules.

  These are already enabled in the 'main' kernel config, and in other
  distros. In Debian/Archlinux/Fedora it is a built-in, and on SUSE it
  is a module installed by default.

  To verify this works, it is sufficient to check that the
  /sys/firmware/dmi/entries/ directory in sysfs is present:

  $ ls /sys/firmware/dmi/entries/
  0-0126-1   126-4  126-8  130-0  133-0  136-0  140-2  15-0  18-0  21-1   
221-1  24-0  7-1  8-2  8-6
  1-0126-10  126-5  126-9  131-0  134-0  14-0   140-3  16-0  19-0  219-0  
221-2  3-0   7-2  8-3  9-0
  12-0   126-2   126-6  127-0  131-1  135-0  140-0  140-4  17-0  2-0   22-0   
221-3  4-0   8-0  8-4  9-1
  126-0  126-3   126-7  13-0   132-0  135-1  140-1  14-1   17-1  21-0  221-0  
222-0  7-0   8-1  8-5

  Without this module installed and loaded, the directory won't be
  there. Once enabled, it will be there.

  [Regression Potential]

  Moving a module from a less-common to a more-common package should not
  have any negative side effects. The main effect will be a little more
  disk space used by the more common package, whether the module is in
  use or not. There will also be more functionality available in the
  default installation, which means a slightly increased surface and
  possibility of new bugs in case it gets used.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2054567] [NEW] ubuntu_bpf selftests fail to build

[Roxana Nicolescu]

Public bug reported:

Sru justification

[Impact]
Upstream v5.15.139  (#lp2049432) brought commit "selftests/bpf: Test tail call 
counting with bpf2bpf and data on stack" that affects one of the bpf kselftests.
because LIBBPF_OPTS macro does not exists, it does not compile. Error below.

[Fix]
Cherry-pick commit "libbpf: Rename DECLARE_LIBBPF_OPTS into LIBBPF_OPTS"

[Test]
This should be solved soon, but compileselftests debian rule does not compile 
bpf selftests.
I tested it by using our regression testing tooling, but same results can be 
achieved by running:
$ make  -C linux/tools/testing/selftests TARGETS=bpf SKIP_TARGETS= clean all 
KDIR=/usr/src/linux-headers-5.15.0--generic
from the linux tree directory

Without the fix, it fails to compile:
  
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:
 In function ‘test_tailcall_bpf2bpf_6’:
  
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:9:
 warning: implicit declaration of function ‘LIBBPF_OPTS’; did you mean 
‘LIBBPF_API’? [-Wimplicit-function-declaration]
822 | LIBBPF_OPTS(bpf_test_run_opts, topts,
| ^~~
| LIBBPF_API
  
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:21:
 error: ‘bpf_test_run_opts’ undeclared (first use in this function)
822 | LIBBPF_OPTS(bpf_test_run_opts, topts,
| ^
  
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:21:
 note: each undeclared identifier is reported only once for each function it 
appears in
  
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:40:
 error: ‘topts’ undeclared (first use in this function)
822 | LIBBPF_OPTS(bpf_test_run_opts, topts,
|^
  
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:823:17:
 error: expected expression before ‘.’ token
823 | .data_in = _v4,
| ^
  make[1]: *** [Makefile:471: 
/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tailcalls.test.o]
 Error 1
  make: *** [Makefile:172: all] Error 2

With the fix, it compiles.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Jammy)
 Importance: Undecided
 Status: New


** Tags: sru-20240205

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Tags added: sru-20240205

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2054567

Title:
  ubuntu_bpf selftests fail to build

Status in linux package in Ubuntu:
  New
Status in linux source package in Jammy:
  New

Bug description:
  Sru justification

  [Impact]
  Upstream v5.15.139  (#lp2049432) brought commit "selftests/bpf: Test tail 
call counting with bpf2bpf and data on stack" that affects one of the bpf 
kselftests.
  because LIBBPF_OPTS macro does not exists, it does not compile. Error below.

  [Fix]
  Cherry-pick commit "libbpf: Rename DECLARE_LIBBPF_OPTS into LIBBPF_OPTS"

  [Test]
  This should be solved soon, but compileselftests debian rule does not compile 
bpf selftests.
  I tested it by using our regression testing tooling, but same results can be 
achieved by running:
  $ make  -C linux/tools/testing/selftests TARGETS=bpf SKIP_TARGETS= clean all 
KDIR=/usr/src/linux-headers-5.15.0--generic
  from the linux tree directory

  Without the fix, it fails to compile:

/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:
 In function ‘test_tailcall_bpf2bpf_6’:

/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:9:
 warning: implicit declaration of function ‘LIBBPF_OPTS’; did you mean 
‘LIBBPF_API’? [-Wimplicit-function-declaration]
  822 | LIBBPF_OPTS(bpf_test_run_opts, topts,
  | ^~~
  | LIBBPF_API

/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:21:
 error: ‘bpf_test_run_opts’ undeclared (first use in this function)
  822 | LIBBPF_OPTS(bpf_test_run_opts, topts,
  | ^

/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:21:
 note: each undeclared identifier is reported only once for each function it 
appears in

/root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:40:
 error: ‘topts’ undeclared (first use in this function)
  822 | LIBBPF_OPTS(bpf_test_run_opts, 

[Kernel-packages] [Bug 2049689] Re: partproke is broken on empty loopback device

[Roxana Nicolescu]

I tested it in a vm following the instruction from the description and
the error is not reproducible anymore. I'll mark this as verified so
that we can release the kernel

** Tags removed: verification-needed-jammy-linux 
verification-needed-mantic-linux
** Tags added: verification-done-jammy-linux verification-done-mantic-linux

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2049689

Title:
  partproke is broken on empty loopback device

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

  * BLKPG_DEL_PARTITION on an empty loopback device used to return ENXIO
  but now returns EINVAL, breaking partprobe due to commit
  "block: don't add or resize partition on the disk with GENHD_FL_NO_PART"
  introduced in mantic 6.5.0-17 and jammy 5.15.0-94.

  [Fix]

  * backport commit
  "block: Move checking GENHD_FL_NO_PART to bdev_add_partition()"

  [Test Plan]

  * dd if=/dev/zero of=/tmp/foo bs=1M count=50
  * partprobe $(losetup --find --show /tmp/foo)
  Before the fix this fails.
  After the fix it should work.

  [Where problems could occur]

  * We may see issues on disk partitions operations.

  
  Old description:
  This is with the kernel from jammy-proposed (linux-image-5.15.0-94-generic 
5.15.0-94.104).

  Do this:

  # dd if=/dev/zero of=/tmp/file bs=1M count=50
  # partprobe "$(losetup --show --find /tmp/file)"

  Notice this very odd error message:

  Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
  16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32,
  33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49,
  50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on
  /dev/loop2 have been written, but we have been unable to inform the
  kernel of the change, probably because it/they are in use.  As a
  result, the old partition(s) will remain in use.  You should reboot
  now before making further changes.

  That's a result of an ioctl changing its error code in an incompatible
  way between kernel versions 5.15.0.91.88 and 5.15.0.94.91, confusing
  partprobe.

  5.15.0.91.88:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 ENXIO (No such device or 
address)

  5.15.0.94.91:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 EINVAL (Invalid argument)

  This is a userspace API break which impacts GNU parted and util-linux
  (as confirmed by the util-linux maintainer).

  This issue was discovered as part of Cockpit CI here:
  https://github.com/cockpit-project/bots/pull/5793

  This issue is being discussed on LKML here (with a patch likely to
  land soon): https://lkml.org/lkml/2024/1/15/147

  lsb_release -rd:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2049689] Re: partproke is broken on empty loopback device

[Roxana Nicolescu]

Allison Karlitskaya (desrt) sorry, just saw your question now.
You can install the new version from -proposed 5.15.0-100.110.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2049689

Title:
  partproke is broken on empty loopback device

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

  * BLKPG_DEL_PARTITION on an empty loopback device used to return ENXIO
  but now returns EINVAL, breaking partprobe due to commit
  "block: don't add or resize partition on the disk with GENHD_FL_NO_PART"
  introduced in mantic 6.5.0-17 and jammy 5.15.0-94.

  [Fix]

  * backport commit
  "block: Move checking GENHD_FL_NO_PART to bdev_add_partition()"

  [Test Plan]

  * dd if=/dev/zero of=/tmp/foo bs=1M count=50
  * partprobe $(losetup --find --show /tmp/foo)
  Before the fix this fails.
  After the fix it should work.

  [Where problems could occur]

  * We may see issues on disk partitions operations.

  
  Old description:
  This is with the kernel from jammy-proposed (linux-image-5.15.0-94-generic 
5.15.0-94.104).

  Do this:

  # dd if=/dev/zero of=/tmp/file bs=1M count=50
  # partprobe "$(losetup --show --find /tmp/file)"

  Notice this very odd error message:

  Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
  16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32,
  33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49,
  50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on
  /dev/loop2 have been written, but we have been unable to inform the
  kernel of the change, probably because it/they are in use.  As a
  result, the old partition(s) will remain in use.  You should reboot
  now before making further changes.

  That's a result of an ioctl changing its error code in an incompatible
  way between kernel versions 5.15.0.91.88 and 5.15.0.94.91, confusing
  partprobe.

  5.15.0.91.88:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 ENXIO (No such device or 
address)

  5.15.0.94.91:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 EINVAL (Invalid argument)

  This is a userspace API break which impacts GNU parted and util-linux
  (as confirmed by the util-linux maintainer).

  This issue was discovered as part of Cockpit CI here:
  https://github.com/cockpit-project/bots/pull/5793

  This issue is being discussed on LKML here (with a patch likely to
  land soon): https://lkml.org/lkml/2024/1/15/147

  lsb_release -rd:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2051176] Re: Update Ubuntu.md

[Roxana Nicolescu]

No functional change, no test needed

** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic-linux

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2051176

Title:
  Update Ubuntu.md

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

   * The Ubuntu.md has incorrect Ubuntu release and kernel version
  information which may impact any tools that use this information to
  determine the Ubuntu release.

  [ Test Plan ]

   * cat Ubuntu.md and check to make sure it is correct

  [ Where problems could occur ]

   * There is no functional impact on the kernel.. we could introduce a
  typo in Ubuntu.md

  [ Other Info ]

  * I used the current kernel version of 6.5.10 since it didn't seem to
  make sense to use the old version we released with.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2052005] Re: Validate connection interval to pass Bluetooth Test Suite

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Mantic)
   Status: Confirmed => Fix Committed

** Changed in: linux (Ubuntu Noble)
   Status: Confirmed => In Progress

** Changed in: linux (Ubuntu Jammy)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2052005

Title:
  Validate connection interval to pass Bluetooth Test Suite

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  In Progress

Bug description:
  [Impact]
  Ubuntu doesn't pass Bluetooth Test Suite to get Bluetooth certified.

  [Fix]
  Validate max connection interval to pass test case
  "GAP/CONN/CPUP/BV-05-C 'Connection Parameter Update Procedure Invalid
  Parameters Central Responder'" 

  [Test]
  Run the test suite. With the patch applied the case is passed.

  [Where problems could occur]
  If any device requires setting a wrong interval to function properly,
  this might affect those devices in theory.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2051947] Re: Sound: Add rtl quirk of M70-Gen5

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Mantic)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2051947

Title:
  Sound: Add rtl quirk of M70-Gen5

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  New
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  When plugin the headset jack, only speaker is identified.

  [Fix]
  Add ALC283_FIXUP_HEADSET_MIC quirk to make its headset mic work.

  [Test]
  Vendor tested on hardware, headset mic works fine.

  [Where problems could occur]
  It may break audio.

  This commit is merged by stable updates in noble kernel,
  5.15 doesn't support this platform,
  SRU for mantic and oem-6.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2051947/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2051896] Re: Fix spurious wakeup caused by Cirque touchpad

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Mantic)
   Status: Confirmed => Fix Committed

** Changed in: linux (Ubuntu Noble)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2051896

Title:
  Fix spurious wakeup caused by Cirque touchpad

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  Spurious wakeup event caused by Cirque touchpad, prevent the system from
  sleep properly.

  [Fix]
  Skip SET_POWER SLEEP so there won't be any IRQ raised by the touchpad.

  [Test]
  Suspend the system 100 times and make sure non of the wakeup event is
  caused by the touchpad and its IRQ line.

  [Where problems could occur]
  Logically the power consumption can increase slightly, but in reality
  there isn't any noticeable change. Since the quirk only applies to one
  device, there isn't much regression risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2051896/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp