[Kernel-packages] [Bug 2060291] [NEW] [Intel N95] Horizonral line artifact/ghosting when scaling windows to a certain width

2024-04-07 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

When scaling some windows in some programs down horizontal lines appear
that seem to be part of the texture memory somewhere else on the screen.

This only occurs in some programs like nautilus and gedit, but not in
others like terminal or Firefox.

It did however occur when I opened the dialog in firefox to attach the
screen capture.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  5 03:44:15 2024
DistUpgraded: 2024-04-04 22:25:39,405 DEBUG icon theme changed, re-reading
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
 nvidia/470.239.06, 5.15.0-101-generic, x86_64: installed
 nvidia/470.239.06, 6.5.0-26-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Alder Lake-N [UHD Graphics] [8086:46d2] (prog-if 00 [VGA 
controller])
   Subsystem: Intel Corporation Alder Lake-N [UHD Graphics] [8086:7270]
InstallationDate: Installed on 2022-12-15 (477 days ago)
InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
 Bus 001 Device 003: ID 0461:4e8d Primax Electronics, Ltd HP USB Optical Mouse
 Bus 001 Device 002: ID 04f3:0103 Elan Microelectronics Corp. ActiveJet K-2024 
Multimedia Keyboard
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic 
root=UUID=7e20054f-50f7-4011-8c9c-516960719274 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2024-04-05 (0 days ago)
dmi.bios.date: 02/06/2023
dmi.bios.release: 5.26
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: ADLNV104
dmi.board.asset.tag: Default string
dmi.board.name: MINI S
dmi.board.vendor: AZW
dmi.board.version: 10
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrADLNV104:bd02/06/2023:br5.26:svnAZW:pnMINIS:pvrDefaultstring:rvnAZW:rnMINIS:rvr10:cvnDefaultstring:ct3:cvrDefaultstring:sku01:
dmi.product.family: Default string
dmi.product.name: MINI S
dmi.product.sku: 01
dmi.product.version: Default string
dmi.sys.vendor: AZW
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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

** Affects: nautilus (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug corruption mantic ubuntu
-- 
[Intel N95] Horizonral line artifact/ghosting when scaling windows to a certain 
width
https://bugs.launchpad.net/bugs/2060291
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
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 2058808] Re: iwlwifi disconnect and crash - intel wifi7

2024-04-07 Thread Andy Chi
** Tags added: originate-from-2060420 stella

-- 
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/2058808

Title:
  iwlwifi disconnect and crash - intel wifi7

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  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:
  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:
  iwlwifi disconnecting and crashing when I using Wifi 2.4GHz.

  [ cut here ]
  Invalid rxb from HW 0
  WARNING: CPU: 14 PID: 896 at 
drivers/net/wireless/intel/iwlwifi/pcie/rx.c:1489 
iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
  Modules linked in: ccm vboxdrv(OE) rfcomm cmac algif_hash algif_skcipher 
af_alg bnep btusb btrtl btbcm btintel btmtk bluetooth ecdh_generic input_leds 
joydev ecc intel_rapl_msr intel_rapl_common intel_uncore_frequency 
intel_uncore_frequency_common nft_limit x86_pkg_temp_thermal intel_powerclamp 
coretemp iwlmvm kvm_intel xt_tcpudp xt_LOG nf_log_syslog kvm mac80211 xt_limit 
xt_conntrack nf_conntrack libarc4 nf_defrag_ipv6 irqbypass nf_defrag_ipv4 
crct10dif_pclmul crc32_pclmul nft_compat polyval_clmulni polyval_generic 
nf_tables ghash_clmulni_intel libcrc32c sha256_ssse3 iwlwifi sha1_ssse3 sunrpc 
rapl nvidia_uvm(PO) nfnetlink binfmt_misc n
   xhci_pci xhci_pci_renesas nvme_common video wmi mac_hid
  CPU: 14 PID: 896 Comm: irq/160-iwlwifi Tainted: PW  OE  
6.5.0-26-generic #26~22.04.1-Ubuntu
  Hardware name: ASRock Z790 Nova WiFi/Z790 Nova WiFi, BIOS 3.09 12/26/2023
  RIP: 0010:iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
  Code: e9 8b 43 34 83 43 30 08 83 e8 08 89 43 34 e9 70 fe ff ff 44 89 f0 89 d6 
45 89 e6 41 89 c4 48 c7 c7 a8 cb 53 c4 e8 42 e4 62 e8 <0f> 0b 4c 89 ff e8 e8 3b 
ff ff 8b 55 d4 85 d2 0f 95 c0 41 21 c6 e9
  RSP: 0018:b91d803e0e18 EFLAGS: 00010246
  RAX:  RBX: 956747353c30 RCX: 
  RDX:  RSI:  RDI: 
  RBP: b91d803e0e78 R08:  R09: 
  R10:  R11:  R12: 1007
  R13: 0015 R14:  R15: 956746a30028
  FS:  () GS:95768f38() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 02659c472000 CR3: 000112e8e000 CR4: 00752ee0
  PKRU: 5554
  Call Trace:
   
   ? show_regs+0x6d/0x80
   ? __warn+0x89/0x160
   ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
   ? report_bug+0x17e/0x1b0
   ? handle_bug+0x46/0x90
   ? exc_invalid_op+0x18/0x80
   ? asm_exc_invalid_op+0x1b/0x20
   ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
   ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi]
   ? free_unref_page+0x30/0x180
   iwl_pcie_napi_poll_msix+0x32/0x100 [iwlwifi]
   ? skb_free_head+0xa8/0xd0
   __napi_poll+0x30/0x1f0
   net_rx_action+0x181/0x2e0
   ? __irq_wake_thread+0x42/0x50
   __do_softirq+0xd9/0x349
   ? __pfx_irq_thread_fn+0x10/0x10
   do_softirq.part.0+0x41/0x80
   
   
   __local_bh_enable_ip+0x72/0x80
   iwl_pcie_irq_rx_msix_handler+0xd7/0x1a0 [iwlwifi]
   irq_thread_fn+0x21/0x70
   irq_thread+0xf8/0x1c0
   ? __pfx_irq_thread_dtor+0x10/0x10
   ? __pfx_irq_thread+0x10/0x10
   kthread+0xef/0x120
   ? __pfx_kthread+0x10/0x10
   ret_from_fork+0x44/0x70
   ? __pfx_kthread+0x10/0x10
   ret_from_fork_asm+0x1b/0x30
   
  ---[ end trace  ]---
  iwlwifi :05:00.0: Microcode SW error detected. Restarting 0x0.
  iwlwifi :05:00.0: Start IWL Error Log Dump:
  iwlwifi :05:00.0: Transport status: 0x004A, valid: 6
  iwlwifi :05:00.0: Loaded firmware version: 83.ec13314b.0 
gl-c0-fm-c0-83.ucode
  iwlwifi :05:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN
  iwlwifi :05:00.0: 0x0003 | trm_hw_status0
  iwlwifi :05:00.0: 0x | trm_hw_status1
  iwlwifi :05:00.0: 0x002C280A | branchlink2
  iwlwifi :05:00.0: 0x9328 | interruptlink1
  iwlwifi :05:00.0: 0x9328 | interruptlink2
  iwlwifi :05:00.0: 0xF46C | data1
  iwlwifi :05:00.0: 0x0100 | data2
  iwlwifi :05:00.0: 0x | data3
  iwlwifi :05:00.0: 0xA0005E44 | beacon time
  iwlwifi :05:00.0: 0x2806818F | tsf low
  iwlwifi :05:00.0: 0x | tsf hi
  iwlwifi :05:00.0: 0x | time gp1
  iwlwifi :05:00.0: 0x0BB840A7 | time gp2
  iwlwifi :05:00.0: 0x0001 | uCode revision type
  iwlwifi :05:00.0: 0x0053 | uCode version major
  iwlwifi :05:00.0: 0xEC13314B | uCode version minor
  iwlwifi :05:00.0: 0x0472 | hw version
  iwlwifi :05:00.0: 0x00C80002 | board version
  iwlwifi :05:00.0: 0x03B7001C | hcmd
  iwlwifi :05:00.0: 

[Kernel-packages] [Bug 2049634] Re: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data

2024-04-07 Thread Matthew Ruffell
Hi R. Diez,

The 6.5.0-27-generic kernel just got released, so it should make its way
to an archive mirror near you in the next couple of hours, and should
solve your SMB 1 issue. The 6.8 kernel should be good to go when you get
it in the next couple of months.

Let us know if you encounter any more SMB 1 issues in the future.

Thanks,
Matthew

-- 
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:
  Fix Committed
Status in linux source package in Mantic:
  Fix Released
Status in linux source package in Noble:
  Fix Committed

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 

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

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1055.61~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-done-focal-linux-oracle-5.15'. If the
problem still exists, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-failed-focal-linux-oracle-5.15'.


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


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


** Tags added: kernel-spammed-focal-linux-oracle-5.15-v2 
verification-needed-focal-linux-oracle-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/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 2045561] Re: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1055.61~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-done-focal-linux-oracle-5.15'. If the
problem still exists, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-failed-focal-linux-oracle-5.15'.


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


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


** Tags added: kernel-spammed-focal-linux-oracle-5.15-v2 
verification-needed-focal-linux-oracle-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/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 Released
Status in linux source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  Fix Released
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 1971699] Re: disable Intel DMA remapping by default

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
bluefield/5.15.0-1040.42 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-bluefield'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-failed-jammy-linux-bluefield'.


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


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


** Tags added: kernel-spammed-jammy-linux-bluefield-v2 
verification-needed-jammy-linux-bluefield

-- 
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 1971699] Re: disable Intel DMA remapping by default

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1052.58 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-done-jammy-linux-intel-iotg'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-failed-jammy-linux-intel-iotg'.


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


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


** Tags added: kernel-spammed-jammy-linux-intel-iotg-v2 
verification-needed-jammy-linux-intel-iotg

-- 
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 2045561] Re: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
bluefield/5.15.0-1040.42 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-bluefield'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-failed-jammy-linux-bluefield'.


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


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


** Tags added: kernel-spammed-jammy-linux-bluefield-v2 
verification-needed-jammy-linux-bluefield

-- 
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 Released
Status in linux source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  Fix Released
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 2045561] Re: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-raspi/6.5.0-1014.17
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-raspi' to 'verification-done-
mantic-linux-raspi'. If the problem still exists, change the tag
'verification-needed-mantic-linux-raspi' to 'verification-failed-mantic-
linux-raspi'.


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


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


** Tags added: kernel-spammed-mantic-linux-raspi-v2 
verification-needed-mantic-linux-raspi

-- 
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 Released
Status in linux source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  Fix Released
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 2045561] Re: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1052.58 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-done-jammy-linux-intel-iotg'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-failed-jammy-linux-intel-iotg'.


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


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


** Tags added: kernel-spammed-jammy-linux-intel-iotg-v2 
verification-needed-jammy-linux-intel-iotg

-- 
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 Released
Status in linux source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  Fix Released
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 2052005] Re: Validate connection interval to pass Bluetooth Test Suite

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-raspi/6.5.0-1014.17
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-raspi' to 'verification-done-
mantic-linux-raspi'. If the problem still exists, change the tag
'verification-needed-mantic-linux-raspi' to 'verification-failed-mantic-
linux-raspi'.


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


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


** Tags added: kernel-spammed-mantic-linux-raspi-v2 
verification-needed-mantic-linux-raspi

-- 
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 Released
Status in linux source package in Mantic:
  Fix Released
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 2052005] Re: Validate connection interval to pass Bluetooth Test Suite

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
bluefield/5.15.0-1040.42 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-bluefield'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-failed-jammy-linux-bluefield'.


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


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


** Tags added: kernel-spammed-jammy-linux-bluefield-v2 
verification-needed-jammy-linux-bluefield

-- 
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 Released
Status in linux source package in Mantic:
  Fix Released
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 2052005] Re: Validate connection interval to pass Bluetooth Test Suite

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1055.61~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-done-focal-linux-oracle-5.15'. If the
problem still exists, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-failed-focal-linux-oracle-5.15'.


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


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


** Tags added: kernel-spammed-focal-linux-oracle-5.15-v2 
verification-needed-focal-linux-oracle-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/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 Released
Status in linux source package in Mantic:
  Fix Released
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 2052005] Re: Validate connection interval to pass Bluetooth Test Suite

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1052.58 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-done-jammy-linux-intel-iotg'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-failed-jammy-linux-intel-iotg'.


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


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


** Tags added: kernel-spammed-jammy-linux-intel-iotg-v2 
verification-needed-jammy-linux-intel-iotg

-- 
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 Released
Status in linux source package in Mantic:
  Fix Released
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 2052817] Re: cpufreq: intel_pstate: Enable HWP IO boost for all servers

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1055.61~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-done-focal-linux-oracle-5.15'. If the
problem still exists, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-failed-focal-linux-oracle-5.15'.


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


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


** Tags added: kernel-spammed-focal-linux-oracle-5.15-v2 
verification-needed-focal-linux-oracle-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/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 Released

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 2052817] Re: cpufreq: intel_pstate: Enable HWP IO boost for all servers

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
bluefield/5.15.0-1040.42 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-bluefield'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-failed-jammy-linux-bluefield'.


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


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


** Tags added: kernel-spammed-jammy-linux-bluefield-v2 
verification-needed-jammy-linux-bluefield

-- 
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 Released

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 2052817] Re: cpufreq: intel_pstate: Enable HWP IO boost for all servers

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1052.58 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-done-jammy-linux-intel-iotg'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-failed-jammy-linux-intel-iotg'.


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


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


** Tags added: kernel-spammed-jammy-linux-intel-iotg-v2 
verification-needed-jammy-linux-intel-iotg

-- 
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 Released

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 2052827] Re: performance: mm/memcontrol.c: remove the redundant updating of stats_flush_threshold

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1055.61~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-done-focal-linux-oracle-5.15'. If the
problem still exists, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-failed-focal-linux-oracle-5.15'.


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


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


** Tags added: kernel-spammed-focal-linux-oracle-5.15-v2 
verification-needed-focal-linux-oracle-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/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 Released

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 2052827] Re: performance: mm/memcontrol.c: remove the redundant updating of stats_flush_threshold

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
bluefield/5.15.0-1040.42 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-bluefield'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-failed-jammy-linux-bluefield'.


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


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


** Tags added: kernel-spammed-jammy-linux-bluefield-v2 
verification-needed-jammy-linux-bluefield

-- 
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 Released

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 2052827] Re: performance: mm/memcontrol.c: remove the redundant updating of stats_flush_threshold

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1052.58 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-done-jammy-linux-intel-iotg'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-failed-jammy-linux-intel-iotg'.


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


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


** Tags added: kernel-spammed-jammy-linux-intel-iotg-v2 
verification-needed-jammy-linux-intel-iotg

-- 
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 Released

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 2053069] Re: performance: address_space: add padding for i_map and i_mmap_rwsem to mitigate a false sharing

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1055.61~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-done-focal-linux-oracle-5.15'. If the
problem still exists, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-failed-focal-linux-oracle-5.15'.


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


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


** Tags added: kernel-spammed-focal-linux-oracle-5.15-v2 
verification-needed-focal-linux-oracle-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/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 Released

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 2053069] Re: performance: address_space: add padding for i_map and i_mmap_rwsem to mitigate a false sharing

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
bluefield/5.15.0-1040.42 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-bluefield'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-failed-jammy-linux-bluefield'.


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


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


** Tags added: kernel-spammed-jammy-linux-bluefield-v2 
verification-needed-jammy-linux-bluefield

-- 
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 Released

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 2053069] Re: performance: address_space: add padding for i_map and i_mmap_rwsem to mitigate a false sharing

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1052.58 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-done-jammy-linux-intel-iotg'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-failed-jammy-linux-intel-iotg'.


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


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


** Tags added: kernel-spammed-jammy-linux-intel-iotg-v2 
verification-needed-jammy-linux-intel-iotg

-- 
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 Released

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 2053152] Re: performance: mm/percpu-internal.h: Re-layout pcpu_chunk to mitigate false sharing

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
bluefield/5.15.0-1040.42 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-bluefield'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-failed-jammy-linux-bluefield'.


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


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


** Tags added: kernel-spammed-jammy-linux-bluefield-v2 
verification-needed-jammy-linux-bluefield

-- 
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/2053152

Title:
  performance: mm/percpu-internal.h: Re-layout pcpu_chunk to mitigate
  false sharing

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

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

  [Description]
When running UnixBench/Execl throughput case, false sharing is observed due 
to frequent read on base_addr and write on free_bytes, chunk_md.
UnixBench/Execl represents a class of workload where bash scripts are 
spawned frequently to do some short jobs. It will do system call on execl 
frequently, and execl will call mm_init to initialize mm_struct of the process. 
mm_init will call __percpu_counter_init for percpu_counters initialization. 
Then pcpu_alloc is called to read the base_addr of pcpu_chunk for memory 
allocation. Inside pcpu_alloc, it will call pcpu_alloc_area to allocate memory 
from a specified chunk. This function will update "free_bytes" and "chunk_md" 
to record the rest free bytes and other meta data for this chunk. 
Correspondingly, pcpu_free_area will also update these 2 members when free 
memory.

In current pcpu_chunk layout, `base_addr' is in the same cache line
  with `free_bytes' and `chunk_md', and `base_addr' is at the last 8
  bytes. This patch moves `bound_map' up to `base_addr', to let
  `base_addr' locate in a new cacheline.

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

Component(s):
  Performance and Scalability

  [Software Information]
Target Version:
  23.10
Target Kernel:
  6.5
Commit IDs:
  3a6358c0dbe6 percpu-internal/pcpu_chunk: re-layout pcpu_chunk structure 
to reduce false sharing
External Links:

  [Business Justification]

  [Testing guidance]

  [External ID]
OSVE-5160


  The following requested patch has been applied upstream for v6.5-rc1:

   - 3a6358c0dbe6 percpu-internal/pcpu_chunk: re-layout pcpu_chunk
  structure to reduce false sharing

  
https://github.com/torvalds/linux/commit/3a6358c0dbe6a286a4f4504ba392a6039a9fbd12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053152/+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 2053152] Re: performance: mm/percpu-internal.h: Re-layout pcpu_chunk to mitigate false sharing

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1055.61~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-done-focal-linux-oracle-5.15'. If the
problem still exists, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-failed-focal-linux-oracle-5.15'.


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


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


** Tags added: kernel-spammed-focal-linux-oracle-5.15-v2 
verification-needed-focal-linux-oracle-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/2053152

Title:
  performance: mm/percpu-internal.h: Re-layout pcpu_chunk to mitigate
  false sharing

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

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

  [Description]
When running UnixBench/Execl throughput case, false sharing is observed due 
to frequent read on base_addr and write on free_bytes, chunk_md.
UnixBench/Execl represents a class of workload where bash scripts are 
spawned frequently to do some short jobs. It will do system call on execl 
frequently, and execl will call mm_init to initialize mm_struct of the process. 
mm_init will call __percpu_counter_init for percpu_counters initialization. 
Then pcpu_alloc is called to read the base_addr of pcpu_chunk for memory 
allocation. Inside pcpu_alloc, it will call pcpu_alloc_area to allocate memory 
from a specified chunk. This function will update "free_bytes" and "chunk_md" 
to record the rest free bytes and other meta data for this chunk. 
Correspondingly, pcpu_free_area will also update these 2 members when free 
memory.

In current pcpu_chunk layout, `base_addr' is in the same cache line
  with `free_bytes' and `chunk_md', and `base_addr' is at the last 8
  bytes. This patch moves `bound_map' up to `base_addr', to let
  `base_addr' locate in a new cacheline.

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

Component(s):
  Performance and Scalability

  [Software Information]
Target Version:
  23.10
Target Kernel:
  6.5
Commit IDs:
  3a6358c0dbe6 percpu-internal/pcpu_chunk: re-layout pcpu_chunk structure 
to reduce false sharing
External Links:

  [Business Justification]

  [Testing guidance]

  [External ID]
OSVE-5160


  The following requested patch has been applied upstream for v6.5-rc1:

   - 3a6358c0dbe6 percpu-internal/pcpu_chunk: re-layout pcpu_chunk
  structure to reduce false sharing

  
https://github.com/torvalds/linux/commit/3a6358c0dbe6a286a4f4504ba392a6039a9fbd12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053152/+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 2053152] Re: performance: mm/percpu-internal.h: Re-layout pcpu_chunk to mitigate false sharing

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1052.58 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-done-jammy-linux-intel-iotg'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-failed-jammy-linux-intel-iotg'.


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


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


** Tags added: kernel-spammed-jammy-linux-intel-iotg-v2 
verification-needed-jammy-linux-intel-iotg

-- 
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/2053152

Title:
  performance: mm/percpu-internal.h: Re-layout pcpu_chunk to mitigate
  false sharing

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

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

  [Description]
When running UnixBench/Execl throughput case, false sharing is observed due 
to frequent read on base_addr and write on free_bytes, chunk_md.
UnixBench/Execl represents a class of workload where bash scripts are 
spawned frequently to do some short jobs. It will do system call on execl 
frequently, and execl will call mm_init to initialize mm_struct of the process. 
mm_init will call __percpu_counter_init for percpu_counters initialization. 
Then pcpu_alloc is called to read the base_addr of pcpu_chunk for memory 
allocation. Inside pcpu_alloc, it will call pcpu_alloc_area to allocate memory 
from a specified chunk. This function will update "free_bytes" and "chunk_md" 
to record the rest free bytes and other meta data for this chunk. 
Correspondingly, pcpu_free_area will also update these 2 members when free 
memory.

In current pcpu_chunk layout, `base_addr' is in the same cache line
  with `free_bytes' and `chunk_md', and `base_addr' is at the last 8
  bytes. This patch moves `bound_map' up to `base_addr', to let
  `base_addr' locate in a new cacheline.

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

Component(s):
  Performance and Scalability

  [Software Information]
Target Version:
  23.10
Target Kernel:
  6.5
Commit IDs:
  3a6358c0dbe6 percpu-internal/pcpu_chunk: re-layout pcpu_chunk structure 
to reduce false sharing
External Links:

  [Business Justification]

  [Testing guidance]

  [External ID]
OSVE-5160


  The following requested patch has been applied upstream for v6.5-rc1:

   - 3a6358c0dbe6 percpu-internal/pcpu_chunk: re-layout pcpu_chunk
  structure to reduce false sharing

  
https://github.com/torvalds/linux/commit/3a6358c0dbe6a286a4f4504ba392a6039a9fbd12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053152/+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

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1055.61~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-done-focal-linux-oracle-5.15'. If the
problem still exists, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-failed-focal-linux-oracle-5.15'.


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


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


** Tags added: kernel-spammed-focal-linux-oracle-5.15-v2 
verification-needed-focal-linux-oracle-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/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 Released
Status in linux source package in Mantic:
  Fix Released

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 2053251] Re: performance: Scheduler: ratelimit updating of load_avg

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
bluefield/5.15.0-1040.42 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-bluefield'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-failed-jammy-linux-bluefield'.


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


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


** Tags added: kernel-spammed-jammy-linux-bluefield-v2 
verification-needed-jammy-linux-bluefield

-- 
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 Released
Status in linux source package in Mantic:
  Fix Released

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 2053251] Re: performance: Scheduler: ratelimit updating of load_avg

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1052.58 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-done-jammy-linux-intel-iotg'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-failed-jammy-linux-intel-iotg'.


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


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


** Tags added: kernel-spammed-jammy-linux-intel-iotg-v2 
verification-needed-jammy-linux-intel-iotg

-- 
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 Released
Status in linux source package in Mantic:
  Fix Released

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 2053251] Re: performance: Scheduler: ratelimit updating of load_avg

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-raspi/6.5.0-1014.17
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-raspi' to 'verification-done-
mantic-linux-raspi'. If the problem still exists, change the tag
'verification-needed-mantic-linux-raspi' to 'verification-failed-mantic-
linux-raspi'.


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


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


** Tags added: kernel-spammed-mantic-linux-raspi-v2 
verification-needed-mantic-linux-raspi

-- 
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 Released
Status in linux source package in Mantic:
  Fix Released

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 2054094] Re: linux-tools-common: man page of usbip[d] is misplaced

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1055.61~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-done-focal-linux-oracle-5.15'. If the
problem still exists, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-failed-focal-linux-oracle-5.15'.


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


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


** Tags added: kernel-spammed-focal-linux-oracle-5.15-v2 
verification-needed-focal-linux-oracle-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/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 Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released
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 2054094] Re: linux-tools-common: man page of usbip[d] is misplaced

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
bluefield/5.15.0-1040.42 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-bluefield'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-failed-jammy-linux-bluefield'.


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


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


** Tags added: kernel-spammed-jammy-linux-bluefield-v2 
verification-needed-jammy-linux-bluefield

-- 
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 Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released
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 2054094] Re: linux-tools-common: man page of usbip[d] is misplaced

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1052.58 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-done-jammy-linux-intel-iotg'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-failed-jammy-linux-intel-iotg'.


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


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


** Tags added: kernel-spammed-jammy-linux-intel-iotg-v2 
verification-needed-jammy-linux-intel-iotg

-- 
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 Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released
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 2054699] Re: x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1055.61~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-done-focal-linux-oracle-5.15'. If the
problem still exists, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-failed-focal-linux-oracle-5.15'.


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


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


** Tags added: kernel-spammed-focal-linux-oracle-5.15-v2 
verification-needed-focal-linux-oracle-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 Released
Status in linux source package in Mantic:
  Fix Released

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 2054094] Re: linux-tools-common: man page of usbip[d] is misplaced

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-raspi/6.5.0-1014.17
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-raspi' to 'verification-done-
mantic-linux-raspi'. If the problem still exists, change the tag
'verification-needed-mantic-linux-raspi' to 'verification-failed-mantic-
linux-raspi'.


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


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


** Tags added: kernel-spammed-mantic-linux-raspi-v2 
verification-needed-mantic-linux-raspi

-- 
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 Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released
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 2054699] Re: x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1052.58 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-done-jammy-linux-intel-iotg'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-failed-jammy-linux-intel-iotg'.


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


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


** Tags added: kernel-spammed-jammy-linux-intel-iotg-v2 
verification-needed-jammy-linux-intel-iotg

-- 
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 Released
Status in linux source package in Mantic:
  Fix Released

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 2054567] Re: Fix bpf selftests build failure after v5.15.139 update

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1052.58 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-done-jammy-linux-intel-iotg'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-failed-jammy-linux-intel-iotg'.


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


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


** Tags added: kernel-spammed-jammy-linux-intel-iotg-v2 
verification-needed-jammy-linux-intel-iotg

-- 
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 Released

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 2054567] Re: Fix bpf selftests build failure after v5.15.139 update

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
bluefield/5.15.0-1040.42 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-bluefield'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-failed-jammy-linux-bluefield'.


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


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


** Tags added: kernel-spammed-jammy-linux-bluefield-v2 
verification-needed-jammy-linux-bluefield

-- 
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 Released

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 2054567] Re: Fix bpf selftests build failure after v5.15.139 update

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1055.61~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-done-focal-linux-oracle-5.15'. If the
problem still exists, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-failed-focal-linux-oracle-5.15'.


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


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


** Tags added: kernel-spammed-focal-linux-oracle-5.15-v2 
verification-needed-focal-linux-oracle-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/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 Released

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 2054699] Re: x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-raspi/6.5.0-1014.17
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-raspi' to 'verification-done-
mantic-linux-raspi'. If the problem still exists, change the tag
'verification-needed-mantic-linux-raspi' to 'verification-failed-mantic-
linux-raspi'.


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


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


** Tags added: kernel-spammed-mantic-linux-raspi-v2 
verification-needed-mantic-linux-raspi

-- 
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 Released
Status in linux source package in Mantic:
  Fix Released

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 2054699] Re: x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
bluefield/5.15.0-1040.42 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-bluefield'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-failed-jammy-linux-bluefield'.


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


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


** Tags added: kernel-spammed-jammy-linux-bluefield-v2 
verification-needed-jammy-linux-bluefield

-- 
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 Released
Status in linux source package in Mantic:
  Fix Released

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 2054809] Re: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1055.61~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-done-focal-linux-oracle-5.15'. If the
problem still exists, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-failed-focal-linux-oracle-5.15'.


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


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


** Tags added: kernel-spammed-focal-linux-oracle-5.15-v2 
verification-needed-focal-linux-oracle-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/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:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released
Status in linux source package in Noble:
  Fix Released

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 2054809] Re: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
bluefield/5.15.0-1040.42 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-bluefield'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-failed-jammy-linux-bluefield'.


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


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


** Tags added: kernel-spammed-jammy-linux-bluefield-v2 
verification-needed-jammy-linux-bluefield

-- 
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:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released
Status in linux source package in Noble:
  Fix Released

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 2054809] Re: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-raspi/6.5.0-1014.17
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-raspi' to 'verification-done-
mantic-linux-raspi'. If the problem still exists, change the tag
'verification-needed-mantic-linux-raspi' to 'verification-failed-mantic-
linux-raspi'.


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


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


** Tags added: kernel-spammed-mantic-linux-raspi-v2 
verification-needed-mantic-linux-raspi

-- 
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:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released
Status in linux source package in Noble:
  Fix Released

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 2054809] Re: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1052.58 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-done-jammy-linux-intel-iotg'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-failed-jammy-linux-intel-iotg'.


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


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


** Tags added: kernel-spammed-jammy-linux-intel-iotg-v2 
verification-needed-jammy-linux-intel-iotg

-- 
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:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released
Status in linux source package in Noble:
  Fix Released

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 2055685] Re: Cranky update-dkms-versions rollout

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1055.61~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-done-focal-linux-oracle-5.15'. If the
problem still exists, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-failed-focal-linux-oracle-5.15'.


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


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


** Tags added: kernel-spammed-focal-linux-oracle-5.15-v2 
verification-needed-focal-linux-oracle-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 Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released

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 2055685] Re: Cranky update-dkms-versions rollout

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
bluefield/5.15.0-1040.42 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-bluefield'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-failed-jammy-linux-bluefield'.


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


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


** Tags added: kernel-spammed-jammy-linux-bluefield-v2 
verification-needed-jammy-linux-bluefield

-- 
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 Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released

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 2055685] Re: Cranky update-dkms-versions rollout

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
bluefield/5.15.0-1040.42 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-bluefield'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-failed-jammy-linux-bluefield'.


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


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

-- 
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 Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released

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 2055685] Re: Cranky update-dkms-versions rollout

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1052.58 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-done-jammy-linux-intel-iotg'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-failed-jammy-linux-intel-iotg'.


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


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


** Tags added: kernel-spammed-jammy-linux-intel-iotg-v2 
verification-needed-jammy-linux-intel-iotg

-- 
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 Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released

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 2055685] Re: Cranky update-dkms-versions rollout

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-raspi/6.5.0-1014.17
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-raspi' to 'verification-done-
mantic-linux-raspi'. If the problem still exists, change the tag
'verification-needed-mantic-linux-raspi' to 'verification-failed-mantic-
linux-raspi'.


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


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


** Tags added: kernel-spammed-mantic-linux-raspi-v2 
verification-needed-mantic-linux-raspi

-- 
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 Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released

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 2055686] Re: Drop ABI checks from kernel build

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1055.61~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-done-focal-linux-oracle-5.15'. If the
problem still exists, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-failed-focal-linux-oracle-5.15'.


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


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


** Tags added: kernel-spammed-focal-linux-oracle-5.15-v2 
verification-needed-focal-linux-oracle-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/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 Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released

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 2055686] Re: Drop ABI checks from kernel build

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
bluefield/5.15.0-1040.42 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-bluefield'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-failed-jammy-linux-bluefield'.


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


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


** Tags added: kernel-spammed-jammy-linux-bluefield-v2 
verification-needed-jammy-linux-bluefield

-- 
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 Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released

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 2055686] Re: Drop ABI checks from kernel build

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1052.58 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-done-jammy-linux-intel-iotg'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-failed-jammy-linux-intel-iotg'.


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


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


** Tags added: kernel-spammed-jammy-linux-intel-iotg-v2 
verification-needed-jammy-linux-intel-iotg

-- 
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 Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released

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 2056143] Re: block/loop: No longer allows to create partitions

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
oracle-5.15/5.15.0-1055.61~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-done-focal-linux-oracle-5.15'. If the
problem still exists, change the tag 'verification-needed-focal-linux-
oracle-5.15' to 'verification-failed-focal-linux-oracle-5.15'.


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


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


** Tags added: kernel-spammed-focal-linux-oracle-5.15-v2 
verification-needed-focal-linux-oracle-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/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 Released

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 2055686] Re: Drop ABI checks from kernel build

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-raspi/6.5.0-1014.17
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-raspi' to 'verification-done-
mantic-linux-raspi'. If the problem still exists, change the tag
'verification-needed-mantic-linux-raspi' to 'verification-failed-mantic-
linux-raspi'.


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


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


** Tags added: kernel-spammed-mantic-linux-raspi-v2 
verification-needed-mantic-linux-raspi

-- 
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 Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released

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 2056143] Re: block/loop: No longer allows to create partitions

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-
bluefield/5.15.0-1040.42 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-done-jammy-linux-bluefield'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-bluefield' to
'verification-failed-jammy-linux-bluefield'.


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


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


** Tags added: kernel-spammed-jammy-linux-bluefield-v2 
verification-needed-jammy-linux-bluefield

-- 
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 Released

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 2056143] Re: block/loop: No longer allows to create partitions

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1052.58 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-done-jammy-linux-intel-iotg'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-intel-iotg' to
'verification-failed-jammy-linux-intel-iotg'.


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


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


** Tags added: kernel-spammed-jammy-linux-intel-iotg-v2 
verification-needed-jammy-linux-intel-iotg

-- 
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 Released

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 2051947] Re: Sound: Add rtl quirk of M70-Gen5

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-raspi/6.5.0-1014.17
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-raspi' to 'verification-done-
mantic-linux-raspi'. If the problem still exists, change the tag
'verification-needed-mantic-linux-raspi' to 'verification-failed-mantic-
linux-raspi'.


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


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


** Tags added: kernel-spammed-mantic-linux-raspi-v2 
verification-needed-mantic-linux-raspi

-- 
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 Released
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 2049634] Re: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-raspi/6.5.0-1014.17
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-raspi' to 'verification-done-
mantic-linux-raspi'. If the problem still exists, change the tag
'verification-needed-mantic-linux-raspi' to 'verification-failed-mantic-
linux-raspi'.


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


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


** Tags added: kernel-spammed-mantic-linux-raspi-v2 
verification-needed-mantic-linux-raspi

-- 
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:
  Fix Committed
Status in linux source package in Mantic:
  Fix Released
Status in linux source package in Noble:
  Fix Committed

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 

[Kernel-packages] [Bug 2051896] Re: Fix spurious wakeup caused by Cirque touchpad

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-raspi/6.5.0-1014.17
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-raspi' to 'verification-done-
mantic-linux-raspi'. If the problem still exists, change the tag
'verification-needed-mantic-linux-raspi' to 'verification-failed-mantic-
linux-raspi'.


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


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


** Tags added: kernel-spammed-mantic-linux-raspi-v2 
verification-needed-mantic-linux-raspi

-- 
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:
  Fix Released
Status in linux source package in Mantic:
  Fix Released
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


[Kernel-packages] [Bug 2052662] Re: move_mount mediation does not detect if source is detached

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-raspi/6.5.0-1014.17
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-raspi' to 'verification-done-
mantic-linux-raspi'. If the problem still exists, change the tag
'verification-needed-mantic-linux-raspi' to 'verification-failed-mantic-
linux-raspi'.


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


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


** Tags added: kernel-spammed-mantic-linux-raspi-v2 
verification-needed-mantic-linux-raspi

-- 
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/2052662

Title:
  move_mount mediation does not detect if source is detached

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

Bug description:
  Impact:

  In AppArmor mediation, detached mounts are appearing as / when
  applying mount mediation, which is incorrect and leads to bad
  AppArmor policy being generated.

  In addition, the move_mount mediation is not being advertised to
  userspace, which denies the applications the possibility to
  respond accordingly.

  Fix:

  Fixed upstream by commit 8026e40608b4d552216d2a818ca7080a4264bb44
  by preventing move_mont from applying the attach_disconnected
  flag.

  
  Testcase:

  Check if move_mount file is available in securityfs:

  $ cat /sys/kernel/security/apparmor/features/mount/move_mount 
  detached

  Run upstream AppArmor mount tests, which include move_mount mediation.
  
https://gitlab.com/apparmor/apparmor/-/blob/master/tests/regression/apparmor/mount.sh

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052662/+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 2054218] Re: kvm: Running perf against qemu processes results in page fault inside guest

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-raspi/6.5.0-1014.17
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-raspi' to 'verification-done-
mantic-linux-raspi'. If the problem still exists, change the tag
'verification-needed-mantic-linux-raspi' to 'verification-failed-mantic-
linux-raspi'.


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


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


** Tags added: kernel-spammed-mantic-linux-raspi-v2 
verification-needed-mantic-linux-raspi

-- 
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/2054218

Title:
  kvm: Running perf against qemu processes results in page fault inside
  guest

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

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

  [Impact]

  Running perf against a QEMU/kvm process results in the guest suffering
  a page fault in trying to store Precise Event Based Sampling (PEBS)
  records for the host. This affects both using perf against a single
  process, in which it crashes the targeted guest, or using perf system
  wide, in which it crashes all running guests on the system.

  The issue was introduced in 6.0 by:

  commit c59a1f106f5cd4843c097069ff1bb2ad72103a67
  Author: Like Xu 
  Date:   Mon Apr 11 18:19:36 2022 +0800
  Subject: KVM: x86/pmu: Add IA32_PEBS_ENABLE MSR emulation for extended PEBS
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c59a1f106f5cd4843c097069ff1bb2ad72103a67

  This affects all 6.2 and 6.5 kernels. There is no known workaround,
  apart from not using perf on affected systems.

  [Fix]

  The issue was fixed in 6.7 by:

  commit 971079464001c6856186ca137778e534d983174a
  Author: Paolo Bonzini 
  Date:   Thu Jan 4 16:15:17 2024 +0100
  Subject: KVM: x86/pmu: fix masking logic for MSR_CORE_PERF_GLOBAL_CTRL
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=971079464001c6856186ca137778e534d983174a

  This reinstates the logic for setting MSR_CORE_PERF_GLOBAL_CTRL to
  what it was before "KVM: x86/pmu: Add IA32_PEBS_ENABLE MSR emulation
  for extended PEBS".

  -   .guest = intel_ctrl & (~cpuc->intel_ctrl_host_mask | 
~pebs_mask),
  +   .guest = intel_ctrl & ~cpuc->intel_ctrl_host_mask & 
~pebs_mask,

  The faulty logic includes any bit that isn't both marked as
  exclude_guest and using PEBS, while it should really be excluding PEBS
  from the host.

  [Testcase]

  Start a bare metal server. Enable KVM, start a few VMs. The VMs can be
  idle, they don't require any workload.

  $ sudo apt-get install qemu-kvm libvirt-daemon-system libvirt-clients 
bridge-utils uvtool
  $ sudo reboot
  $ ssh-keygen
  $ uvt-simplestreams-libvirt sync --source 
http://cloud-images.ubuntu.com/daily release=jammy arch=amd64
  $ uvt-kvm create --cpu 4 --memory 4096 --disk 10 jammy-a release=jammy 
arch=amd64
  $ uvt-kvm create --cpu 4 --memory 4096 --disk 10 jammy-b release=jammy 
arch=amd64
  $ uvt-kvm create --cpu 4 --memory 4096 --disk 10 jammy-c release=jammy 
arch=amd64
  $ virsh list
   Id   Name  State
  -
   2jammy-a   running
   3jammy-b   running
   4jammy-c   running
  $ uvt-kvm ssh jammy-a
  Check it works.
  $ ps aux | grep qemu
  Find the pid of jammy-a
  $ perf top -p $PID
  $ virsh console jammy-a
  Escape character is ^] (Ctrl + ])
  [  357.793039] BUG: unable to handle page fault for address: fe49178c6028
  $ uvt-kvm ssh jammy-a
  (no response)

  Test packages are available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf379502-test

  If you install it, then running perf against the PID of qemu processes
  will no longer crash the guest, and they will be accessible by SSH
  afterward.

  [Where problems could occur]

  We are rearranging the logic of setting the PEBS MSRs, which affects
  processor sampling of events. This will affect any profiling tools
  running against KVM based virtual machines, namely perf against QEMU.

  If a regression were to occur, running perf against a VM could cause
  it to page fault and subsequently crash, resulting in downtime.

  The only workaround will be to disable all profiling tools until a fix
  is available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054218/+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 2055082] Re: IB peer memory feature regressed in 6.5

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-raspi/6.5.0-1014.17
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-raspi' to 'verification-done-
mantic-linux-raspi'. If the problem still exists, change the tag
'verification-needed-mantic-linux-raspi' to 'verification-failed-mantic-
linux-raspi'.


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


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


** Tags added: kernel-spammed-mantic-linux-raspi-v2 
verification-needed-mantic-linux-raspi

-- 
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/2055082

Title:
  IB peer memory feature regressed in 6.5

Status in linux package in Ubuntu:
  Won't Fix
Status in linux source package in Mantic:
  Fix Released

Bug description:
  [Impact]
  The GPU Direct over Infiniband feature of NVIDIA GPUs no longer works on 
jammy/hwe kernels that have migrated to 6.5 *except* for the -nvidia kernel, 
which pulled in support via bug 2049537.

  We have carried this patch since 5.4 (see bug 1923104). We do not plan
  to carry this patch into 6.8 or later - we are working on a
  deprecation post for that to give users some time to migrate.

  [Test Case]
  
https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests/tree/ubuntu_performance_gpudirect_rdma

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055082/+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 2054773] Re: Fix AMD brightness issue on AUO panel

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-raspi/6.5.0-1014.17
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-raspi' to 'verification-done-
mantic-linux-raspi'. If the problem still exists, change the tag
'verification-needed-mantic-linux-raspi' to 'verification-failed-mantic-
linux-raspi'.


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


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


** Tags added: kernel-spammed-mantic-linux-raspi-v2 
verification-needed-mantic-linux-raspi

-- 
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/2054773

Title:
  Fix AMD brightness issue on AUO panel

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:
  Won't Fix
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  When change brightness quickly on gnome menu,
  AUO panel will be stuck in previous brightness.

  [Fix]
  The TCON is random hung by PSR-SU.
  Force enable ffu mode on PSR-SU panel.

  [Test]
  Tested on hardware, the brightness is changed as expected.

  [Where problems could occur]
  It may break AMD display.

  The commit is already in v6.8-rc5, 
  the platform is not fully supported in Jammy 5.15,
  So SRU oem-6.5 and mantic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2054773/+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()

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-aws - 6.5.0-1017.17

---
linux-aws (6.5.0-1017.17) mantic; urgency=medium

  * mantic/linux-aws: 6.5.0-1017.17 -proposed tracker (LP: #2055564)

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- debian.aws/dkms-versions -- update from kernel-versions (main/2024.03.04)

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * aws: Backport latest ENA driver in upstream Linux to enable IRQ moderation
(LP: #2056475)
- net: ena: Enable DIM by default

  * tcp: Add memory barrier to tcp_push() (LP: #2051727)
- tcp: Add memory barrier to tcp_push()

  [ Ubuntu: 6.5.0-27.28 ]

  * mantic/linux: 6.5.0-27.28 -proposed tracker (LP: #2055584)
  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)
  * CVE-2024-26597
- net: qualcomm: rmnet: fix global oob in rmnet_policy
  * CVE-2024-26599
- pwm: Fix out-of-bounds access in of_pwm_single_xlate()
  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks
  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions
  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra
  * performance: Scheduler: ratelimit updating of load_avg (LP: #2053251)
- sched/fair: Ratelimit update to tg->load_avg
  * IB peer memory feature regressed in 6.5 (LP: #2055082)
- SAUCE: RDMA/core: Introduce peer memory interface
  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory
  * CVE-2024-23851
- dm: limit the number of targets and parameter size area
  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read
  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform
  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules
  * Fix AMD brightness issue on AUO panel (LP: #2054773)
- drm/amdgpu: make damage clips support configurable
  * Mantic update: upstream stable patchset 2024-02-28 (LP: #2055199)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- wifi: avoid offset calculation on NULL pointer
- wifi: mac80211: handle 320 MHz in ieee80211_ht_cap_ie_to_sta_ht_cap
- debugfs: fix automount d_fsdata usage
- nvme-core: fix a memory leak in nvme_ns_info_from_identify()
- drm/amd/display: update dcn315 lpddr pstate latency
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- smb: client, common: fix fortify warnings
- blk-mq: don't count completed flush data request as inflight in case of
  quiesce
- nvme-core: check for too small lba shift
- hwtracing: hisi_ptt: Handle the interrupt in hardirq context
- hwtracing: hisi_ptt: Don't try to attach a task
- ASoC: wm8974: Correct boost mixer inputs
- arm64: dts: rockchip: fix rk356x pcie msg interrupt name
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- ASoC: Intel: skl_hda_dsp_generic: Drop HDMI routes when HDMI is not
  available
- nouveau/tu102: flush all pdbs on vmm flush
- ASoC: amd: yc: Add DMI entry to support System76 Pangolin 13
- ASoC: hdac_hda: Conditionally register dais for HDMI and Analog
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- nvme: introduce helper 

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

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-iot/5.4.0-1034.35
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-iot' to 'verification-done-focal-
linux-iot'. If the problem still exists, change the tag 'verification-
needed-focal-linux-iot' to 'verification-failed-focal-linux-iot'.


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


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


** Tags added: kernel-spammed-focal-linux-iot-v2 
verification-needed-focal-linux-iot

-- 
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 Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released
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 2055685] Re: Cranky update-dkms-versions rollout

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-iot/5.4.0-1034.35
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-iot' to 'verification-done-focal-
linux-iot'. If the problem still exists, change the tag 'verification-
needed-focal-linux-iot' to 'verification-failed-focal-linux-iot'.


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


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


** Tags added: kernel-spammed-focal-linux-iot-v2 
verification-needed-focal-linux-iot

-- 
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 Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released

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 2055686] Re: Drop ABI checks from kernel build

2024-04-07 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the linux-iot/5.4.0-1034.35
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal-linux-iot' to 'verification-done-focal-
linux-iot'. If the problem still exists, change the tag 'verification-
needed-focal-linux-iot' to 'verification-failed-focal-linux-iot'.


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


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


** Tags added: kernel-spammed-focal-linux-iot-v2 
verification-needed-focal-linux-iot

-- 
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 Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released

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 2056475] Re: aws: Backport latest ENA driver in upstream Linux to enable IRQ moderation

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-aws - 6.5.0-1017.17

---
linux-aws (6.5.0-1017.17) mantic; urgency=medium

  * mantic/linux-aws: 6.5.0-1017.17 -proposed tracker (LP: #2055564)

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- debian.aws/dkms-versions -- update from kernel-versions (main/2024.03.04)

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * aws: Backport latest ENA driver in upstream Linux to enable IRQ moderation
(LP: #2056475)
- net: ena: Enable DIM by default

  * tcp: Add memory barrier to tcp_push() (LP: #2051727)
- tcp: Add memory barrier to tcp_push()

  [ Ubuntu: 6.5.0-27.28 ]

  * mantic/linux: 6.5.0-27.28 -proposed tracker (LP: #2055584)
  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)
  * CVE-2024-26597
- net: qualcomm: rmnet: fix global oob in rmnet_policy
  * CVE-2024-26599
- pwm: Fix out-of-bounds access in of_pwm_single_xlate()
  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks
  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions
  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra
  * performance: Scheduler: ratelimit updating of load_avg (LP: #2053251)
- sched/fair: Ratelimit update to tg->load_avg
  * IB peer memory feature regressed in 6.5 (LP: #2055082)
- SAUCE: RDMA/core: Introduce peer memory interface
  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory
  * CVE-2024-23851
- dm: limit the number of targets and parameter size area
  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read
  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform
  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules
  * Fix AMD brightness issue on AUO panel (LP: #2054773)
- drm/amdgpu: make damage clips support configurable
  * Mantic update: upstream stable patchset 2024-02-28 (LP: #2055199)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- wifi: avoid offset calculation on NULL pointer
- wifi: mac80211: handle 320 MHz in ieee80211_ht_cap_ie_to_sta_ht_cap
- debugfs: fix automount d_fsdata usage
- nvme-core: fix a memory leak in nvme_ns_info_from_identify()
- drm/amd/display: update dcn315 lpddr pstate latency
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- smb: client, common: fix fortify warnings
- blk-mq: don't count completed flush data request as inflight in case of
  quiesce
- nvme-core: check for too small lba shift
- hwtracing: hisi_ptt: Handle the interrupt in hardirq context
- hwtracing: hisi_ptt: Don't try to attach a task
- ASoC: wm8974: Correct boost mixer inputs
- arm64: dts: rockchip: fix rk356x pcie msg interrupt name
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- ASoC: Intel: skl_hda_dsp_generic: Drop HDMI routes when HDMI is not
  available
- nouveau/tu102: flush all pdbs on vmm flush
- ASoC: amd: yc: Add DMI entry to support System76 Pangolin 13
- ASoC: hdac_hda: Conditionally register dais for HDMI and Analog
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- nvme: introduce helper 

[Kernel-packages] [Bug 2039720] Re: Intel IDPF support

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-gke - 5.15.0-1054.59

---
linux-gke (5.15.0-1054.59) jammy; urgency=medium

  * jammy/linux-gke: 5.15.0-1054.59 -proposed tracker (LP: #2055601)

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- debian.gke/dkms-versions -- update from kernel-versions (main/2024.03.04)

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * Intel IDPF support (LP: #2039720)
- idpf: add module register and probe functionality
- idpf: add controlq init and reset checks
- idpf: add core init and interrupt request
- idpf: add create vport and netdev configuration
- idpf: add ptypes and MAC filter support
- idpf: configure resources for TX queues
- idpf: configure resources for RX queues
- idpf: initialize interrupts and enable vport
- idpf: add splitq start_xmit
- idpf: add TX splitq napi poll support
- idpf: add RX splitq napi poll support
- idpf: add singleq start_xmit and napi poll
- idpf: add ethtool callbacks
- idpf: add SRIOV support and other ndo_ops
- virtchnl: add virtchnl version 2 ops
- u64_stats: Introduce u64_stats_set()
- [Config] gcp: Adding support for IDPF driver

  [ Ubuntu: 5.15.0-102.112 ]

  * jammy/linux: 5.15.0-102.112 -proposed tracker (LP: #2055632)
  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks
- [Packaging] Drop abi checks from final-checks
  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)
  * block/loop: No longer allows to create partitions (LP: #2056143)
- block, loop: support partitions without scanning
  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions
- [Packaging] remove update-version-dkms
  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra
  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory
  * CVE-2024-23851
- dm ioctl: log an error if the ioctl structure is corrupted
- dm: limit the number of targets and parameter size area
  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read
  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform
  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules
  * Fix bpf selftests build failure after v5.15.139 update (LP: #2054567)
- Revert "selftests/bpf: Test tail call counting with bpf2bpf and data on
  stack"
  * Jammy update: v5.15.148 upstream stable release (LP: #2055145)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- debugfs: fix automount d_fsdata usage
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- nvme-core: check for too small lba shift
- ASoC: wm8974: Correct boost mixer inputs
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- nouveau/tu102: flush all pdbs on vmm flush
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- ASoC: ops: add correct range check for limiting volume
- nvme: introduce helper function to get ctrl state
- drm/amdgpu: Add NULL checks for function pointers
- drm/exynos: fix a potential error pointer dereference
- drm/exynos: fix a wrong error checking
- hwmon: (corsair-psu) Fix 

[Kernel-packages] [Bug 2057936] Re: Azure: hv: hyperv.h: Replace one-element array with flexible-array member

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-azure - 6.5.0-1018.19

---
linux-azure (6.5.0-1018.19) mantic; urgency=medium

  * mantic/linux-azure: 6.5.0-1018.19 -proposed tracker (LP: #2055566)

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Azure: Include erofs in linux-modules instead of 
linux-
  modules-extra

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- debian.azure/dkms-versions -- update from kernel-versions 
(main/2024.03.04)

  * Azure: hv: hyperv.h: Replace one-element array with flexible-array member
(LP: #2057936)
- hv: hyperv.h: Replace one-element array with flexible-array member

  [ Ubuntu: 6.5.0-27.28 ]

  * mantic/linux: 6.5.0-27.28 -proposed tracker (LP: #2055584)
  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)
  * CVE-2024-26597
- net: qualcomm: rmnet: fix global oob in rmnet_policy
  * CVE-2024-26599
- pwm: Fix out-of-bounds access in of_pwm_single_xlate()
  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks
  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions
  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra
  * performance: Scheduler: ratelimit updating of load_avg (LP: #2053251)
- sched/fair: Ratelimit update to tg->load_avg
  * IB peer memory feature regressed in 6.5 (LP: #2055082)
- SAUCE: RDMA/core: Introduce peer memory interface
  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory
  * CVE-2024-23851
- dm: limit the number of targets and parameter size area
  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read
  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform
  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules
  * Fix AMD brightness issue on AUO panel (LP: #2054773)
- drm/amdgpu: make damage clips support configurable
  * Mantic update: upstream stable patchset 2024-02-28 (LP: #2055199)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- wifi: avoid offset calculation on NULL pointer
- wifi: mac80211: handle 320 MHz in ieee80211_ht_cap_ie_to_sta_ht_cap
- debugfs: fix automount d_fsdata usage
- nvme-core: fix a memory leak in nvme_ns_info_from_identify()
- drm/amd/display: update dcn315 lpddr pstate latency
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- smb: client, common: fix fortify warnings
- blk-mq: don't count completed flush data request as inflight in case of
  quiesce
- nvme-core: check for too small lba shift
- hwtracing: hisi_ptt: Handle the interrupt in hardirq context
- hwtracing: hisi_ptt: Don't try to attach a task
- ASoC: wm8974: Correct boost mixer inputs
- arm64: dts: rockchip: fix rk356x pcie msg interrupt name
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- ASoC: Intel: skl_hda_dsp_generic: Drop HDMI routes when HDMI is not
  available
- nouveau/tu102: flush all pdbs on vmm flush
- ASoC: amd: yc: Add DMI entry to support System76 Pangolin 13
- ASoC: hdac_hda: Conditionally register dais for HDMI and Analog
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- nvme: introduce helper function to get ctrl state
- nvme: prevent potential spectre v1 gadget
- arm64: dts: rockchip: Fix PCI node addresses on rk3399-gru
- drm/amdgpu: Add NULL checks for function pointers
- drm/exynos: fix a potential error pointer 

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

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 6.5.0-27.28

---
linux (6.5.0-27.28) mantic; urgency=medium

  * mantic/linux: 6.5.0-27.28 -proposed tracker (LP: #2055584)

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)

  * CVE-2024-26597
- net: qualcomm: rmnet: fix global oob in rmnet_policy

  * CVE-2024-26599
- pwm: Fix out-of-bounds access in of_pwm_single_xlate()

  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks

  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * performance: Scheduler: ratelimit updating of load_avg (LP: #2053251)
- sched/fair: Ratelimit update to tg->load_avg

  * IB peer memory feature regressed in 6.5 (LP: #2055082)
- SAUCE: RDMA/core: Introduce peer memory interface

  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory

  * CVE-2024-23851
- dm: limit the number of targets and parameter size area

  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read

  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * Fix AMD brightness issue on AUO panel (LP: #2054773)
- drm/amdgpu: make damage clips support configurable

  * Mantic update: upstream stable patchset 2024-02-28 (LP: #2055199)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- wifi: avoid offset calculation on NULL pointer
- wifi: mac80211: handle 320 MHz in ieee80211_ht_cap_ie_to_sta_ht_cap
- debugfs: fix automount d_fsdata usage
- nvme-core: fix a memory leak in nvme_ns_info_from_identify()
- drm/amd/display: update dcn315 lpddr pstate latency
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- smb: client, common: fix fortify warnings
- blk-mq: don't count completed flush data request as inflight in case of
  quiesce
- nvme-core: check for too small lba shift
- hwtracing: hisi_ptt: Handle the interrupt in hardirq context
- hwtracing: hisi_ptt: Don't try to attach a task
- ASoC: wm8974: Correct boost mixer inputs
- arm64: dts: rockchip: fix rk356x pcie msg interrupt name
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- ASoC: Intel: skl_hda_dsp_generic: Drop HDMI routes when HDMI is not
  available
- nouveau/tu102: flush all pdbs on vmm flush
- ASoC: amd: yc: Add DMI entry to support System76 Pangolin 13
- ASoC: hdac_hda: Conditionally register dais for HDMI and Analog
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- nvme: introduce helper function to get ctrl state
- nvme: prevent potential spectre v1 gadget
- arm64: dts: rockchip: Fix PCI node addresses on rk3399-gru
- drm/amdgpu: Add NULL checks for function pointers
- drm/exynos: fix a potential error pointer dereference
- drm/exynos: fix a wrong error checking
- hwmon: (corsair-psu) Fix probe when built-in
- LoongArch: Preserve syscall nr across execve()
- clk: rockchip: rk3568: Add PLL rate for 292.5MHz
- clk: rockchip: rk3128: Fix HCLK_OTG gate register
- jbd2: correct the printing of write_flags in jbd2_write_superblock()
- jbd2: increase the journal IO's priority
- drm/crtc: Fix uninit-value bug in drm_mode_setcrtc
- neighbour: Don't let neigh_forced_gc() disable preemption for long
- platform/x86: intel-vbtn: Fix missing tablet-mode-switch events
- jbd2: fix soft lockup in 

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

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.15.0-102.112

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

  * jammy/linux: 5.15.0-102.112 -proposed tracker (LP: #2055632)

  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks
- [Packaging] Drop abi checks from final-checks

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)

  * block/loop: No longer allows to create partitions (LP: #2056143)
- block, loop: support partitions without scanning

  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions
- [Packaging] remove update-version-dkms

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory

  * CVE-2024-23851
- dm ioctl: log an error if the ioctl structure is corrupted
- dm: limit the number of targets and parameter size area

  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read

  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * Fix bpf selftests build failure after v5.15.139 update (LP: #2054567)
- Revert "selftests/bpf: Test tail call counting with bpf2bpf and data on
  stack"

  * Jammy update: v5.15.148 upstream stable release (LP: #2055145)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- debugfs: fix automount d_fsdata usage
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- nvme-core: check for too small lba shift
- ASoC: wm8974: Correct boost mixer inputs
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- nouveau/tu102: flush all pdbs on vmm flush
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- ASoC: ops: add correct range check for limiting volume
- nvme: introduce helper function to get ctrl state
- drm/amdgpu: Add NULL checks for function pointers
- drm/exynos: fix a potential error pointer dereference
- drm/exynos: fix a wrong error checking
- hwmon: (corsair-psu) Fix probe when built-in
- clk: rockchip: rk3128: Fix HCLK_OTG gate register
- jbd2: correct the printing of write_flags in jbd2_write_superblock()
- drm/crtc: Fix uninit-value bug in drm_mode_setcrtc
- neighbour: Don't let neigh_forced_gc() disable preemption for long
- platform/x86: intel-vbtn: Fix missing tablet-mode-switch events
- jbd2: fix soft lockup in journal_finish_inode_data_buffers()
- tracing: Have large events show up as '[LINE TOO BIG]' instead of nothing
- tracing: Add size check when printing trace_marker output
- stmmac: dwmac-loongson: drop useless check for compatible fallback
- MIPS: dts: loongson: drop incorrect dwmac fallback compatible
- tracing: Fix uaf issue when open the hist or hist_debug file
- ring-buffer: Do not record in NMI if the arch does not support cmpxchg in
  NMI
- reset: hisilicon: hi6220: fix Wvoid-pointer-to-enum-cast warning
- Input: atkbd - skip ATKBD_CMD_GETID in translated mode
- Input: i8042 - add nomux quirk for Acer P459-G2-M
- s390/scm: fix virtual vs physical address confusion
- ARC: fix spare error
- wifi: iwlwifi: pcie: avoid a NULL pointer dereference
- Input: xpad - add Razer Wolverine V2 support
- ASoC: Intel: bytcr_rt5640: Add quirk for the Medion Lifetab S10346
- i2c: rk3x: fix potential spinlock recursion on poll
- net: qrtr: ns: Return 0 if server port is not present
- ARM: sun9i: smp: fix return code check of 

[Kernel-packages] [Bug 2048077] Re: Migrate oem-6.1 to oem-6.5

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-meta-oem-6.5 - 6.5.0.1019.21

---
linux-meta-oem-6.5 (6.5.0.1019.21) jammy; urgency=medium

  * Bump ABI 6.5.0-1019

  * Packaging resync (LP: #1786013)
- [Packaging] remove update-version script

  * Migrate oem-6.1 to oem-6.5 (LP: #2048077)
- [Packaging] Migrate oem-22.04a/b/c to oem-22.04d

  * Miscellaneous Ubuntu changes
- debian/dkms-versions -- update from main

 -- Timo Aaltonen   Mon, 18 Mar 2024
18:00:34 +0200

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

Title:
  Migrate oem-6.1 to oem-6.5

Status in linux-meta-oem-6.5 package in Ubuntu:
  Invalid
Status in linux-restricted-modules-oem-6.5 package in Ubuntu:
  Invalid
Status in linux-meta-oem-6.5 source package in Jammy:
  Fix Released
Status in linux-restricted-modules-oem-6.5 source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  Migrate oem-6.1 to oem-6.5, because some platforms need it instead of hwe-6.5.

  
  [Test case]
  Update a machine with oem-6.1 metapackages to the proposed ones, and verify 
that all packages (including nvidia etc) migrate properly.

  [Where things could go wrong]
  In theory we might miss a package to transition, but at this point this is 
unlikely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-6.5/+bug/2048077/+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 2048077] Re: Migrate oem-6.1 to oem-6.5

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-restricted-modules-oem-6.5 -
6.5.0-1019.20+1

---
linux-restricted-modules-oem-6.5 (6.5.0-1019.20+1) jammy; urgency=medium

  * Migrate oem-6.1 to oem-6.5 (LP: #2048077)
- [Packaging] Migrate nvidia 545 too.

  * Packaging resync (LP: #1786013)
- [Packaging] update variants

 -- Timo Aaltonen   Wed, 27 Mar 2024
10:40:44 +0200

** Changed in: linux-restricted-modules-oem-6.5 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

** Changed in: linux-meta-oem-6.5 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Migrate oem-6.1 to oem-6.5

Status in linux-meta-oem-6.5 package in Ubuntu:
  Invalid
Status in linux-restricted-modules-oem-6.5 package in Ubuntu:
  Invalid
Status in linux-meta-oem-6.5 source package in Jammy:
  Fix Released
Status in linux-restricted-modules-oem-6.5 source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  Migrate oem-6.1 to oem-6.5, because some platforms need it instead of hwe-6.5.

  
  [Test case]
  Update a machine with oem-6.1 metapackages to the proposed ones, and verify 
that all packages (including nvidia etc) migrate properly.

  [Where things could go wrong]
  In theory we might miss a package to transition, but at this point this is 
unlikely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-6.5/+bug/2048077/+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 2049634] Re: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 6.5.0-27.28

---
linux (6.5.0-27.28) mantic; urgency=medium

  * mantic/linux: 6.5.0-27.28 -proposed tracker (LP: #2055584)

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)

  * CVE-2024-26597
- net: qualcomm: rmnet: fix global oob in rmnet_policy

  * CVE-2024-26599
- pwm: Fix out-of-bounds access in of_pwm_single_xlate()

  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks

  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * performance: Scheduler: ratelimit updating of load_avg (LP: #2053251)
- sched/fair: Ratelimit update to tg->load_avg

  * IB peer memory feature regressed in 6.5 (LP: #2055082)
- SAUCE: RDMA/core: Introduce peer memory interface

  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory

  * CVE-2024-23851
- dm: limit the number of targets and parameter size area

  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read

  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * Fix AMD brightness issue on AUO panel (LP: #2054773)
- drm/amdgpu: make damage clips support configurable

  * Mantic update: upstream stable patchset 2024-02-28 (LP: #2055199)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- wifi: avoid offset calculation on NULL pointer
- wifi: mac80211: handle 320 MHz in ieee80211_ht_cap_ie_to_sta_ht_cap
- debugfs: fix automount d_fsdata usage
- nvme-core: fix a memory leak in nvme_ns_info_from_identify()
- drm/amd/display: update dcn315 lpddr pstate latency
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- smb: client, common: fix fortify warnings
- blk-mq: don't count completed flush data request as inflight in case of
  quiesce
- nvme-core: check for too small lba shift
- hwtracing: hisi_ptt: Handle the interrupt in hardirq context
- hwtracing: hisi_ptt: Don't try to attach a task
- ASoC: wm8974: Correct boost mixer inputs
- arm64: dts: rockchip: fix rk356x pcie msg interrupt name
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- ASoC: Intel: skl_hda_dsp_generic: Drop HDMI routes when HDMI is not
  available
- nouveau/tu102: flush all pdbs on vmm flush
- ASoC: amd: yc: Add DMI entry to support System76 Pangolin 13
- ASoC: hdac_hda: Conditionally register dais for HDMI and Analog
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- nvme: introduce helper function to get ctrl state
- nvme: prevent potential spectre v1 gadget
- arm64: dts: rockchip: Fix PCI node addresses on rk3399-gru
- drm/amdgpu: Add NULL checks for function pointers
- drm/exynos: fix a potential error pointer dereference
- drm/exynos: fix a wrong error checking
- hwmon: (corsair-psu) Fix probe when built-in
- LoongArch: Preserve syscall nr across execve()
- clk: rockchip: rk3568: Add PLL rate for 292.5MHz
- clk: rockchip: rk3128: Fix HCLK_OTG gate register
- jbd2: correct the printing of write_flags in jbd2_write_superblock()
- jbd2: increase the journal IO's priority
- drm/crtc: Fix uninit-value bug in drm_mode_setcrtc
- neighbour: Don't let neigh_forced_gc() disable preemption for long
- platform/x86: intel-vbtn: Fix missing tablet-mode-switch events
- jbd2: fix soft lockup in 

[Kernel-packages] [Bug 2051896] Re: Fix spurious wakeup caused by Cirque touchpad

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 6.5.0-27.28

---
linux (6.5.0-27.28) mantic; urgency=medium

  * mantic/linux: 6.5.0-27.28 -proposed tracker (LP: #2055584)

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)

  * CVE-2024-26597
- net: qualcomm: rmnet: fix global oob in rmnet_policy

  * CVE-2024-26599
- pwm: Fix out-of-bounds access in of_pwm_single_xlate()

  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks

  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * performance: Scheduler: ratelimit updating of load_avg (LP: #2053251)
- sched/fair: Ratelimit update to tg->load_avg

  * IB peer memory feature regressed in 6.5 (LP: #2055082)
- SAUCE: RDMA/core: Introduce peer memory interface

  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory

  * CVE-2024-23851
- dm: limit the number of targets and parameter size area

  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read

  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * Fix AMD brightness issue on AUO panel (LP: #2054773)
- drm/amdgpu: make damage clips support configurable

  * Mantic update: upstream stable patchset 2024-02-28 (LP: #2055199)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- wifi: avoid offset calculation on NULL pointer
- wifi: mac80211: handle 320 MHz in ieee80211_ht_cap_ie_to_sta_ht_cap
- debugfs: fix automount d_fsdata usage
- nvme-core: fix a memory leak in nvme_ns_info_from_identify()
- drm/amd/display: update dcn315 lpddr pstate latency
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- smb: client, common: fix fortify warnings
- blk-mq: don't count completed flush data request as inflight in case of
  quiesce
- nvme-core: check for too small lba shift
- hwtracing: hisi_ptt: Handle the interrupt in hardirq context
- hwtracing: hisi_ptt: Don't try to attach a task
- ASoC: wm8974: Correct boost mixer inputs
- arm64: dts: rockchip: fix rk356x pcie msg interrupt name
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- ASoC: Intel: skl_hda_dsp_generic: Drop HDMI routes when HDMI is not
  available
- nouveau/tu102: flush all pdbs on vmm flush
- ASoC: amd: yc: Add DMI entry to support System76 Pangolin 13
- ASoC: hdac_hda: Conditionally register dais for HDMI and Analog
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- nvme: introduce helper function to get ctrl state
- nvme: prevent potential spectre v1 gadget
- arm64: dts: rockchip: Fix PCI node addresses on rk3399-gru
- drm/amdgpu: Add NULL checks for function pointers
- drm/exynos: fix a potential error pointer dereference
- drm/exynos: fix a wrong error checking
- hwmon: (corsair-psu) Fix probe when built-in
- LoongArch: Preserve syscall nr across execve()
- clk: rockchip: rk3568: Add PLL rate for 292.5MHz
- clk: rockchip: rk3128: Fix HCLK_OTG gate register
- jbd2: correct the printing of write_flags in jbd2_write_superblock()
- jbd2: increase the journal IO's priority
- drm/crtc: Fix uninit-value bug in drm_mode_setcrtc
- neighbour: Don't let neigh_forced_gc() disable preemption for long
- platform/x86: intel-vbtn: Fix missing tablet-mode-switch events
- jbd2: fix soft lockup in 

[Kernel-packages] [Bug 2051924] Re: Mantic update: upstream stable patchset 2024-02-01

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 6.5.0-27.28

---
linux (6.5.0-27.28) mantic; urgency=medium

  * mantic/linux: 6.5.0-27.28 -proposed tracker (LP: #2055584)

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)

  * CVE-2024-26597
- net: qualcomm: rmnet: fix global oob in rmnet_policy

  * CVE-2024-26599
- pwm: Fix out-of-bounds access in of_pwm_single_xlate()

  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks

  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * performance: Scheduler: ratelimit updating of load_avg (LP: #2053251)
- sched/fair: Ratelimit update to tg->load_avg

  * IB peer memory feature regressed in 6.5 (LP: #2055082)
- SAUCE: RDMA/core: Introduce peer memory interface

  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory

  * CVE-2024-23851
- dm: limit the number of targets and parameter size area

  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read

  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * Fix AMD brightness issue on AUO panel (LP: #2054773)
- drm/amdgpu: make damage clips support configurable

  * Mantic update: upstream stable patchset 2024-02-28 (LP: #2055199)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- wifi: avoid offset calculation on NULL pointer
- wifi: mac80211: handle 320 MHz in ieee80211_ht_cap_ie_to_sta_ht_cap
- debugfs: fix automount d_fsdata usage
- nvme-core: fix a memory leak in nvme_ns_info_from_identify()
- drm/amd/display: update dcn315 lpddr pstate latency
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- smb: client, common: fix fortify warnings
- blk-mq: don't count completed flush data request as inflight in case of
  quiesce
- nvme-core: check for too small lba shift
- hwtracing: hisi_ptt: Handle the interrupt in hardirq context
- hwtracing: hisi_ptt: Don't try to attach a task
- ASoC: wm8974: Correct boost mixer inputs
- arm64: dts: rockchip: fix rk356x pcie msg interrupt name
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- ASoC: Intel: skl_hda_dsp_generic: Drop HDMI routes when HDMI is not
  available
- nouveau/tu102: flush all pdbs on vmm flush
- ASoC: amd: yc: Add DMI entry to support System76 Pangolin 13
- ASoC: hdac_hda: Conditionally register dais for HDMI and Analog
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- nvme: introduce helper function to get ctrl state
- nvme: prevent potential spectre v1 gadget
- arm64: dts: rockchip: Fix PCI node addresses on rk3399-gru
- drm/amdgpu: Add NULL checks for function pointers
- drm/exynos: fix a potential error pointer dereference
- drm/exynos: fix a wrong error checking
- hwmon: (corsair-psu) Fix probe when built-in
- LoongArch: Preserve syscall nr across execve()
- clk: rockchip: rk3568: Add PLL rate for 292.5MHz
- clk: rockchip: rk3128: Fix HCLK_OTG gate register
- jbd2: correct the printing of write_flags in jbd2_write_superblock()
- jbd2: increase the journal IO's priority
- drm/crtc: Fix uninit-value bug in drm_mode_setcrtc
- neighbour: Don't let neigh_forced_gc() disable preemption for long
- platform/x86: intel-vbtn: Fix missing tablet-mode-switch events
- jbd2: fix soft lockup in 

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

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 6.5.0-27.28

---
linux (6.5.0-27.28) mantic; urgency=medium

  * mantic/linux: 6.5.0-27.28 -proposed tracker (LP: #2055584)

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)

  * CVE-2024-26597
- net: qualcomm: rmnet: fix global oob in rmnet_policy

  * CVE-2024-26599
- pwm: Fix out-of-bounds access in of_pwm_single_xlate()

  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks

  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * performance: Scheduler: ratelimit updating of load_avg (LP: #2053251)
- sched/fair: Ratelimit update to tg->load_avg

  * IB peer memory feature regressed in 6.5 (LP: #2055082)
- SAUCE: RDMA/core: Introduce peer memory interface

  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory

  * CVE-2024-23851
- dm: limit the number of targets and parameter size area

  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read

  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * Fix AMD brightness issue on AUO panel (LP: #2054773)
- drm/amdgpu: make damage clips support configurable

  * Mantic update: upstream stable patchset 2024-02-28 (LP: #2055199)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- wifi: avoid offset calculation on NULL pointer
- wifi: mac80211: handle 320 MHz in ieee80211_ht_cap_ie_to_sta_ht_cap
- debugfs: fix automount d_fsdata usage
- nvme-core: fix a memory leak in nvme_ns_info_from_identify()
- drm/amd/display: update dcn315 lpddr pstate latency
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- smb: client, common: fix fortify warnings
- blk-mq: don't count completed flush data request as inflight in case of
  quiesce
- nvme-core: check for too small lba shift
- hwtracing: hisi_ptt: Handle the interrupt in hardirq context
- hwtracing: hisi_ptt: Don't try to attach a task
- ASoC: wm8974: Correct boost mixer inputs
- arm64: dts: rockchip: fix rk356x pcie msg interrupt name
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- ASoC: Intel: skl_hda_dsp_generic: Drop HDMI routes when HDMI is not
  available
- nouveau/tu102: flush all pdbs on vmm flush
- ASoC: amd: yc: Add DMI entry to support System76 Pangolin 13
- ASoC: hdac_hda: Conditionally register dais for HDMI and Analog
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- nvme: introduce helper function to get ctrl state
- nvme: prevent potential spectre v1 gadget
- arm64: dts: rockchip: Fix PCI node addresses on rk3399-gru
- drm/amdgpu: Add NULL checks for function pointers
- drm/exynos: fix a potential error pointer dereference
- drm/exynos: fix a wrong error checking
- hwmon: (corsair-psu) Fix probe when built-in
- LoongArch: Preserve syscall nr across execve()
- clk: rockchip: rk3568: Add PLL rate for 292.5MHz
- clk: rockchip: rk3128: Fix HCLK_OTG gate register
- jbd2: correct the printing of write_flags in jbd2_write_superblock()
- jbd2: increase the journal IO's priority
- drm/crtc: Fix uninit-value bug in drm_mode_setcrtc
- neighbour: Don't let neigh_forced_gc() disable preemption for long
- platform/x86: intel-vbtn: Fix missing tablet-mode-switch events
- jbd2: fix soft lockup in 

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

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 6.5.0-27.28

---
linux (6.5.0-27.28) mantic; urgency=medium

  * mantic/linux: 6.5.0-27.28 -proposed tracker (LP: #2055584)

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)

  * CVE-2024-26597
- net: qualcomm: rmnet: fix global oob in rmnet_policy

  * CVE-2024-26599
- pwm: Fix out-of-bounds access in of_pwm_single_xlate()

  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks

  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * performance: Scheduler: ratelimit updating of load_avg (LP: #2053251)
- sched/fair: Ratelimit update to tg->load_avg

  * IB peer memory feature regressed in 6.5 (LP: #2055082)
- SAUCE: RDMA/core: Introduce peer memory interface

  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory

  * CVE-2024-23851
- dm: limit the number of targets and parameter size area

  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read

  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * Fix AMD brightness issue on AUO panel (LP: #2054773)
- drm/amdgpu: make damage clips support configurable

  * Mantic update: upstream stable patchset 2024-02-28 (LP: #2055199)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- wifi: avoid offset calculation on NULL pointer
- wifi: mac80211: handle 320 MHz in ieee80211_ht_cap_ie_to_sta_ht_cap
- debugfs: fix automount d_fsdata usage
- nvme-core: fix a memory leak in nvme_ns_info_from_identify()
- drm/amd/display: update dcn315 lpddr pstate latency
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- smb: client, common: fix fortify warnings
- blk-mq: don't count completed flush data request as inflight in case of
  quiesce
- nvme-core: check for too small lba shift
- hwtracing: hisi_ptt: Handle the interrupt in hardirq context
- hwtracing: hisi_ptt: Don't try to attach a task
- ASoC: wm8974: Correct boost mixer inputs
- arm64: dts: rockchip: fix rk356x pcie msg interrupt name
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- ASoC: Intel: skl_hda_dsp_generic: Drop HDMI routes when HDMI is not
  available
- nouveau/tu102: flush all pdbs on vmm flush
- ASoC: amd: yc: Add DMI entry to support System76 Pangolin 13
- ASoC: hdac_hda: Conditionally register dais for HDMI and Analog
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- nvme: introduce helper function to get ctrl state
- nvme: prevent potential spectre v1 gadget
- arm64: dts: rockchip: Fix PCI node addresses on rk3399-gru
- drm/amdgpu: Add NULL checks for function pointers
- drm/exynos: fix a potential error pointer dereference
- drm/exynos: fix a wrong error checking
- hwmon: (corsair-psu) Fix probe when built-in
- LoongArch: Preserve syscall nr across execve()
- clk: rockchip: rk3568: Add PLL rate for 292.5MHz
- clk: rockchip: rk3128: Fix HCLK_OTG gate register
- jbd2: correct the printing of write_flags in jbd2_write_superblock()
- jbd2: increase the journal IO's priority
- drm/crtc: Fix uninit-value bug in drm_mode_setcrtc
- neighbour: Don't let neigh_forced_gc() disable preemption for long
- platform/x86: intel-vbtn: Fix missing tablet-mode-switch events
- jbd2: fix soft lockup in 

[Kernel-packages] [Bug 2052499] Re: Mantic update: upstream stable patchset 2024-02-06

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 6.5.0-27.28

---
linux (6.5.0-27.28) mantic; urgency=medium

  * mantic/linux: 6.5.0-27.28 -proposed tracker (LP: #2055584)

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)

  * CVE-2024-26597
- net: qualcomm: rmnet: fix global oob in rmnet_policy

  * CVE-2024-26599
- pwm: Fix out-of-bounds access in of_pwm_single_xlate()

  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks

  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * performance: Scheduler: ratelimit updating of load_avg (LP: #2053251)
- sched/fair: Ratelimit update to tg->load_avg

  * IB peer memory feature regressed in 6.5 (LP: #2055082)
- SAUCE: RDMA/core: Introduce peer memory interface

  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory

  * CVE-2024-23851
- dm: limit the number of targets and parameter size area

  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read

  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * Fix AMD brightness issue on AUO panel (LP: #2054773)
- drm/amdgpu: make damage clips support configurable

  * Mantic update: upstream stable patchset 2024-02-28 (LP: #2055199)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- wifi: avoid offset calculation on NULL pointer
- wifi: mac80211: handle 320 MHz in ieee80211_ht_cap_ie_to_sta_ht_cap
- debugfs: fix automount d_fsdata usage
- nvme-core: fix a memory leak in nvme_ns_info_from_identify()
- drm/amd/display: update dcn315 lpddr pstate latency
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- smb: client, common: fix fortify warnings
- blk-mq: don't count completed flush data request as inflight in case of
  quiesce
- nvme-core: check for too small lba shift
- hwtracing: hisi_ptt: Handle the interrupt in hardirq context
- hwtracing: hisi_ptt: Don't try to attach a task
- ASoC: wm8974: Correct boost mixer inputs
- arm64: dts: rockchip: fix rk356x pcie msg interrupt name
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- ASoC: Intel: skl_hda_dsp_generic: Drop HDMI routes when HDMI is not
  available
- nouveau/tu102: flush all pdbs on vmm flush
- ASoC: amd: yc: Add DMI entry to support System76 Pangolin 13
- ASoC: hdac_hda: Conditionally register dais for HDMI and Analog
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- nvme: introduce helper function to get ctrl state
- nvme: prevent potential spectre v1 gadget
- arm64: dts: rockchip: Fix PCI node addresses on rk3399-gru
- drm/amdgpu: Add NULL checks for function pointers
- drm/exynos: fix a potential error pointer dereference
- drm/exynos: fix a wrong error checking
- hwmon: (corsair-psu) Fix probe when built-in
- LoongArch: Preserve syscall nr across execve()
- clk: rockchip: rk3568: Add PLL rate for 292.5MHz
- clk: rockchip: rk3128: Fix HCLK_OTG gate register
- jbd2: correct the printing of write_flags in jbd2_write_superblock()
- jbd2: increase the journal IO's priority
- drm/crtc: Fix uninit-value bug in drm_mode_setcrtc
- neighbour: Don't let neigh_forced_gc() disable preemption for long
- platform/x86: intel-vbtn: Fix missing tablet-mode-switch events
- jbd2: fix soft lockup in 

[Kernel-packages] [Bug 2052404] Re: Jammy update: v5.15.144 upstream stable release

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.15.0-102.112

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

  * jammy/linux: 5.15.0-102.112 -proposed tracker (LP: #2055632)

  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks
- [Packaging] Drop abi checks from final-checks

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)

  * block/loop: No longer allows to create partitions (LP: #2056143)
- block, loop: support partitions without scanning

  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions
- [Packaging] remove update-version-dkms

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory

  * CVE-2024-23851
- dm ioctl: log an error if the ioctl structure is corrupted
- dm: limit the number of targets and parameter size area

  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read

  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * Fix bpf selftests build failure after v5.15.139 update (LP: #2054567)
- Revert "selftests/bpf: Test tail call counting with bpf2bpf and data on
  stack"

  * Jammy update: v5.15.148 upstream stable release (LP: #2055145)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- debugfs: fix automount d_fsdata usage
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- nvme-core: check for too small lba shift
- ASoC: wm8974: Correct boost mixer inputs
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- nouveau/tu102: flush all pdbs on vmm flush
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- ASoC: ops: add correct range check for limiting volume
- nvme: introduce helper function to get ctrl state
- drm/amdgpu: Add NULL checks for function pointers
- drm/exynos: fix a potential error pointer dereference
- drm/exynos: fix a wrong error checking
- hwmon: (corsair-psu) Fix probe when built-in
- clk: rockchip: rk3128: Fix HCLK_OTG gate register
- jbd2: correct the printing of write_flags in jbd2_write_superblock()
- drm/crtc: Fix uninit-value bug in drm_mode_setcrtc
- neighbour: Don't let neigh_forced_gc() disable preemption for long
- platform/x86: intel-vbtn: Fix missing tablet-mode-switch events
- jbd2: fix soft lockup in journal_finish_inode_data_buffers()
- tracing: Have large events show up as '[LINE TOO BIG]' instead of nothing
- tracing: Add size check when printing trace_marker output
- stmmac: dwmac-loongson: drop useless check for compatible fallback
- MIPS: dts: loongson: drop incorrect dwmac fallback compatible
- tracing: Fix uaf issue when open the hist or hist_debug file
- ring-buffer: Do not record in NMI if the arch does not support cmpxchg in
  NMI
- reset: hisilicon: hi6220: fix Wvoid-pointer-to-enum-cast warning
- Input: atkbd - skip ATKBD_CMD_GETID in translated mode
- Input: i8042 - add nomux quirk for Acer P459-G2-M
- s390/scm: fix virtual vs physical address confusion
- ARC: fix spare error
- wifi: iwlwifi: pcie: avoid a NULL pointer dereference
- Input: xpad - add Razer Wolverine V2 support
- ASoC: Intel: bytcr_rt5640: Add quirk for the Medion Lifetab S10346
- i2c: rk3x: fix potential spinlock recursion on poll
- net: qrtr: ns: Return 0 if server port is not present
- ARM: sun9i: smp: fix return code check of 

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

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.15.0-102.112

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

  * jammy/linux: 5.15.0-102.112 -proposed tracker (LP: #2055632)

  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks
- [Packaging] Drop abi checks from final-checks

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)

  * block/loop: No longer allows to create partitions (LP: #2056143)
- block, loop: support partitions without scanning

  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions
- [Packaging] remove update-version-dkms

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory

  * CVE-2024-23851
- dm ioctl: log an error if the ioctl structure is corrupted
- dm: limit the number of targets and parameter size area

  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read

  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * Fix bpf selftests build failure after v5.15.139 update (LP: #2054567)
- Revert "selftests/bpf: Test tail call counting with bpf2bpf and data on
  stack"

  * Jammy update: v5.15.148 upstream stable release (LP: #2055145)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- debugfs: fix automount d_fsdata usage
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- nvme-core: check for too small lba shift
- ASoC: wm8974: Correct boost mixer inputs
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- nouveau/tu102: flush all pdbs on vmm flush
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- ASoC: ops: add correct range check for limiting volume
- nvme: introduce helper function to get ctrl state
- drm/amdgpu: Add NULL checks for function pointers
- drm/exynos: fix a potential error pointer dereference
- drm/exynos: fix a wrong error checking
- hwmon: (corsair-psu) Fix probe when built-in
- clk: rockchip: rk3128: Fix HCLK_OTG gate register
- jbd2: correct the printing of write_flags in jbd2_write_superblock()
- drm/crtc: Fix uninit-value bug in drm_mode_setcrtc
- neighbour: Don't let neigh_forced_gc() disable preemption for long
- platform/x86: intel-vbtn: Fix missing tablet-mode-switch events
- jbd2: fix soft lockup in journal_finish_inode_data_buffers()
- tracing: Have large events show up as '[LINE TOO BIG]' instead of nothing
- tracing: Add size check when printing trace_marker output
- stmmac: dwmac-loongson: drop useless check for compatible fallback
- MIPS: dts: loongson: drop incorrect dwmac fallback compatible
- tracing: Fix uaf issue when open the hist or hist_debug file
- ring-buffer: Do not record in NMI if the arch does not support cmpxchg in
  NMI
- reset: hisilicon: hi6220: fix Wvoid-pointer-to-enum-cast warning
- Input: atkbd - skip ATKBD_CMD_GETID in translated mode
- Input: i8042 - add nomux quirk for Acer P459-G2-M
- s390/scm: fix virtual vs physical address confusion
- ARC: fix spare error
- wifi: iwlwifi: pcie: avoid a NULL pointer dereference
- Input: xpad - add Razer Wolverine V2 support
- ASoC: Intel: bytcr_rt5640: Add quirk for the Medion Lifetab S10346
- i2c: rk3x: fix potential spinlock recursion on poll
- net: qrtr: ns: Return 0 if server port is not present
- ARM: sun9i: smp: fix return code check of 

[Kernel-packages] [Bug 2052406] Re: Jammy update: v5.15.145 upstream stable release

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.15.0-102.112

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

  * jammy/linux: 5.15.0-102.112 -proposed tracker (LP: #2055632)

  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks
- [Packaging] Drop abi checks from final-checks

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)

  * block/loop: No longer allows to create partitions (LP: #2056143)
- block, loop: support partitions without scanning

  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions
- [Packaging] remove update-version-dkms

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory

  * CVE-2024-23851
- dm ioctl: log an error if the ioctl structure is corrupted
- dm: limit the number of targets and parameter size area

  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read

  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * Fix bpf selftests build failure after v5.15.139 update (LP: #2054567)
- Revert "selftests/bpf: Test tail call counting with bpf2bpf and data on
  stack"

  * Jammy update: v5.15.148 upstream stable release (LP: #2055145)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- debugfs: fix automount d_fsdata usage
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- nvme-core: check for too small lba shift
- ASoC: wm8974: Correct boost mixer inputs
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- nouveau/tu102: flush all pdbs on vmm flush
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- ASoC: ops: add correct range check for limiting volume
- nvme: introduce helper function to get ctrl state
- drm/amdgpu: Add NULL checks for function pointers
- drm/exynos: fix a potential error pointer dereference
- drm/exynos: fix a wrong error checking
- hwmon: (corsair-psu) Fix probe when built-in
- clk: rockchip: rk3128: Fix HCLK_OTG gate register
- jbd2: correct the printing of write_flags in jbd2_write_superblock()
- drm/crtc: Fix uninit-value bug in drm_mode_setcrtc
- neighbour: Don't let neigh_forced_gc() disable preemption for long
- platform/x86: intel-vbtn: Fix missing tablet-mode-switch events
- jbd2: fix soft lockup in journal_finish_inode_data_buffers()
- tracing: Have large events show up as '[LINE TOO BIG]' instead of nothing
- tracing: Add size check when printing trace_marker output
- stmmac: dwmac-loongson: drop useless check for compatible fallback
- MIPS: dts: loongson: drop incorrect dwmac fallback compatible
- tracing: Fix uaf issue when open the hist or hist_debug file
- ring-buffer: Do not record in NMI if the arch does not support cmpxchg in
  NMI
- reset: hisilicon: hi6220: fix Wvoid-pointer-to-enum-cast warning
- Input: atkbd - skip ATKBD_CMD_GETID in translated mode
- Input: i8042 - add nomux quirk for Acer P459-G2-M
- s390/scm: fix virtual vs physical address confusion
- ARC: fix spare error
- wifi: iwlwifi: pcie: avoid a NULL pointer dereference
- Input: xpad - add Razer Wolverine V2 support
- ASoC: Intel: bytcr_rt5640: Add quirk for the Medion Lifetab S10346
- i2c: rk3x: fix potential spinlock recursion on poll
- net: qrtr: ns: Return 0 if server port is not present
- ARM: sun9i: smp: fix return code check of 

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

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.15.0-102.112

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

  * jammy/linux: 5.15.0-102.112 -proposed tracker (LP: #2055632)

  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks
- [Packaging] Drop abi checks from final-checks

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)

  * block/loop: No longer allows to create partitions (LP: #2056143)
- block, loop: support partitions without scanning

  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions
- [Packaging] remove update-version-dkms

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory

  * CVE-2024-23851
- dm ioctl: log an error if the ioctl structure is corrupted
- dm: limit the number of targets and parameter size area

  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read

  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * Fix bpf selftests build failure after v5.15.139 update (LP: #2054567)
- Revert "selftests/bpf: Test tail call counting with bpf2bpf and data on
  stack"

  * Jammy update: v5.15.148 upstream stable release (LP: #2055145)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- debugfs: fix automount d_fsdata usage
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- nvme-core: check for too small lba shift
- ASoC: wm8974: Correct boost mixer inputs
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- nouveau/tu102: flush all pdbs on vmm flush
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- ASoC: ops: add correct range check for limiting volume
- nvme: introduce helper function to get ctrl state
- drm/amdgpu: Add NULL checks for function pointers
- drm/exynos: fix a potential error pointer dereference
- drm/exynos: fix a wrong error checking
- hwmon: (corsair-psu) Fix probe when built-in
- clk: rockchip: rk3128: Fix HCLK_OTG gate register
- jbd2: correct the printing of write_flags in jbd2_write_superblock()
- drm/crtc: Fix uninit-value bug in drm_mode_setcrtc
- neighbour: Don't let neigh_forced_gc() disable preemption for long
- platform/x86: intel-vbtn: Fix missing tablet-mode-switch events
- jbd2: fix soft lockup in journal_finish_inode_data_buffers()
- tracing: Have large events show up as '[LINE TOO BIG]' instead of nothing
- tracing: Add size check when printing trace_marker output
- stmmac: dwmac-loongson: drop useless check for compatible fallback
- MIPS: dts: loongson: drop incorrect dwmac fallback compatible
- tracing: Fix uaf issue when open the hist or hist_debug file
- ring-buffer: Do not record in NMI if the arch does not support cmpxchg in
  NMI
- reset: hisilicon: hi6220: fix Wvoid-pointer-to-enum-cast warning
- Input: atkbd - skip ATKBD_CMD_GETID in translated mode
- Input: i8042 - add nomux quirk for Acer P459-G2-M
- s390/scm: fix virtual vs physical address confusion
- ARC: fix spare error
- wifi: iwlwifi: pcie: avoid a NULL pointer dereference
- Input: xpad - add Razer Wolverine V2 support
- ASoC: Intel: bytcr_rt5640: Add quirk for the Medion Lifetab S10346
- i2c: rk3x: fix potential spinlock recursion on poll
- net: qrtr: ns: Return 0 if server port is not present
- ARM: sun9i: smp: fix return code check of 

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

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.15.0-102.112

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

  * jammy/linux: 5.15.0-102.112 -proposed tracker (LP: #2055632)

  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks
- [Packaging] Drop abi checks from final-checks

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)

  * block/loop: No longer allows to create partitions (LP: #2056143)
- block, loop: support partitions without scanning

  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions
- [Packaging] remove update-version-dkms

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory

  * CVE-2024-23851
- dm ioctl: log an error if the ioctl structure is corrupted
- dm: limit the number of targets and parameter size area

  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read

  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * Fix bpf selftests build failure after v5.15.139 update (LP: #2054567)
- Revert "selftests/bpf: Test tail call counting with bpf2bpf and data on
  stack"

  * Jammy update: v5.15.148 upstream stable release (LP: #2055145)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- debugfs: fix automount d_fsdata usage
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- nvme-core: check for too small lba shift
- ASoC: wm8974: Correct boost mixer inputs
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- nouveau/tu102: flush all pdbs on vmm flush
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- ASoC: ops: add correct range check for limiting volume
- nvme: introduce helper function to get ctrl state
- drm/amdgpu: Add NULL checks for function pointers
- drm/exynos: fix a potential error pointer dereference
- drm/exynos: fix a wrong error checking
- hwmon: (corsair-psu) Fix probe when built-in
- clk: rockchip: rk3128: Fix HCLK_OTG gate register
- jbd2: correct the printing of write_flags in jbd2_write_superblock()
- drm/crtc: Fix uninit-value bug in drm_mode_setcrtc
- neighbour: Don't let neigh_forced_gc() disable preemption for long
- platform/x86: intel-vbtn: Fix missing tablet-mode-switch events
- jbd2: fix soft lockup in journal_finish_inode_data_buffers()
- tracing: Have large events show up as '[LINE TOO BIG]' instead of nothing
- tracing: Add size check when printing trace_marker output
- stmmac: dwmac-loongson: drop useless check for compatible fallback
- MIPS: dts: loongson: drop incorrect dwmac fallback compatible
- tracing: Fix uaf issue when open the hist or hist_debug file
- ring-buffer: Do not record in NMI if the arch does not support cmpxchg in
  NMI
- reset: hisilicon: hi6220: fix Wvoid-pointer-to-enum-cast warning
- Input: atkbd - skip ATKBD_CMD_GETID in translated mode
- Input: i8042 - add nomux quirk for Acer P459-G2-M
- s390/scm: fix virtual vs physical address confusion
- ARC: fix spare error
- wifi: iwlwifi: pcie: avoid a NULL pointer dereference
- Input: xpad - add Razer Wolverine V2 support
- ASoC: Intel: bytcr_rt5640: Add quirk for the Medion Lifetab S10346
- i2c: rk3x: fix potential spinlock recursion on poll
- net: qrtr: ns: Return 0 if server port is not present
- ARM: sun9i: smp: fix return code check of 

[Kernel-packages] [Bug 2053251] Re: performance: Scheduler: ratelimit updating of load_avg

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 6.5.0-27.28

---
linux (6.5.0-27.28) mantic; urgency=medium

  * mantic/linux: 6.5.0-27.28 -proposed tracker (LP: #2055584)

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)

  * CVE-2024-26597
- net: qualcomm: rmnet: fix global oob in rmnet_policy

  * CVE-2024-26599
- pwm: Fix out-of-bounds access in of_pwm_single_xlate()

  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks

  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * performance: Scheduler: ratelimit updating of load_avg (LP: #2053251)
- sched/fair: Ratelimit update to tg->load_avg

  * IB peer memory feature regressed in 6.5 (LP: #2055082)
- SAUCE: RDMA/core: Introduce peer memory interface

  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory

  * CVE-2024-23851
- dm: limit the number of targets and parameter size area

  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read

  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * Fix AMD brightness issue on AUO panel (LP: #2054773)
- drm/amdgpu: make damage clips support configurable

  * Mantic update: upstream stable patchset 2024-02-28 (LP: #2055199)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- wifi: avoid offset calculation on NULL pointer
- wifi: mac80211: handle 320 MHz in ieee80211_ht_cap_ie_to_sta_ht_cap
- debugfs: fix automount d_fsdata usage
- nvme-core: fix a memory leak in nvme_ns_info_from_identify()
- drm/amd/display: update dcn315 lpddr pstate latency
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- smb: client, common: fix fortify warnings
- blk-mq: don't count completed flush data request as inflight in case of
  quiesce
- nvme-core: check for too small lba shift
- hwtracing: hisi_ptt: Handle the interrupt in hardirq context
- hwtracing: hisi_ptt: Don't try to attach a task
- ASoC: wm8974: Correct boost mixer inputs
- arm64: dts: rockchip: fix rk356x pcie msg interrupt name
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- ASoC: Intel: skl_hda_dsp_generic: Drop HDMI routes when HDMI is not
  available
- nouveau/tu102: flush all pdbs on vmm flush
- ASoC: amd: yc: Add DMI entry to support System76 Pangolin 13
- ASoC: hdac_hda: Conditionally register dais for HDMI and Analog
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- nvme: introduce helper function to get ctrl state
- nvme: prevent potential spectre v1 gadget
- arm64: dts: rockchip: Fix PCI node addresses on rk3399-gru
- drm/amdgpu: Add NULL checks for function pointers
- drm/exynos: fix a potential error pointer dereference
- drm/exynos: fix a wrong error checking
- hwmon: (corsair-psu) Fix probe when built-in
- LoongArch: Preserve syscall nr across execve()
- clk: rockchip: rk3568: Add PLL rate for 292.5MHz
- clk: rockchip: rk3128: Fix HCLK_OTG gate register
- jbd2: correct the printing of write_flags in jbd2_write_superblock()
- jbd2: increase the journal IO's priority
- drm/crtc: Fix uninit-value bug in drm_mode_setcrtc
- neighbour: Don't let neigh_forced_gc() disable preemption for long
- platform/x86: intel-vbtn: Fix missing tablet-mode-switch events
- jbd2: fix soft lockup in 

[Kernel-packages] [Bug 2052662] Re: move_mount mediation does not detect if source is detached

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 6.5.0-27.28

---
linux (6.5.0-27.28) mantic; urgency=medium

  * mantic/linux: 6.5.0-27.28 -proposed tracker (LP: #2055584)

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)

  * CVE-2024-26597
- net: qualcomm: rmnet: fix global oob in rmnet_policy

  * CVE-2024-26599
- pwm: Fix out-of-bounds access in of_pwm_single_xlate()

  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks

  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * performance: Scheduler: ratelimit updating of load_avg (LP: #2053251)
- sched/fair: Ratelimit update to tg->load_avg

  * IB peer memory feature regressed in 6.5 (LP: #2055082)
- SAUCE: RDMA/core: Introduce peer memory interface

  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory

  * CVE-2024-23851
- dm: limit the number of targets and parameter size area

  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read

  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * Fix AMD brightness issue on AUO panel (LP: #2054773)
- drm/amdgpu: make damage clips support configurable

  * Mantic update: upstream stable patchset 2024-02-28 (LP: #2055199)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- wifi: avoid offset calculation on NULL pointer
- wifi: mac80211: handle 320 MHz in ieee80211_ht_cap_ie_to_sta_ht_cap
- debugfs: fix automount d_fsdata usage
- nvme-core: fix a memory leak in nvme_ns_info_from_identify()
- drm/amd/display: update dcn315 lpddr pstate latency
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- smb: client, common: fix fortify warnings
- blk-mq: don't count completed flush data request as inflight in case of
  quiesce
- nvme-core: check for too small lba shift
- hwtracing: hisi_ptt: Handle the interrupt in hardirq context
- hwtracing: hisi_ptt: Don't try to attach a task
- ASoC: wm8974: Correct boost mixer inputs
- arm64: dts: rockchip: fix rk356x pcie msg interrupt name
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- ASoC: Intel: skl_hda_dsp_generic: Drop HDMI routes when HDMI is not
  available
- nouveau/tu102: flush all pdbs on vmm flush
- ASoC: amd: yc: Add DMI entry to support System76 Pangolin 13
- ASoC: hdac_hda: Conditionally register dais for HDMI and Analog
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- nvme: introduce helper function to get ctrl state
- nvme: prevent potential spectre v1 gadget
- arm64: dts: rockchip: Fix PCI node addresses on rk3399-gru
- drm/amdgpu: Add NULL checks for function pointers
- drm/exynos: fix a potential error pointer dereference
- drm/exynos: fix a wrong error checking
- hwmon: (corsair-psu) Fix probe when built-in
- LoongArch: Preserve syscall nr across execve()
- clk: rockchip: rk3568: Add PLL rate for 292.5MHz
- clk: rockchip: rk3128: Fix HCLK_OTG gate register
- jbd2: correct the printing of write_flags in jbd2_write_superblock()
- jbd2: increase the journal IO's priority
- drm/crtc: Fix uninit-value bug in drm_mode_setcrtc
- neighbour: Don't let neigh_forced_gc() disable preemption for long
- platform/x86: intel-vbtn: Fix missing tablet-mode-switch events
- jbd2: fix soft lockup in 

[Kernel-packages] [Bug 2053152] Re: performance: mm/percpu-internal.h: Re-layout pcpu_chunk to mitigate false sharing

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.15.0-102.112

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

  * jammy/linux: 5.15.0-102.112 -proposed tracker (LP: #2055632)

  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks
- [Packaging] Drop abi checks from final-checks

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)

  * block/loop: No longer allows to create partitions (LP: #2056143)
- block, loop: support partitions without scanning

  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions
- [Packaging] remove update-version-dkms

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory

  * CVE-2024-23851
- dm ioctl: log an error if the ioctl structure is corrupted
- dm: limit the number of targets and parameter size area

  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read

  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * Fix bpf selftests build failure after v5.15.139 update (LP: #2054567)
- Revert "selftests/bpf: Test tail call counting with bpf2bpf and data on
  stack"

  * Jammy update: v5.15.148 upstream stable release (LP: #2055145)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- debugfs: fix automount d_fsdata usage
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- nvme-core: check for too small lba shift
- ASoC: wm8974: Correct boost mixer inputs
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- nouveau/tu102: flush all pdbs on vmm flush
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- ASoC: ops: add correct range check for limiting volume
- nvme: introduce helper function to get ctrl state
- drm/amdgpu: Add NULL checks for function pointers
- drm/exynos: fix a potential error pointer dereference
- drm/exynos: fix a wrong error checking
- hwmon: (corsair-psu) Fix probe when built-in
- clk: rockchip: rk3128: Fix HCLK_OTG gate register
- jbd2: correct the printing of write_flags in jbd2_write_superblock()
- drm/crtc: Fix uninit-value bug in drm_mode_setcrtc
- neighbour: Don't let neigh_forced_gc() disable preemption for long
- platform/x86: intel-vbtn: Fix missing tablet-mode-switch events
- jbd2: fix soft lockup in journal_finish_inode_data_buffers()
- tracing: Have large events show up as '[LINE TOO BIG]' instead of nothing
- tracing: Add size check when printing trace_marker output
- stmmac: dwmac-loongson: drop useless check for compatible fallback
- MIPS: dts: loongson: drop incorrect dwmac fallback compatible
- tracing: Fix uaf issue when open the hist or hist_debug file
- ring-buffer: Do not record in NMI if the arch does not support cmpxchg in
  NMI
- reset: hisilicon: hi6220: fix Wvoid-pointer-to-enum-cast warning
- Input: atkbd - skip ATKBD_CMD_GETID in translated mode
- Input: i8042 - add nomux quirk for Acer P459-G2-M
- s390/scm: fix virtual vs physical address confusion
- ARC: fix spare error
- wifi: iwlwifi: pcie: avoid a NULL pointer dereference
- Input: xpad - add Razer Wolverine V2 support
- ASoC: Intel: bytcr_rt5640: Add quirk for the Medion Lifetab S10346
- i2c: rk3x: fix potential spinlock recursion on poll
- net: qrtr: ns: Return 0 if server port is not present
- ARM: sun9i: smp: fix return code check of 

[Kernel-packages] [Bug 2053212] Re: Jammy update: v5.15.146 upstream stable release

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.15.0-102.112

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

  * jammy/linux: 5.15.0-102.112 -proposed tracker (LP: #2055632)

  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks
- [Packaging] Drop abi checks from final-checks

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)

  * block/loop: No longer allows to create partitions (LP: #2056143)
- block, loop: support partitions without scanning

  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions
- [Packaging] remove update-version-dkms

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory

  * CVE-2024-23851
- dm ioctl: log an error if the ioctl structure is corrupted
- dm: limit the number of targets and parameter size area

  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read

  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * Fix bpf selftests build failure after v5.15.139 update (LP: #2054567)
- Revert "selftests/bpf: Test tail call counting with bpf2bpf and data on
  stack"

  * Jammy update: v5.15.148 upstream stable release (LP: #2055145)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- debugfs: fix automount d_fsdata usage
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- nvme-core: check for too small lba shift
- ASoC: wm8974: Correct boost mixer inputs
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- nouveau/tu102: flush all pdbs on vmm flush
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- ASoC: ops: add correct range check for limiting volume
- nvme: introduce helper function to get ctrl state
- drm/amdgpu: Add NULL checks for function pointers
- drm/exynos: fix a potential error pointer dereference
- drm/exynos: fix a wrong error checking
- hwmon: (corsair-psu) Fix probe when built-in
- clk: rockchip: rk3128: Fix HCLK_OTG gate register
- jbd2: correct the printing of write_flags in jbd2_write_superblock()
- drm/crtc: Fix uninit-value bug in drm_mode_setcrtc
- neighbour: Don't let neigh_forced_gc() disable preemption for long
- platform/x86: intel-vbtn: Fix missing tablet-mode-switch events
- jbd2: fix soft lockup in journal_finish_inode_data_buffers()
- tracing: Have large events show up as '[LINE TOO BIG]' instead of nothing
- tracing: Add size check when printing trace_marker output
- stmmac: dwmac-loongson: drop useless check for compatible fallback
- MIPS: dts: loongson: drop incorrect dwmac fallback compatible
- tracing: Fix uaf issue when open the hist or hist_debug file
- ring-buffer: Do not record in NMI if the arch does not support cmpxchg in
  NMI
- reset: hisilicon: hi6220: fix Wvoid-pointer-to-enum-cast warning
- Input: atkbd - skip ATKBD_CMD_GETID in translated mode
- Input: i8042 - add nomux quirk for Acer P459-G2-M
- s390/scm: fix virtual vs physical address confusion
- ARC: fix spare error
- wifi: iwlwifi: pcie: avoid a NULL pointer dereference
- Input: xpad - add Razer Wolverine V2 support
- ASoC: Intel: bytcr_rt5640: Add quirk for the Medion Lifetab S10346
- i2c: rk3x: fix potential spinlock recursion on poll
- net: qrtr: ns: Return 0 if server port is not present
- ARM: sun9i: smp: fix return code check of 

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

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.15.0-102.112

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

  * jammy/linux: 5.15.0-102.112 -proposed tracker (LP: #2055632)

  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks
- [Packaging] Drop abi checks from final-checks

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)

  * block/loop: No longer allows to create partitions (LP: #2056143)
- block, loop: support partitions without scanning

  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions
- [Packaging] remove update-version-dkms

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory

  * CVE-2024-23851
- dm ioctl: log an error if the ioctl structure is corrupted
- dm: limit the number of targets and parameter size area

  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read

  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * Fix bpf selftests build failure after v5.15.139 update (LP: #2054567)
- Revert "selftests/bpf: Test tail call counting with bpf2bpf and data on
  stack"

  * Jammy update: v5.15.148 upstream stable release (LP: #2055145)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- debugfs: fix automount d_fsdata usage
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- nvme-core: check for too small lba shift
- ASoC: wm8974: Correct boost mixer inputs
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- nouveau/tu102: flush all pdbs on vmm flush
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- ASoC: ops: add correct range check for limiting volume
- nvme: introduce helper function to get ctrl state
- drm/amdgpu: Add NULL checks for function pointers
- drm/exynos: fix a potential error pointer dereference
- drm/exynos: fix a wrong error checking
- hwmon: (corsair-psu) Fix probe when built-in
- clk: rockchip: rk3128: Fix HCLK_OTG gate register
- jbd2: correct the printing of write_flags in jbd2_write_superblock()
- drm/crtc: Fix uninit-value bug in drm_mode_setcrtc
- neighbour: Don't let neigh_forced_gc() disable preemption for long
- platform/x86: intel-vbtn: Fix missing tablet-mode-switch events
- jbd2: fix soft lockup in journal_finish_inode_data_buffers()
- tracing: Have large events show up as '[LINE TOO BIG]' instead of nothing
- tracing: Add size check when printing trace_marker output
- stmmac: dwmac-loongson: drop useless check for compatible fallback
- MIPS: dts: loongson: drop incorrect dwmac fallback compatible
- tracing: Fix uaf issue when open the hist or hist_debug file
- ring-buffer: Do not record in NMI if the arch does not support cmpxchg in
  NMI
- reset: hisilicon: hi6220: fix Wvoid-pointer-to-enum-cast warning
- Input: atkbd - skip ATKBD_CMD_GETID in translated mode
- Input: i8042 - add nomux quirk for Acer P459-G2-M
- s390/scm: fix virtual vs physical address confusion
- ARC: fix spare error
- wifi: iwlwifi: pcie: avoid a NULL pointer dereference
- Input: xpad - add Razer Wolverine V2 support
- ASoC: Intel: bytcr_rt5640: Add quirk for the Medion Lifetab S10346
- i2c: rk3x: fix potential spinlock recursion on poll
- net: qrtr: ns: Return 0 if server port is not present
- ARM: sun9i: smp: fix return code check of 

[Kernel-packages] [Bug 2052792] Re: Mantic update: upstream stable patchset 2024-02-09

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 6.5.0-27.28

---
linux (6.5.0-27.28) mantic; urgency=medium

  * mantic/linux: 6.5.0-27.28 -proposed tracker (LP: #2055584)

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)

  * CVE-2024-26597
- net: qualcomm: rmnet: fix global oob in rmnet_policy

  * CVE-2024-26599
- pwm: Fix out-of-bounds access in of_pwm_single_xlate()

  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks

  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * performance: Scheduler: ratelimit updating of load_avg (LP: #2053251)
- sched/fair: Ratelimit update to tg->load_avg

  * IB peer memory feature regressed in 6.5 (LP: #2055082)
- SAUCE: RDMA/core: Introduce peer memory interface

  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory

  * CVE-2024-23851
- dm: limit the number of targets and parameter size area

  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read

  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * Fix AMD brightness issue on AUO panel (LP: #2054773)
- drm/amdgpu: make damage clips support configurable

  * Mantic update: upstream stable patchset 2024-02-28 (LP: #2055199)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- wifi: avoid offset calculation on NULL pointer
- wifi: mac80211: handle 320 MHz in ieee80211_ht_cap_ie_to_sta_ht_cap
- debugfs: fix automount d_fsdata usage
- nvme-core: fix a memory leak in nvme_ns_info_from_identify()
- drm/amd/display: update dcn315 lpddr pstate latency
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- smb: client, common: fix fortify warnings
- blk-mq: don't count completed flush data request as inflight in case of
  quiesce
- nvme-core: check for too small lba shift
- hwtracing: hisi_ptt: Handle the interrupt in hardirq context
- hwtracing: hisi_ptt: Don't try to attach a task
- ASoC: wm8974: Correct boost mixer inputs
- arm64: dts: rockchip: fix rk356x pcie msg interrupt name
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- ASoC: Intel: skl_hda_dsp_generic: Drop HDMI routes when HDMI is not
  available
- nouveau/tu102: flush all pdbs on vmm flush
- ASoC: amd: yc: Add DMI entry to support System76 Pangolin 13
- ASoC: hdac_hda: Conditionally register dais for HDMI and Analog
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- nvme: introduce helper function to get ctrl state
- nvme: prevent potential spectre v1 gadget
- arm64: dts: rockchip: Fix PCI node addresses on rk3399-gru
- drm/amdgpu: Add NULL checks for function pointers
- drm/exynos: fix a potential error pointer dereference
- drm/exynos: fix a wrong error checking
- hwmon: (corsair-psu) Fix probe when built-in
- LoongArch: Preserve syscall nr across execve()
- clk: rockchip: rk3568: Add PLL rate for 292.5MHz
- clk: rockchip: rk3128: Fix HCLK_OTG gate register
- jbd2: correct the printing of write_flags in jbd2_write_superblock()
- jbd2: increase the journal IO's priority
- drm/crtc: Fix uninit-value bug in drm_mode_setcrtc
- neighbour: Don't let neigh_forced_gc() disable preemption for long
- platform/x86: intel-vbtn: Fix missing tablet-mode-switch events
- jbd2: fix soft lockup in 

[Kernel-packages] [Bug 2053251] Re: performance: Scheduler: ratelimit updating of load_avg

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.15.0-102.112

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

  * jammy/linux: 5.15.0-102.112 -proposed tracker (LP: #2055632)

  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks
- [Packaging] Drop abi checks from final-checks

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)

  * block/loop: No longer allows to create partitions (LP: #2056143)
- block, loop: support partitions without scanning

  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions
- [Packaging] remove update-version-dkms

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory

  * CVE-2024-23851
- dm ioctl: log an error if the ioctl structure is corrupted
- dm: limit the number of targets and parameter size area

  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read

  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * Fix bpf selftests build failure after v5.15.139 update (LP: #2054567)
- Revert "selftests/bpf: Test tail call counting with bpf2bpf and data on
  stack"

  * Jammy update: v5.15.148 upstream stable release (LP: #2055145)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- debugfs: fix automount d_fsdata usage
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- nvme-core: check for too small lba shift
- ASoC: wm8974: Correct boost mixer inputs
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- nouveau/tu102: flush all pdbs on vmm flush
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- ASoC: ops: add correct range check for limiting volume
- nvme: introduce helper function to get ctrl state
- drm/amdgpu: Add NULL checks for function pointers
- drm/exynos: fix a potential error pointer dereference
- drm/exynos: fix a wrong error checking
- hwmon: (corsair-psu) Fix probe when built-in
- clk: rockchip: rk3128: Fix HCLK_OTG gate register
- jbd2: correct the printing of write_flags in jbd2_write_superblock()
- drm/crtc: Fix uninit-value bug in drm_mode_setcrtc
- neighbour: Don't let neigh_forced_gc() disable preemption for long
- platform/x86: intel-vbtn: Fix missing tablet-mode-switch events
- jbd2: fix soft lockup in journal_finish_inode_data_buffers()
- tracing: Have large events show up as '[LINE TOO BIG]' instead of nothing
- tracing: Add size check when printing trace_marker output
- stmmac: dwmac-loongson: drop useless check for compatible fallback
- MIPS: dts: loongson: drop incorrect dwmac fallback compatible
- tracing: Fix uaf issue when open the hist or hist_debug file
- ring-buffer: Do not record in NMI if the arch does not support cmpxchg in
  NMI
- reset: hisilicon: hi6220: fix Wvoid-pointer-to-enum-cast warning
- Input: atkbd - skip ATKBD_CMD_GETID in translated mode
- Input: i8042 - add nomux quirk for Acer P459-G2-M
- s390/scm: fix virtual vs physical address confusion
- ARC: fix spare error
- wifi: iwlwifi: pcie: avoid a NULL pointer dereference
- Input: xpad - add Razer Wolverine V2 support
- ASoC: Intel: bytcr_rt5640: Add quirk for the Medion Lifetab S10346
- i2c: rk3x: fix potential spinlock recursion on poll
- net: qrtr: ns: Return 0 if server port is not present
- ARM: sun9i: smp: fix return code check of 

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

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.15.0-102.112

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

  * jammy/linux: 5.15.0-102.112 -proposed tracker (LP: #2055632)

  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks
- [Packaging] Drop abi checks from final-checks

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)

  * block/loop: No longer allows to create partitions (LP: #2056143)
- block, loop: support partitions without scanning

  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions
- [Packaging] remove update-version-dkms

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory

  * CVE-2024-23851
- dm ioctl: log an error if the ioctl structure is corrupted
- dm: limit the number of targets and parameter size area

  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read

  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * Fix bpf selftests build failure after v5.15.139 update (LP: #2054567)
- Revert "selftests/bpf: Test tail call counting with bpf2bpf and data on
  stack"

  * Jammy update: v5.15.148 upstream stable release (LP: #2055145)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- debugfs: fix automount d_fsdata usage
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- nvme-core: check for too small lba shift
- ASoC: wm8974: Correct boost mixer inputs
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- nouveau/tu102: flush all pdbs on vmm flush
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- ASoC: ops: add correct range check for limiting volume
- nvme: introduce helper function to get ctrl state
- drm/amdgpu: Add NULL checks for function pointers
- drm/exynos: fix a potential error pointer dereference
- drm/exynos: fix a wrong error checking
- hwmon: (corsair-psu) Fix probe when built-in
- clk: rockchip: rk3128: Fix HCLK_OTG gate register
- jbd2: correct the printing of write_flags in jbd2_write_superblock()
- drm/crtc: Fix uninit-value bug in drm_mode_setcrtc
- neighbour: Don't let neigh_forced_gc() disable preemption for long
- platform/x86: intel-vbtn: Fix missing tablet-mode-switch events
- jbd2: fix soft lockup in journal_finish_inode_data_buffers()
- tracing: Have large events show up as '[LINE TOO BIG]' instead of nothing
- tracing: Add size check when printing trace_marker output
- stmmac: dwmac-loongson: drop useless check for compatible fallback
- MIPS: dts: loongson: drop incorrect dwmac fallback compatible
- tracing: Fix uaf issue when open the hist or hist_debug file
- ring-buffer: Do not record in NMI if the arch does not support cmpxchg in
  NMI
- reset: hisilicon: hi6220: fix Wvoid-pointer-to-enum-cast warning
- Input: atkbd - skip ATKBD_CMD_GETID in translated mode
- Input: i8042 - add nomux quirk for Acer P459-G2-M
- s390/scm: fix virtual vs physical address confusion
- ARC: fix spare error
- wifi: iwlwifi: pcie: avoid a NULL pointer dereference
- Input: xpad - add Razer Wolverine V2 support
- ASoC: Intel: bytcr_rt5640: Add quirk for the Medion Lifetab S10346
- i2c: rk3x: fix potential spinlock recursion on poll
- net: qrtr: ns: Return 0 if server port is not present
- ARM: sun9i: smp: fix return code check of 

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

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 6.5.0-27.28

---
linux (6.5.0-27.28) mantic; urgency=medium

  * mantic/linux: 6.5.0-27.28 -proposed tracker (LP: #2055584)

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)

  * CVE-2024-26597
- net: qualcomm: rmnet: fix global oob in rmnet_policy

  * CVE-2024-26599
- pwm: Fix out-of-bounds access in of_pwm_single_xlate()

  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks

  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * performance: Scheduler: ratelimit updating of load_avg (LP: #2053251)
- sched/fair: Ratelimit update to tg->load_avg

  * IB peer memory feature regressed in 6.5 (LP: #2055082)
- SAUCE: RDMA/core: Introduce peer memory interface

  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory

  * CVE-2024-23851
- dm: limit the number of targets and parameter size area

  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read

  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * Fix AMD brightness issue on AUO panel (LP: #2054773)
- drm/amdgpu: make damage clips support configurable

  * Mantic update: upstream stable patchset 2024-02-28 (LP: #2055199)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- wifi: avoid offset calculation on NULL pointer
- wifi: mac80211: handle 320 MHz in ieee80211_ht_cap_ie_to_sta_ht_cap
- debugfs: fix automount d_fsdata usage
- nvme-core: fix a memory leak in nvme_ns_info_from_identify()
- drm/amd/display: update dcn315 lpddr pstate latency
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- smb: client, common: fix fortify warnings
- blk-mq: don't count completed flush data request as inflight in case of
  quiesce
- nvme-core: check for too small lba shift
- hwtracing: hisi_ptt: Handle the interrupt in hardirq context
- hwtracing: hisi_ptt: Don't try to attach a task
- ASoC: wm8974: Correct boost mixer inputs
- arm64: dts: rockchip: fix rk356x pcie msg interrupt name
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- ASoC: Intel: skl_hda_dsp_generic: Drop HDMI routes when HDMI is not
  available
- nouveau/tu102: flush all pdbs on vmm flush
- ASoC: amd: yc: Add DMI entry to support System76 Pangolin 13
- ASoC: hdac_hda: Conditionally register dais for HDMI and Analog
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- nvme: introduce helper function to get ctrl state
- nvme: prevent potential spectre v1 gadget
- arm64: dts: rockchip: Fix PCI node addresses on rk3399-gru
- drm/amdgpu: Add NULL checks for function pointers
- drm/exynos: fix a potential error pointer dereference
- drm/exynos: fix a wrong error checking
- hwmon: (corsair-psu) Fix probe when built-in
- LoongArch: Preserve syscall nr across execve()
- clk: rockchip: rk3568: Add PLL rate for 292.5MHz
- clk: rockchip: rk3128: Fix HCLK_OTG gate register
- jbd2: correct the printing of write_flags in jbd2_write_superblock()
- jbd2: increase the journal IO's priority
- drm/crtc: Fix uninit-value bug in drm_mode_setcrtc
- neighbour: Don't let neigh_forced_gc() disable preemption for long
- platform/x86: intel-vbtn: Fix missing tablet-mode-switch events
- jbd2: fix soft lockup in 

[Kernel-packages] [Bug 2054218] Re: kvm: Running perf against qemu processes results in page fault inside guest

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 6.5.0-27.28

---
linux (6.5.0-27.28) mantic; urgency=medium

  * mantic/linux: 6.5.0-27.28 -proposed tracker (LP: #2055584)

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)

  * CVE-2024-26597
- net: qualcomm: rmnet: fix global oob in rmnet_policy

  * CVE-2024-26599
- pwm: Fix out-of-bounds access in of_pwm_single_xlate()

  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks

  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * performance: Scheduler: ratelimit updating of load_avg (LP: #2053251)
- sched/fair: Ratelimit update to tg->load_avg

  * IB peer memory feature regressed in 6.5 (LP: #2055082)
- SAUCE: RDMA/core: Introduce peer memory interface

  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory

  * CVE-2024-23851
- dm: limit the number of targets and parameter size area

  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read

  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * Fix AMD brightness issue on AUO panel (LP: #2054773)
- drm/amdgpu: make damage clips support configurable

  * Mantic update: upstream stable patchset 2024-02-28 (LP: #2055199)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- wifi: avoid offset calculation on NULL pointer
- wifi: mac80211: handle 320 MHz in ieee80211_ht_cap_ie_to_sta_ht_cap
- debugfs: fix automount d_fsdata usage
- nvme-core: fix a memory leak in nvme_ns_info_from_identify()
- drm/amd/display: update dcn315 lpddr pstate latency
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- smb: client, common: fix fortify warnings
- blk-mq: don't count completed flush data request as inflight in case of
  quiesce
- nvme-core: check for too small lba shift
- hwtracing: hisi_ptt: Handle the interrupt in hardirq context
- hwtracing: hisi_ptt: Don't try to attach a task
- ASoC: wm8974: Correct boost mixer inputs
- arm64: dts: rockchip: fix rk356x pcie msg interrupt name
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- ASoC: Intel: skl_hda_dsp_generic: Drop HDMI routes when HDMI is not
  available
- nouveau/tu102: flush all pdbs on vmm flush
- ASoC: amd: yc: Add DMI entry to support System76 Pangolin 13
- ASoC: hdac_hda: Conditionally register dais for HDMI and Analog
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- nvme: introduce helper function to get ctrl state
- nvme: prevent potential spectre v1 gadget
- arm64: dts: rockchip: Fix PCI node addresses on rk3399-gru
- drm/amdgpu: Add NULL checks for function pointers
- drm/exynos: fix a potential error pointer dereference
- drm/exynos: fix a wrong error checking
- hwmon: (corsair-psu) Fix probe when built-in
- LoongArch: Preserve syscall nr across execve()
- clk: rockchip: rk3568: Add PLL rate for 292.5MHz
- clk: rockchip: rk3128: Fix HCLK_OTG gate register
- jbd2: correct the printing of write_flags in jbd2_write_superblock()
- jbd2: increase the journal IO's priority
- drm/crtc: Fix uninit-value bug in drm_mode_setcrtc
- neighbour: Don't let neigh_forced_gc() disable preemption for long
- platform/x86: intel-vbtn: Fix missing tablet-mode-switch events
- jbd2: fix soft lockup in 

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

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.15.0-102.112

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

  * jammy/linux: 5.15.0-102.112 -proposed tracker (LP: #2055632)

  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks
- [Packaging] Drop abi checks from final-checks

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)

  * block/loop: No longer allows to create partitions (LP: #2056143)
- block, loop: support partitions without scanning

  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions
- [Packaging] remove update-version-dkms

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory

  * CVE-2024-23851
- dm ioctl: log an error if the ioctl structure is corrupted
- dm: limit the number of targets and parameter size area

  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read

  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * Fix bpf selftests build failure after v5.15.139 update (LP: #2054567)
- Revert "selftests/bpf: Test tail call counting with bpf2bpf and data on
  stack"

  * Jammy update: v5.15.148 upstream stable release (LP: #2055145)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- debugfs: fix automount d_fsdata usage
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- nvme-core: check for too small lba shift
- ASoC: wm8974: Correct boost mixer inputs
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- nouveau/tu102: flush all pdbs on vmm flush
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- ASoC: ops: add correct range check for limiting volume
- nvme: introduce helper function to get ctrl state
- drm/amdgpu: Add NULL checks for function pointers
- drm/exynos: fix a potential error pointer dereference
- drm/exynos: fix a wrong error checking
- hwmon: (corsair-psu) Fix probe when built-in
- clk: rockchip: rk3128: Fix HCLK_OTG gate register
- jbd2: correct the printing of write_flags in jbd2_write_superblock()
- drm/crtc: Fix uninit-value bug in drm_mode_setcrtc
- neighbour: Don't let neigh_forced_gc() disable preemption for long
- platform/x86: intel-vbtn: Fix missing tablet-mode-switch events
- jbd2: fix soft lockup in journal_finish_inode_data_buffers()
- tracing: Have large events show up as '[LINE TOO BIG]' instead of nothing
- tracing: Add size check when printing trace_marker output
- stmmac: dwmac-loongson: drop useless check for compatible fallback
- MIPS: dts: loongson: drop incorrect dwmac fallback compatible
- tracing: Fix uaf issue when open the hist or hist_debug file
- ring-buffer: Do not record in NMI if the arch does not support cmpxchg in
  NMI
- reset: hisilicon: hi6220: fix Wvoid-pointer-to-enum-cast warning
- Input: atkbd - skip ATKBD_CMD_GETID in translated mode
- Input: i8042 - add nomux quirk for Acer P459-G2-M
- s390/scm: fix virtual vs physical address confusion
- ARC: fix spare error
- wifi: iwlwifi: pcie: avoid a NULL pointer dereference
- Input: xpad - add Razer Wolverine V2 support
- ASoC: Intel: bytcr_rt5640: Add quirk for the Medion Lifetab S10346
- i2c: rk3x: fix potential spinlock recursion on poll
- net: qrtr: ns: Return 0 if server port is not present
- ARM: sun9i: smp: fix return code check of 

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

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 6.5.0-27.28

---
linux (6.5.0-27.28) mantic; urgency=medium

  * mantic/linux: 6.5.0-27.28 -proposed tracker (LP: #2055584)

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)

  * CVE-2024-26597
- net: qualcomm: rmnet: fix global oob in rmnet_policy

  * CVE-2024-26599
- pwm: Fix out-of-bounds access in of_pwm_single_xlate()

  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks

  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * performance: Scheduler: ratelimit updating of load_avg (LP: #2053251)
- sched/fair: Ratelimit update to tg->load_avg

  * IB peer memory feature regressed in 6.5 (LP: #2055082)
- SAUCE: RDMA/core: Introduce peer memory interface

  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory

  * CVE-2024-23851
- dm: limit the number of targets and parameter size area

  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read

  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * Fix AMD brightness issue on AUO panel (LP: #2054773)
- drm/amdgpu: make damage clips support configurable

  * Mantic update: upstream stable patchset 2024-02-28 (LP: #2055199)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- wifi: avoid offset calculation on NULL pointer
- wifi: mac80211: handle 320 MHz in ieee80211_ht_cap_ie_to_sta_ht_cap
- debugfs: fix automount d_fsdata usage
- nvme-core: fix a memory leak in nvme_ns_info_from_identify()
- drm/amd/display: update dcn315 lpddr pstate latency
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- smb: client, common: fix fortify warnings
- blk-mq: don't count completed flush data request as inflight in case of
  quiesce
- nvme-core: check for too small lba shift
- hwtracing: hisi_ptt: Handle the interrupt in hardirq context
- hwtracing: hisi_ptt: Don't try to attach a task
- ASoC: wm8974: Correct boost mixer inputs
- arm64: dts: rockchip: fix rk356x pcie msg interrupt name
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- ASoC: Intel: skl_hda_dsp_generic: Drop HDMI routes when HDMI is not
  available
- nouveau/tu102: flush all pdbs on vmm flush
- ASoC: amd: yc: Add DMI entry to support System76 Pangolin 13
- ASoC: hdac_hda: Conditionally register dais for HDMI and Analog
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- nvme: introduce helper function to get ctrl state
- nvme: prevent potential spectre v1 gadget
- arm64: dts: rockchip: Fix PCI node addresses on rk3399-gru
- drm/amdgpu: Add NULL checks for function pointers
- drm/exynos: fix a potential error pointer dereference
- drm/exynos: fix a wrong error checking
- hwmon: (corsair-psu) Fix probe when built-in
- LoongArch: Preserve syscall nr across execve()
- clk: rockchip: rk3568: Add PLL rate for 292.5MHz
- clk: rockchip: rk3128: Fix HCLK_OTG gate register
- jbd2: correct the printing of write_flags in jbd2_write_superblock()
- jbd2: increase the journal IO's priority
- drm/crtc: Fix uninit-value bug in drm_mode_setcrtc
- neighbour: Don't let neigh_forced_gc() disable preemption for long
- platform/x86: intel-vbtn: Fix missing tablet-mode-switch events
- jbd2: fix soft lockup in 

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

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.15.0-102.112

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

  * jammy/linux: 5.15.0-102.112 -proposed tracker (LP: #2055632)

  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks
- [Packaging] Drop abi checks from final-checks

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)

  * block/loop: No longer allows to create partitions (LP: #2056143)
- block, loop: support partitions without scanning

  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions
- [Packaging] remove update-version-dkms

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory

  * CVE-2024-23851
- dm ioctl: log an error if the ioctl structure is corrupted
- dm: limit the number of targets and parameter size area

  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read

  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * Fix bpf selftests build failure after v5.15.139 update (LP: #2054567)
- Revert "selftests/bpf: Test tail call counting with bpf2bpf and data on
  stack"

  * Jammy update: v5.15.148 upstream stable release (LP: #2055145)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- debugfs: fix automount d_fsdata usage
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- nvme-core: check for too small lba shift
- ASoC: wm8974: Correct boost mixer inputs
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- nouveau/tu102: flush all pdbs on vmm flush
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- ASoC: ops: add correct range check for limiting volume
- nvme: introduce helper function to get ctrl state
- drm/amdgpu: Add NULL checks for function pointers
- drm/exynos: fix a potential error pointer dereference
- drm/exynos: fix a wrong error checking
- hwmon: (corsair-psu) Fix probe when built-in
- clk: rockchip: rk3128: Fix HCLK_OTG gate register
- jbd2: correct the printing of write_flags in jbd2_write_superblock()
- drm/crtc: Fix uninit-value bug in drm_mode_setcrtc
- neighbour: Don't let neigh_forced_gc() disable preemption for long
- platform/x86: intel-vbtn: Fix missing tablet-mode-switch events
- jbd2: fix soft lockup in journal_finish_inode_data_buffers()
- tracing: Have large events show up as '[LINE TOO BIG]' instead of nothing
- tracing: Add size check when printing trace_marker output
- stmmac: dwmac-loongson: drop useless check for compatible fallback
- MIPS: dts: loongson: drop incorrect dwmac fallback compatible
- tracing: Fix uaf issue when open the hist or hist_debug file
- ring-buffer: Do not record in NMI if the arch does not support cmpxchg in
  NMI
- reset: hisilicon: hi6220: fix Wvoid-pointer-to-enum-cast warning
- Input: atkbd - skip ATKBD_CMD_GETID in translated mode
- Input: i8042 - add nomux quirk for Acer P459-G2-M
- s390/scm: fix virtual vs physical address confusion
- ARC: fix spare error
- wifi: iwlwifi: pcie: avoid a NULL pointer dereference
- Input: xpad - add Razer Wolverine V2 support
- ASoC: Intel: bytcr_rt5640: Add quirk for the Medion Lifetab S10346
- i2c: rk3x: fix potential spinlock recursion on poll
- net: qrtr: ns: Return 0 if server port is not present
- ARM: sun9i: smp: fix return code check of 

[Kernel-packages] [Bug 2054411] Re: Jammy update: v5.15.147 upstream stable release

2024-04-07 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.15.0-102.112

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

  * jammy/linux: 5.15.0-102.112 -proposed tracker (LP: #2055632)

  * Drop ABI checks from kernel build (LP: #2055686)
- [Packaging] Remove in-tree abi checks
- [Packaging] Drop abi checks from final-checks

  * Packaging resync (LP: #1786013)
- [Packaging] drop ABI data
- [Packaging] update annotations scripts
- debian.master/dkms-versions -- update from kernel-versions 
(main/2024.03.04)

  * block/loop: No longer allows to create partitions (LP: #2056143)
- block, loop: support partitions without scanning

  * Cranky update-dkms-versions rollout (LP: #2055685)
- [Packaging] remove update-dkms-versions
- Move debian/dkms-versions to debian.master/dkms-versions
- [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions
- [Packaging] remove update-version-dkms

  * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-
modules-extra to linux-modules (LP: #2054809)
- UBUNTU [Packaging]: Include erofs in linux-modules instead of 
linux-modules-
  extra

  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
- [Packaging] rules: Put usbip manpages in the correct directory

  * CVE-2024-23851
- dm ioctl: log an error if the ioctl structure is corrupted
- dm: limit the number of targets and parameter size area

  * CVE-2024-23850
- btrfs: do not ASSERT() if the newly created subvolume already got read

  * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
(LP: #2054699)
- x86/tsc: Extend watchdog check exemption to 4-Sockets platform

  * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from
linux-modules-extra to linux-modules (LP: #2045561)
- [Packaging] Move dmi-sysfs.ko into linux-modules

  * Fix bpf selftests build failure after v5.15.139 update (LP: #2054567)
- Revert "selftests/bpf: Test tail call counting with bpf2bpf and data on
  stack"

  * Jammy update: v5.15.148 upstream stable release (LP: #2055145)
- f2fs: explicitly null-terminate the xattr list
- pinctrl: lochnagar: Don't build on MIPS
- ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
- mptcp: fix uninit-value in mptcp_incoming_options
- wifi: cfg80211: lock wiphy mutex for rfkill poll
- debugfs: fix automount d_fsdata usage
- drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer
- nvme-core: check for too small lba shift
- ASoC: wm8974: Correct boost mixer inputs
- ASoC: Intel: Skylake: Fix mem leak in few functions
- ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
  __be16
- ASoC: Intel: Skylake: mem leak in skl register function
- ASoC: cs43130: Fix the position of const qualifier
- ASoC: cs43130: Fix incorrect frame delay configuration
- ASoC: rt5650: add mutex to avoid the jack detection failure
- nouveau/tu102: flush all pdbs on vmm flush
- net/tg3: fix race condition in tg3_reset_task()
- ASoC: da7219: Support low DC impedance headset
- ASoC: ops: add correct range check for limiting volume
- nvme: introduce helper function to get ctrl state
- drm/amdgpu: Add NULL checks for function pointers
- drm/exynos: fix a potential error pointer dereference
- drm/exynos: fix a wrong error checking
- hwmon: (corsair-psu) Fix probe when built-in
- clk: rockchip: rk3128: Fix HCLK_OTG gate register
- jbd2: correct the printing of write_flags in jbd2_write_superblock()
- drm/crtc: Fix uninit-value bug in drm_mode_setcrtc
- neighbour: Don't let neigh_forced_gc() disable preemption for long
- platform/x86: intel-vbtn: Fix missing tablet-mode-switch events
- jbd2: fix soft lockup in journal_finish_inode_data_buffers()
- tracing: Have large events show up as '[LINE TOO BIG]' instead of nothing
- tracing: Add size check when printing trace_marker output
- stmmac: dwmac-loongson: drop useless check for compatible fallback
- MIPS: dts: loongson: drop incorrect dwmac fallback compatible
- tracing: Fix uaf issue when open the hist or hist_debug file
- ring-buffer: Do not record in NMI if the arch does not support cmpxchg in
  NMI
- reset: hisilicon: hi6220: fix Wvoid-pointer-to-enum-cast warning
- Input: atkbd - skip ATKBD_CMD_GETID in translated mode
- Input: i8042 - add nomux quirk for Acer P459-G2-M
- s390/scm: fix virtual vs physical address confusion
- ARC: fix spare error
- wifi: iwlwifi: pcie: avoid a NULL pointer dereference
- Input: xpad - add Razer Wolverine V2 support
- ASoC: Intel: bytcr_rt5640: Add quirk for the Medion Lifetab S10346
- i2c: rk3x: fix potential spinlock recursion on poll
- net: qrtr: ns: Return 0 if server port is not present
- ARM: sun9i: smp: fix return code check of 

  1   2   >