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

[Paolo Pisati]

** Patch added: 
"0001-UBUNTU-Packaging-Recommends-linux-tools-kernel-abi-v.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064266/+attachment/5773019/+files/0001-UBUNTU-Packaging-Recommends-linux-tools-kernel-abi-v.patch

** Description changed:

  [Impact]
  
- The linux-virtual meta is missing a recommends line (that is already
- present in every other noble/ubuntu kernel):
+ The linux-virtual meta is missing a recommends line (already present in
+ every other noble/ubuntu kernel):
  
  ...
  Recommends: linux-tools-${kernel-abi-version}-generic, 
ubuntu-kernel-accessories
  ...
  
  [Fix]
  
  Apply the attached fix.
  
  [How to test]
  
  Install linux-virtual with '--install-recommends' and it should pull in:
  
  -linux-tools-${kernel-abi-version}-generic
  -ubuntu-kernel-accessories
  
  [Regression potential]
  
  Low: it's recommend line and it's already present in every other Ubuntu
  Noble kernel.

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

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

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]

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

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

  [Fix]

  Apply the attached fix.

  [How to test]

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

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

  [Regression potential]

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

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


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

[Kernel-packages] [Bug 2060533] [NEW] Noble update: v6.8.4 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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


Linux 6.8.4
Revert "workqueue.c: Increase workqueue name length"
Revert "workqueue: Move pwq->max_active to wq->max_active"
Revert "workqueue: Factor out pwq_is_empty()"
Revert "workqueue: Replace pwq_activate_inactive_work() with 
[__]pwq_activate_work()"
Revert "workqueue: Move nr_active handling into helpers"
Revert "workqueue: Make wq_adjust_max_active() round-robin pwqs while 
activating"
Revert "workqueue: RCU protect wq->dfl_pwq and implement accessors for it"
Revert "workqueue: Introduce struct wq_node_nr_active"
Revert "workqueue: Implement system-wide nr_active enforcement for unbound 
workqueues"
Revert "workqueue: Don't call cpumask_test_cpu() with -1 CPU in 
wq_update_node_max_active()"
Revert "workqueue: Shorten events_freezable_power_efficient name"

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

** Affects: linux (Ubuntu Noble)
 Importance: Undecided
 Status: Confirmed


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

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

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

Title:
  Noble update: v6.8.4 upstream stable release

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

Bug description:
  
  SRU Justification

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

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

  
  Linux 6.8.4
  Revert "workqueue.c: Increase workqueue name length"
  Revert "workqueue: Move pwq->max_active to wq->max_active"
  Revert "workqueue: Factor out pwq_is_empty()"
  Revert "workqueue: Replace pwq_activate_inactive_work() with 
[__]pwq_activate_work()"
  Revert "workqueue: Move nr_active handling into helpers"
  Revert "workqueue: Make wq_adjust_max_active() round-robin pwqs while 
activating"
  Revert "workqueue: RCU protect wq->dfl_pwq and implement accessors for it"
  Revert "workqueue: Introduce struct wq_node_nr_active"
  Revert "workqueue: Implement system-wide nr_active enforcement for unbound 
workqueues"
  Revert "workqueue: Don't call cpumask_test_cpu() with -1 CPU in 
wq_update_node_max_active()"
  Revert "workqueue: Shorten events_freezable_power_efficient name"

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


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

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

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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


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

[Kernel-packages] [Bug 2060097] [NEW] Noble update: v6.8.2 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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


Linux 6.8.2
printk: Use prb_first_seq() as base for 32bit seq macros
printk: Adjust mapping for 32bit seq macros
x86/efistub: Don't clear BSS twice in mixed mode
x86/efistub: Clear decompressor BSS in native EFI entrypoint
dm-integrity: align the outgoing bio in integrity_recheck
dm io: Support IO priority
selftests: forwarding: Fix ping failure due to short timeout
spi: spi-mt65xx: Fix NULL pointer access in interrupt handler
netfilter: nf_tables: Fix a memory leak in nf_tables_updchain
net: dsa: mt7530: fix handling of all link-local frames
net: dsa: mt7530: fix link-local frames that ingress vlan filtering ports
bpf: report RCU QS in cpumap kthread
net: report RCU QS on threaded NAPI repolling
rcu: add a helper to report consolidated flavor QS
netfilter: nf_tables: do not compare internal table flags on updates
netfilter: nft_set_pipapo: release elements in clone only from destroy path
drm/amdgpu: drop setting buffer funcs in sdma442
drm/amdgpu: fix mmhub client id out-of-bounds access
drm/amdgpu: add MMHUB 3.3.1 support
octeontx2-af: Use separate handlers for interrupts
octeontx2-pf: Send UP messages to VF only when VF is up.
octeontx2-pf: Use default max_active works instead of one
octeontx2-pf: Wait till detach_resources msg is complete
octeontx2: Detect the mbox up or down message via register
devlink: fix port new reply cmd type
net/bnx2x: Prevent access to a freed page in page_pool
dm-integrity: fix a memory leak when rechecking the data
net: phy: fix phy_read_poll_timeout argument type in genphy_loopback
ceph: stop copying to iter at EOF on sync reads
nouveau/gsp: don't check devinit disable on GSP.
ipv4: raw: Fix sending packets from raw sockets via IPsec tunnels
hsr: Handle failures in module init
rds: introduce acquire/release ordering in acquire/release_in_xmit()
wireguard: receive: annotate data-race around receiving_counter.counter
net: move dev->state into net_device_read_txrx group
virtio: packed: fix unmap leak for indirect desc table
vdpa/mlx5: Allow CVQ size changes
vdpa_sim: reset must not run
virtio: uapi: Drop __packed attribute in linux/virtio_pci.h
drm: Fix drm_fixp2int_round() making it add 0.5
spi: spi-imx: fix off-by-one in mx51 CPU mode burst length
net: dsa: mt7530: prevent possible incorrect XTAL frequency selection
net: veth: do not manipulate GRO when using XDP
xfrm: Allow UDP encapsulation only in offload modes
packet: annotate data-races around ignore_outgoing
xen/events: increment refcnt only if event channel is refcounted
xen/evtchn: avoid WARN() when unbinding an event channel
riscv: Fix compilation error with FAST_GUP and rv32
ASoC: SOF: amd: Skip IRAM/DRAM size modification for Steam Deck OLED
ASoC: SOF: amd: Move signed_fw_image to struct acp_quirk_entry
io_uring: fix poll_remove stalled req completion
net: ethernet: mtk_eth_soc: fix PPE hanging issue
net: mediatek: mtk_eth_soc: clear MAC_MCR_FORCE_LINK only when MAC is up
drm/xe: Skip VMAs pin when requesting signal to the last XE_EXEC
drm/xe: Invalidate userptr VMA on page pin fault
nvme: fix reconnection fail due to reserved tag allocation
spi: Fix error code checking in spi_mem_exec_op()
spi: spi-mem: add statistics support to ->exec_op() calls
net: txgbe: fix clk_name exceed MAX_DEV_ID limits
hsr: Fix uninit-value access in hsr_get_node()
vmxnet3: Fix missing reserved tailroom
tcp: Fix refcnt handling in __inet_hash_connect().
io_uring: Fix release of pinned pages when __io_uaddr_map fails
cpufreq: Fix per-policy boost behavior on SoCs using cpufreq_boost_set_sw()
soc: fsl: dpio: fix kcalloc() argument order
riscv: Only check online cpus for emulated accesses
devlink: Fix devlink parallel commands processing
net/sched: taprio: proper TCA_TAPRIO_TC_ENTRY_INDEX check
s390/vtime: fix average steal time calculation
octeontx2-af: Use matching wake_up API variant in CGX command interface
rds: tcp: Fix use-after-free of net in reqsk_timer_handler().
tcp: Fix NEW_SYN_RECV handling in inet_twsk_purge()
nouveau: reset the bo resource bus info after an eviction
ASoC: rockchip: i2s-tdm: Fix inaccurate sampling rates
spi: Restore delays for non-GPIO chip select
spi: lpspi: Avoid potential use-after-free in probe()
io_uring: don't save/restore iowait state
thermal/drivers/qoriq: Fix getting tmu range
thermal/drivers/mediatek/lvts_thermal: Fix a memory leak in an error handling 
path
ASoC: tlv320adc3xxx: Don't strip remove function when driver is builtin
x86/hyperv: Use per 

[Kernel-packages] [Bug 2058224] [NEW] Noble update: v6.8.1 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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

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

** Affects: linux (Ubuntu Noble)
 Importance: Undecided
 Status: Confirmed


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

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

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

Title:
  Noble update: v6.8.1 upstream stable release

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

Bug description:
  
  SRU Justification

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058224/+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 2056491] Re: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block`

[Paolo Pisati]

Can you update a working image to the latest bootstrap kernel and try
again?

https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap -
6.8.0-15.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/2056491

Title:
  not able to install noble on PowerVM LPARs `Kernel panic - not
  syncing: VFS: Unable to mount root fs on unknown-block`

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  After I select `Try or Install Ubuntu Server` on a PowerVM ppc64le
  Power9 or Power10 :

  error: out of memory.

  Press any key to continue...
  OF stdout device is: /vdevice/vty@3000
  Preparing to boot Linux version 6.8.0-11-generic (buildd@bos01-ppc64el-003) 
(powerpc64le-linux-gnu-gcc-13 (Ubuntu 13.2.0-13ubuntu1) 13.2.0, GNU ld (GNU 
Binutils for Ubuntu) 2.42) #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 (Ubuntu 
6.8.0-11.11-generic 6.8.0-rc4)
  Detected machine type: 0101
  command line: BOOT_IMAGE=/casper/vmlinux quiet ---
  Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0e67
alloc_top: 2000
alloc_top_hi : 2000
rmo_top  : 2000
ram_top  : 2000
  instantiating rtas at 0x1ec3... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x1078 -> 0x1078179e
  Device tree struct  0x1079 -> 0x107a
  Quiescing Open Firmware ...
  Booting Linux via __start() @ 0x0a75 ...
  [0.019184] plpks: POWER LPAR Platform KeyStore is not supported or enabled
  [0.114052] SED: plpks not available
  [0.114507] /dev/root: Can't open blockdev
  [0.114520] List of all bdev filesystems:
  [0.114523]  ext3
  [0.114523]  ext2
  [0.114525]  ext4
  [0.114527]  squashfs
  [0.114529]  vfat
  [0.114531]  fuseblk
  [0.114532] 
  [0.114535] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)
  [0.114540] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.8.0-11-generic 
#11-Ubuntu
  [0.114545] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 
of:IBM,FW1030.00 (NH1030_017) hv:phyp pSeries
  [0.114551] Call Trace:
  [0.114553] [c6403b40] [c16b2f28] dump_stack_lvl+0x70/0xb4 
(unreliable)
  [0.114562] [c6403b70] [c01926ec] panic+0x300/0x524
  [0.114568] [c6403c10] [c301146c] 
mount_root_generic+0x208/0x448
  [0.114574] [c6403ce0] [c30118d8] 
prepare_namespace+0x98/0x430
  [0.114580] [c6403d70] [c3010820] 
kernel_init_freeable+0x32c/0x37c
  [0.114585] [c6403de0] [c00115ec] kernel_init+0x34/0x298
  [0.114591] [c6403e50] [c000dfbc] 
ret_from_kernel_user_thread+0x14/0x1c
  [0.114596] --- interrupt: 0 at 0x0
  [0.117006] pstore: backend (nvram) writing error (-1)
  [0.119362] Rebooting in 10 seconds..

  This is the message from a Power10(9080-HEX), but the same is
  happening on a PowrerVM-Power9 (9009-22A)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056491/+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 2054439] Re: RM obsolete binaries from noble to allow linux to migrate

[Paolo Pisati]

Proceed with the removal of linux-modules-ipu6-oem-22.04, linux-modules-
ivsc-oem-22.04, linux-modules-nvidia-440-oem-20.04, linux-modules-
nvidia-450-oem-20.04 from noble and noble-proposed, please.

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

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

Title:
  RM obsolete binaries from noble to allow linux to migrate

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

Bug description:
  currently linux is stuck from migrating because of

  * amd64: linux-modules-ipu6-oem-22.04, linux-modules-ivsc-oem-22.04, 
linux-modules-nvidia-440-oem-20.04, linux-modules-nvidia-450-oem-20.04
  - splitting the component into single items and retrying them

  ipu6 / ivsc are curretnly broken and will be re-introduced once fixed.

  nvidia-440 and nvidia-450 are obsolete and remove from the archive
  and so is oem-20.04 kernel flavour which stopped being a thing in
  jammy.

  Please remove all of those packages from noble & noble-proposed to
  allow linux to migrate

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054439/+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 2008522] Re: Intel_powerclamp use powercap/idle-inject and allow cpumask to inject idle

[Paolo Pisati]

Ok, so every commit was upstream by v6.3-rc1.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  Intel_powerclamp use powercap/idle-inject and allow cpumask to inject
  idle

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  [Feature Description]
  Use the powercap/idle-inject framework for intel Power clamp driver.
  Allow CPU mask and max idle percent as module parameter. This way way driver 
can be used for LPM mode in MTL.

  [HW/SW Information]
  Meteor Lake

  [Software Information]
Target Version:
  23.10
Target Kernel:
  6.3
Commit IDs:
  
acbc661032b8,bbfc3349c4e7,c7cd6f04c0df,98e596fc85fe,ebf519710218,966d0ab67350,621084965459,8526eb7fc75a,8e4736358837,c4e927da893b68b99e94a4a2
External Links:

  [Business Justification]
  Platform enabling

  [External ID]
  LFE-7117

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/2008522/+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 2052420] Re: nvidia-dkms-* FTBS with linux 6.8

[Paolo Pisati]

** Patch added: "nvidia-graphics-drivers-535-server_535.154.05-0ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2052420/+attachment/5744907/+files/nvidia-graphics-drivers-535-server_535.154.05-0ubuntu2.debdiff

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
https://bugs.launchpad.net/bugs/2052420

Title:
   nvidia-dkms-* FTBS with linux 6.8

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Noble:
  Fix Committed

Bug description:
  [Impact]

  ...
  In file included from 
/var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:60:
  /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:748:40: 
error: ‘DRM_UNLOCKED’ undeclared here (not in a function); did you mean 
‘VM_LOCKED’?
748 |   DRM_RENDER_ALLOW|DRM_UNLOCKED),
|^~~~
  ...

  [Fix]

  Apply the attached debdiff.

  [How to test]

  Install (and rebuild) the patched package.

  [Regression potential]

  Two patches, none originating from NVidia and both touching locking:
  there's definitely regression potential here, hence i'm proposing this
  upload *only* for Noble and as a way to move forward (and not stall)
  until NVidia drops a new version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2052420/+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 2052420] Re: nvidia-dkms-* FTBS with linux 6.8

[Paolo Pisati]

** Patch added: "nvidia-graphics-drivers-545_545.29.06-0ubuntu5.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2052420/+attachment/5744864/+files/nvidia-graphics-drivers-545_545.29.06-0ubuntu5.debdiff

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
https://bugs.launchpad.net/bugs/2052420

Title:
   nvidia-dkms-* FTBS with linux 6.8

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 source package in Noble:
  Fix Committed

Bug description:
  [Impact]

  ...
  In file included from 
/var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:60:
  /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:748:40: 
error: ‘DRM_UNLOCKED’ undeclared here (not in a function); did you mean 
‘VM_LOCKED’?
748 |   DRM_RENDER_ALLOW|DRM_UNLOCKED),
|^~~~
  ...

  [Fix]

  Apply the attached debdiff.

  [How to test]

  Install (and rebuild) the patched package.

  [Regression potential]

  Two patches, none originating from NVidia and both touching locking:
  there's definitely regression potential here, hence i'm proposing this
  upload *only* for Noble and as a way to move forward (and not stall)
  until NVidia drops a new version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2052420/+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 2052420] Re: nvidia-dkms-* FTBS with linux 6.8

[Paolo Pisati]

** Patch added: "nvidia-graphics-drivers-535_535.154.05-0ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2052420/+attachment/5744863/+files/nvidia-graphics-drivers-535_535.154.05-0ubuntu2.debdiff

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

Title:
   nvidia-dkms-* FTBS with linux 6.8

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 source package in Noble:
  Fix Committed

Bug description:
  [Impact]

  ...
  In file included from 
/var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:60:
  /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:748:40: 
error: ‘DRM_UNLOCKED’ undeclared here (not in a function); did you mean 
‘VM_LOCKED’?
748 |   DRM_RENDER_ALLOW|DRM_UNLOCKED),
|^~~~
  ...

  [Fix]

  Apply the attached debdiff.

  [How to test]

  Install (and rebuild) the patched package.

  [Regression potential]

  Two patches, none originating from NVidia and both touching locking:
  there's definitely regression potential here, hence i'm proposing this
  upload *only* for Noble and as a way to move forward (and not stall)
  until NVidia drops a new version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2052420/+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 2052420] Re: nvidia-dkms-* FTBS with linux 6.8

[Paolo Pisati]

** Patch added: "nvidia-graphics-drivers-545_545.29.06-0ubuntu5.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2052420/+attachment/5744855/+files/nvidia-graphics-drivers-545_545.29.06-0ubuntu5.debdiff

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

Title:
   nvidia-dkms-* FTBS with linux 6.8

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 source package in Noble:
  Fix Committed

Bug description:
  [Impact]

  ...
  In file included from 
/var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:60:
  /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:748:40: 
error: ‘DRM_UNLOCKED’ undeclared here (not in a function); did you mean 
‘VM_LOCKED’?
748 |   DRM_RENDER_ALLOW|DRM_UNLOCKED),
|^~~~
  ...

  [Fix]

  Apply the attached debdiff.

  [How to test]

  Install (and rebuild) the patched package.

  [Regression potential]

  Two patches, none originating from NVidia and both touching locking:
  there's definitely regression potential here, hence i'm proposing this
  upload *only* for Noble and as a way to move forward (and not stall)
  until NVidia drops a new version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2052420/+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 2052420] Re: nvidia-dkms-* FTBS with linux 6.8

[Paolo Pisati]

** Patch added: "nvidia-graphics-drivers-470-server_470.223.02-0ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470-server/+bug/2052420/+attachment/5744699/+files/nvidia-graphics-drivers-470-server_470.223.02-0ubuntu2.debdiff

** Also affects: nvidia-graphics-drivers-545 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-535 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-535-server (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
https://bugs.launchpad.net/bugs/2052420

Title:
   nvidia-dkms-* FTBS with linux 6.8

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 source package in Noble:
  New

Bug description:
  [Impact]

  ...
  In file included from 
/var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:60:
  /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:748:40: 
error: ‘DRM_UNLOCKED’ undeclared here (not in a function); did you mean 
‘VM_LOCKED’?
748 |   DRM_RENDER_ALLOW|DRM_UNLOCKED),
|^~~~
  ...

  [Fix]

  Apply the attached debdiff.

  [How to test]

  Install (and rebuild) the patched package.

  [Regression potential]

  Two patches, none originating from NVidia and both touching locking:
  there's definitely regression potential here, hence i'm proposing this
  upload *only* for Noble and as a way to move forward (and not stall)
  until NVidia drops a new version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2052420/+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 2052420] Re: nvidia-dkms-* FTBS with linux 6.8

[Paolo Pisati]

** Patch added: "nvidia-graphics-drivers-470_470.223.02-0ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2052420/+attachment/5744687/+files/nvidia-graphics-drivers-470_470.223.02-0ubuntu2.debdiff

** Also affects: nvidia-graphics-drivers-470-server (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
   nvidia-dkms-* FTBS with linux 6.8

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 source package in Noble:
  New

Bug description:
  [Impact]

  ...
  In file included from 
/var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:60:
  /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:748:40: 
error: ‘DRM_UNLOCKED’ undeclared here (not in a function); did you mean 
‘VM_LOCKED’?
748 |   DRM_RENDER_ALLOW|DRM_UNLOCKED),
|^~~~
  ...

  [Fix]

  Apply the attached debdiff.

  [How to test]

  Install (and rebuild) the patched package.

  [Regression potential]

  Two patches, none originating from NVidia and both touching locking:
  there's definitely regression potential here, hence i'm proposing this
  upload *only* for Noble and as a way to move forward (and not stall)
  until NVidia drops a new version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2052420/+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 2052420] Re: nvidia-dkms-* FTBS with linux 6.8

[Paolo Pisati]

** Description changed:

  [Impact]
  
  ...
+ In file included from 
/var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:60:
+ /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:748:40: 
error: ‘DRM_UNLOCKED’ undeclared here (not in a function); did you mean 
‘VM_LOCKED’?
+   748 |   DRM_RENDER_ALLOW|DRM_UNLOCKED),
+   |^~~~
  ...
  
  [Fix]
  
  Apply the attached debdiff.
  
  [How to test]
  
  Install (and rebuild) the patched package.
  
  [Regression potential]
  
  Two patches, none originating from NVidia and both touching locking:
  there's definitely regression potential here, hence i'm proposing this
  upload *only* for Noble and as a way to move forward (and not stall)
  until NVidia drops a new version.

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

Title:
   nvidia-dkms-* FTBS with linux 6.8

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 source package in Noble:
  New

Bug description:
  [Impact]

  ...
  In file included from 
/var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:60:
  /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:748:40: 
error: ‘DRM_UNLOCKED’ undeclared here (not in a function); did you mean 
‘VM_LOCKED’?
748 |   DRM_RENDER_ALLOW|DRM_UNLOCKED),
|^~~~
  ...

  [Fix]

  Apply the attached debdiff.

  [How to test]

  Install (and rebuild) the patched package.

  [Regression potential]

  Two patches, none originating from NVidia and both touching locking:
  there's definitely regression potential here, hence i'm proposing this
  upload *only* for Noble and as a way to move forward (and not stall)
  until NVidia drops a new version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2052420/+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 2052420] [NEW] nvidia-dkms-* FTBS with linux 6.8

[Paolo Pisati]

Public bug reported:

[Impact]

...
...

[Fix]

Apply the attached debdiff.

[How to test]

Install (and rebuild) the patched package.

[Regression potential]

Two patches, none originating from NVidia and both touching locking:
there's definitely regression potential here, hence i'm proposing this
upload *only* for Noble and as a way to move forward (and not stall)
until NVidia drops a new version.

** Affects: nvidia-graphics-drivers-470 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: nvidia-graphics-drivers-470 (Ubuntu Noble)
 Importance: Undecided
 Status: New

** Also affects: nvidia-graphics-drivers-390 (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-470 (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: nvidia-graphics-drivers-390 (Ubuntu)

** No longer affects: nvidia-graphics-drivers-390 (Ubuntu Noble)

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

Title:
   nvidia-dkms-* FTBS with linux 6.8

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 source package in Noble:
  New

Bug description:
  [Impact]

  ...
  ...

  [Fix]

  Apply the attached debdiff.

  [How to test]

  Install (and rebuild) the patched package.

  [Regression potential]

  Two patches, none originating from NVidia and both touching locking:
  there's definitely regression potential here, hence i'm proposing this
  upload *only* for Noble and as a way to move forward (and not stall)
  until NVidia drops a new version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2052420/+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 2008522] Re: Intel_powerclamp use powercap/idle-inject and allow cpumask to inject idle

[Paolo Pisati]

Commit
acbc661032b8,bbfc3349c4e7,c7cd6f04c0df,98e596fc85fe,ebf519710218,966d0ab67350,621084965459,8526eb7fc75a,8e4736358837
were all part of v6.3-rc1, thus shipped with 23.10 GA kernel.

While the last mentioned commit (c4e927da893b68b99e94a4a2) is nowhere to
be found, can you double check the SHA?

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

Title:
  Intel_powerclamp use powercap/idle-inject and allow cpumask to inject
  idle

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Feature Description]
  Use the powercap/idle-inject framework for intel Power clamp driver.
  Allow CPU mask and max idle percent as module parameter. This way way driver 
can be used for LPM mode in MTL.

  
  Target Kernel: 6.3
  Target Release: 23.10

  [HW/SW Information]
  Meteor Lake

  [Business Justification]
  Platform enabling

  Upstream: Merged 6.3
  Commit ID:
acbc661032b8,bbfc3349c4e7,c7cd6f04c0df,98e596fc85fe,ebf519710218,966d0ab67350,621084965459,8526eb7fc75a,8e4736358837,c4e927da893b68b99e94a4a2

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/2008522/+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 2046465] [NEW] Noble update: v6.6.6 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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


Linux 6.6.6
Revert "wifi: cfg80211: fix CQM for non-range use"

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

** Affects: linux (Ubuntu Noble)
 Importance: Undecided
 Status: Confirmed


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

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

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

Title:
  Noble update: v6.6.6 upstream stable release

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

Bug description:
  
  SRU Justification

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

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

  
  Linux 6.6.6
  Revert "wifi: cfg80211: fix CQM for non-range use"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046465/+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 2046463] [NEW] Noble update: v6.6.4 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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


Linux 6.6.4
USB: dwc3: qcom: fix wakeup after probe deferral
USB: dwc3: qcom: fix software node leak on probe errors
usb: dwc3: set the dma max_seg_size
usb: dwc3: Fix default mode initialization
USB: dwc2: write HCINT with INTMASK applied
usb: typec: tcpm: Skip hard reset when in error recovery
usb: typec: tcpm: Fix sink caps op current check
USB: serial: option: don't claim interface 4 for ZTE MF290
USB: serial: option: fix FM101R-GL defines
USB: serial: option: add Fibocom L7xx modules
usb: cdnsp: Fix deadlock issue during using NCM gadget
usb: config: fix iteration issue in 'usb_get_bos_descriptor()'
USB: xhci-plat: fix legacy PHY double init
bcache: fixup lock c->root error
bcache: fixup init dirty data errors
bcache: prevent potential division by zero error
bcache: check return value from btree_node_alloc_replacement()
veth: Use tstats per-CPU traffic counters
dm-delay: fix a race between delay_presuspend and delay_bio
ALSA: hda/realtek: Add quirks for ASUS 2024 Zenbooks
ALSA: hda: ASUS UM5302LA: Added quirks for cs35L41/10431A83 on i2c bus
cifs: fix leak of iface for primary channel
cifs: account for primary channel in the interface list
cifs: distribute channels across interfaces based on speed
Revert "phy: realtek: usb: Add driver for the Realtek SoC USB 2.0 PHY"
Revert "phy: realtek: usb: Add driver for the Realtek SoC USB 3.0 PHY"
Revert "usb: phy: add usb phy notify port status API"
hv_netvsc: Mark VF as slave before exposing it to user-mode
hv_netvsc: Fix race of register_netdevice_notifier and VF register
hv_netvsc: fix race of netvsc and VF register_netdevice
platform/x86: ideapad-laptop: Set max_brightness before using it
platform/x86/amd/pmc: adjust getting DRAM size behavior
USB: serial: option: add Luat Air72*U series products
usb: misc: onboard-hub: add support for Microchip USB5744
dt-bindings: usb: microchip,usb5744: Add second supply
platform/x86: hp-bioscfg: Fix error handling in hp_add_other_attributes()
platform/x86: hp-bioscfg: move mutex_lock() down in hp_add_other_attributes()
platform/x86: hp-bioscfg: Simplify return check in hp_add_other_attributes()
s390/dasd: protect device queue against concurrent access
io_uring/fs: consider link->flags when getting path for LINKAT
bcache: fixup multi-threaded bch_sectors_dirty_init() wake-up race
md: fix bi_status reporting in md_end_clone_io
bcache: replace a mistaken IS_ERR() by IS_ERR_OR_NULL() in btree_gc_coalesce()
io_uring: fix off-by one bvec index
tls: fix NULL deref on tls_sw_splice_eof() with empty record
swiotlb-xen: provide the "max_mapping_size" method
ACPI: PM: Add acpi_device_fix_up_power_children() function
ACPI: resource: Skip IRQ override on ASUS ExpertBook B1402CVA
ACPI: processor_idle: use raw_safe_halt() in acpi_idle_play_dead()
ACPI: video: Use acpi_device_fix_up_power_children()
thunderbolt: Set lane bonding bit only for downstream port
drm/ast: Disconnect BMC if physical connector is connected
drm/msm/dpu: Add missing safe_lut_tbl in sc8280xp catalog
kselftest/arm64: Fix output formatting for za-fork
prctl: Disable prctl(PR_SET_MDWE) on parisc
mm: add a NO_INHERIT flag to the PR_SET_MDWE prctl
lockdep: Fix block chain corruption
USB: dwc3: qcom: fix ACPI platform device leak
USB: dwc3: qcom: fix resource leaks on probe deferral
nvmet: nul-terminate the NQNs passed in the connect command
nvme: blank out authentication fabrics options if not configured
afs: Fix file locking on R/O volumes to operate in local mode
afs: Return ENOENT if no cell DNS record can be found
net: ipa: fix one GSI register field width
net: axienet: Fix check for partial TX checksum
vsock/test: fix SEQPACKET message bounds test
i40e: Fix adding unsupported cloud filters
amd-xgbe: propagate the correct speed and duplex status
amd-xgbe: handle the corner-case during tx completion
amd-xgbe: handle corner-case during sfp hotplug
net: veth: fix ethtool stats reporting
octeontx2-pf: Fix ntuple rule creation to direct packet to VF with higher Rx 
queue than its PF
arm/xen: fix xen_vcpu_info allocation alignment
arm64: mm: Fix "rodata=on" when CONFIG_RODATA_FULL_DEFAULT_ENABLED=y
s390/ipl: add missing IPL_TYPE_ECKD_DUMP case to ipl_init()
net/smc: avoid data corruption caused by decline
net: usb: ax88179_178a: fix failed operations during ax88179_reset
drm/panel: boe-tv101wum-nl6: Fine tune Himax83102-j02 panel HFP and HBP
ipv4: Correct/silence an endian warning in __ip_do_redirect
HID: fix HID device 

[Kernel-packages] [Bug 2046464] [NEW] Noble update: v6.6.5 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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


Linux 6.6.5
vfio: Drop vfio_file_iommu_group() stub to fudge around a KVM wart
x86/xen: fix percpu vcpu_info allocation
vfio/pds: Fix possible sleep while in atomic context
vfio/pds: Fix mutex lock->magic != lock warning
drm/amd/display: Fix MPCC 1DLUT programming
drm/amd/display: Simplify brightness initialization
drm/amd/display: Reduce default backlight min from 5 nits to 1 nits
drm/amd/display: refactor ILR to make it work
iommu: Fix printk arg in of_iommu_get_resv_regions()
drm/amd/pm: fix a memleak in aldebaran_tables_init
cpufreq/amd-pstate: Only print supported EPP values for performance governor
cpufreq/amd-pstate: Fix scaling_min_freq and scaling_max_freq update
drm/panel: nt36523: fix return value check in nt36523_probe()
drm/panel: starry-2081101qfh032011-53g: Fine tune the panel power sequence
drm/i915/gsc: Mark internal GSC engine with reserved uabi class
iommu/vt-d: Make context clearing consistent with context mapping
iommu/vt-d: Disable PCI ATS in legacy passthrough mode
iommu/vt-d: Omit devTLB invalidation requests when TES=0
cpufreq: imx6q: Don't disable 792 Mhz OPP unnecessarily
drm/amd/display: Remove power sequencing check
drm/amd/display: Refactor edp power control
s390/cmma: fix handling of swapper_pg_dir and invalid_pg_dir
powerpc/pseries/iommu: enable_ddw incorrectly returns direct mapping for SR-IOV 
device
net: ravb: Keep reverse order of operations in ravb_remove()
net: ravb: Stop DMA in case of failures on ravb_open()
net: ravb: Start TX queues after HW initialization succeeded
net: ravb: Make write access to CXR35 first before accessing other EMAC 
registers
net: ravb: Use pm_runtime_resume_and_get()
net: ravb: Check return value of reset_control_deassert()
ice: Fix VF Reset paths when interface in a failed over aggregate
bpf, sockmap: af_unix stream sockets need to hold ref for pair sock
ethtool: don't propagate EOPNOTSUPP from dumps
ravb: Fix races between ravb_tx_timeout_work() and net related ops
r8169: prevent potential deadlock in rtl8169_close
efi/unaccepted: Fix off-by-one when checking for overlapping ranges
neighbour: Fix __randomize_layout crash in struct neighbour
octeontx2-pf: Restore TC ingress police rules when interface is up
octeontx2-pf: Fix adding mbox work queue entry when num_vfs > 64
net: stmmac: xgmac: Disable FPE MMC interrupts
octeontx2-af: Fix possible buffer overflow
selftests/net: mptcp: fix uninitialized variable warnings
selftests/net: unix: fix unused variable compiler warning
selftests/net: fix a char signedness issue
selftests/net: ipsec: fix constant out of range
uapi: propagate __struct_group() attributes to the container union
bpf: Add missed allocation hint for bpf_mem_cache_alloc_flags()
dpaa2-eth: recycle the RX buffer only after all processing done
dpaa2-eth: increase the needed headroom to account for alignment
net: dsa: mv88e6xxx: fix marvell 6350 probe crash
net: dsa: mv88e6xxx: fix marvell 6350 switch probing
wifi: mac80211: do not pass AP_VLAN vif pointer to drivers during flush
wifi: iwlwifi: mvm: fix an error code in iwl_mvm_mld_add_sta()
ipv4: igmp: fix refcnt uaf issue when receiving igmp query packet
net: rswitch: Fix missing dev_kfree_skb_any() in error path
net: rswitch: Fix return value in rswitch_start_xmit()
net: rswitch: Fix type of ret in rswitch_start_xmit()
netdevsim: Don't accept device bound programs
media: v4l2-subdev: Fix a 64bit bug
pinctrl: stm32: fix array read out of bound
pinctrl: stm32: Add check for devm_kcalloc
wifi: cfg80211: fix CQM for non-range use
io_uring/kbuf: recycle freed mapped buffer ring entries
io_uring/kbuf: defer release of mapped buffer rings
io_uring: enable io_mem_alloc/free to be used in other parts
btrfs: fix 64bit compat send ioctl arguments not initializing version member
btrfs: free the allocated memory if btrfs_alloc_page_array() fails
btrfs: make error messages more clear when getting a chunk map
btrfs: send: ensure send_fd is writable
btrfs: fix off-by-one when checking chunk map includes logical address
btrfs: ref-verify: fix memory leaks in btrfs_ref_tree_mod()
btrfs: add dmesg output for first mount and last unmount of a filesystem
parisc: Mark altinstructions read-only and 32-bit aligned
parisc: Ensure 32-bit alignment on parisc unwind section
parisc: Mark jump_table naturally aligned
parisc: Drop the HP-UX ENOSYM and EREMOTERELEASE error codes
parisc: Mark lock_aligned variables 16-byte aligned on SMP
parisc: Use natural CPU 

[Kernel-packages] [Bug 2046466] [NEW] Noble update: v6.6.7 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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


Linux 6.6.7
drm/amdgpu: Restrict extended wait to PSP v13.0.6
drm/amdgpu: update retry times for psp BL wait
drm/amdgpu: Fix refclk reporting for SMU v13.0.6
riscv: Kconfig: Add select ARM_AMBA to SOC_STARFIVE
gcc-plugins: randstruct: Update code comment in relayout_struct()
ASoC: qcom: sc8280xp: Limit speaker digital volumes
netfilter: nft_set_pipapo: skip inactive elements during set walk
MIPS: Loongson64: Enable DMA noncoherent support
MIPS: Loongson64: Handle more memory types passed from firmware
MIPS: Loongson64: Reserve vgabios memory on boot
perf metrics: Avoid segv if default metricgroup isn't set
perf list: Fix JSON segfault by setting the used skip_duplicate_pmus callback
KVM: SVM: Update EFER software model on CR0 trap for SEV-ES
KVM: s390/mm: Properly reset no-dat
MIPS: kernel: Clear FPU states when setting up kernel threads
cifs: Fix flushing, invalidation and file size with FICLONE
cifs: Fix flushing, invalidation and file size with copy_file_range()
USB: gadget: core: adjust uevent timing on gadget unbind
powerpc/ftrace: Fix stack teardown in ftrace_no_trace
x86/CPU/AMD: Check vendor in the AMD microcode callback
devcoredump: Send uevent once devcd is ready
serial: 8250_omap: Add earlycon support for the AM654 UART controller
serial: 8250: 8250_omap: Do not start RX DMA on THRI interrupt
serial: 8250: 8250_omap: Clear UART_HAS_RHR_IT_DIS bit
serial: sc16is7xx: address RX timeout interrupt errata
ARM: PL011: Fix DMA support
usb: typec: class: fix typec_altmode_put_partner to put plugs
smb: client: fix potential NULL deref in parse_dfs_referrals()
Revert "xhci: Loosen RPM as default policy to cover for AMD xHC 1.1"
cifs: Fix non-availability of dedup breaking generic/304
parport: Add support for Brainboxes IX/UC/PX parallel cards
serial: ma35d1: Validate console index before assignment
serial: 8250_dw: Add ACPI ID for Granite Rapids-D UART
nvmem: Do not expect fixed layouts to grab a layout driver
usb: gadget: f_hid: fix report descriptor allocation
kprobes: consistent rcu api usage for kretprobe holder
ASoC: ops: add correct range check for limiting volume
gpiolib: sysfs: Fix error handling on failed export
x86/sev: Fix kernel crash due to late update to read-only ghcb_version
perf: Fix perf_event_validate_size()
drm/amdgpu: disable MCBP by default
arm64: dts: mt8183: kukui: Fix underscores in node names
arm64: dts: mediatek: add missing space before {
parisc: Fix asm operand number out of range build error in bug table
parisc: Reduce size of the bug_table on 64-bit kernel by half
LoongArch: BPF: Don't sign extend function return value
LoongArch: BPF: Don't sign extend memory load operand
perf vendor events arm64: AmpereOne: Add missing DefaultMetricgroupName fields
misc: mei: client.c: fix problem of return '-EOVERFLOW' in mei_cl_write
misc: mei: client.c: return negative error code in mei_cl_write
coresight: ultrasoc-smb: Fix uninitialized before use buf_hw_base
coresight: ultrasoc-smb: Config SMB buffer before register sink
coresight: ultrasoc-smb: Fix sleep while close preempt in enable_smb
hwtracing: hisi_ptt: Add dummy callback pmu::read()
coresight: Fix crash when Perf and sysfs modes are used concurrently
coresight: etm4x: Remove bogous __exit annotation for some functions
arm64: dts: mediatek: mt8186: Change gpu speedbin nvmem cell name
arm64: dts: mediatek: mt8186: fix clock names for power domains
arm64: dts: mediatek: mt8183-evb: Fix unit_address_vs_reg warning on ntc
arm64: dts: mediatek: mt8183: Move thermal-zones to the root node
arm64: dts: mediatek: mt8183: Fix unit address for scp reserved memory
arm64: dts: mediatek: mt8195: Fix PM suspend/resume with venc clocks
arm64: dts: mediatek: mt8173-evb: Fix regulator-fixed node names
arm64: dts: mediatek: cherry: Fix interrupt cells for MT6360 on I2C7
arm64: dts: mediatek: mt8183-kukui-jacuzzi: fix dsi unnecessary cells properties
arm64: dts: mediatek: mt7622: fix memory node warning check
arm64: dts: mt7986: fix emmc hs400 mode without uboot initialization
arm64: dts: mt7986: define 3W max power to both SFP on BPI-R3
arm64: dts: mt7986: change cooling trips
drm/i915: Skip some timing checks on BXT/GLK DSI transcoders
drm/i915/mst: Reject modes that require the bigjoiner
drm/i915/mst: Fix .mode_valid_ctx() return values
drm/atomic-helpers: Invoke end_fb_access while owning plane state
md/raid6: use valid sector values to determine if an I/O should wait on the 
reshape
powercap: 

[Kernel-packages] [Bug 2045244] [NEW] Noble update: v6.6.3 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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


Linux 6.6.3
drm/amd/display: Change the DMCUB mailbox memory location from FB to inbox
drm/amd/display: Clear dpcd_sink_ext_caps if not set
drm/amd/display: Enable fast plane updates on DCN3.2 and above
drm/amd/display: fix a NULL pointer dereference in amdgpu_dm_i2c_xfer()
drm/amd/display: Fix DSC not Enabled on Direct MST Sink
drm/amd/display: Guard against invalid RPTR/WPTR being set
drm/amdgpu: Fix possible null pointer dereference
drm/amdgpu: lower CS errors to debug severity
drm/amdgpu: fix error handling in amdgpu_bo_list_get()
drm/amdgpu: fix error handling in amdgpu_vm_init
drm/amdgpu: don't use ATRM for external devices
drm/amdgpu: add a retry for IP discovery init
drm/amdgpu: fix GRBM read timeout when do mes_self_test
drm/amdgpu: don't use pci_is_thunderbolt_attached()
drm/amdgpu/smu13: drop compute workload workaround
drm/amd/pm: Fix error of MACO flag setting code
drm/i915: Flush WC GGTT only on required platforms
drm/i915: Fix potential spectre vulnerability
drm/i915: Bump GLK CDCLK frequency when driving multiple pipes
drm/i915/mtl: Support HBR3 rate with C10 phy and eDP in MTL
drm/amd/display: Add Null check for DPP resource
x86/srso: Move retbleed IBPB check into existing 'has_microcode' code block
drm: bridge: it66121: ->get_edid callback must not return err pointers
drm/amd/pm: Handle non-terminated overdrive commands.
ext4: fix racy may inline data check in dio write
ext4: properly sync file size update after O_SYNC direct IO
ext4: add missed brelse in update_backups
ext4: remove gdb backup copy for meta bg in setup_new_flex_group_blocks
ext4: correct the start block of counting reserved clusters
ext4: correct return value of ext4_convert_meta_bg
ext4: mark buffer new if it is unwritten to avoid stale data exposure
ext4: correct offset of gdb backup in non meta_bg group to update_backups
ext4: apply umask if ACL support is disabled
ext4: make sure allocate pending entry not fail
ext4: no need to generate from free list in mballoc
ext4: fix race between writepages and remount
Revert "net: r8169: Disable multicast filter for RTL8168H and RTL8107E"
Revert "HID: logitech-dj: Add support for a new lightspeed receiver iteration"
media: qcom: camss: Fix csid-gen2 for test pattern generator
media: qcom: camss: Fix invalid clock enable bit disjunction
media: qcom: camss: Fix set CSI2_RX_CFG1_VC_MODE when VC is greater than 3
media: qcom: camss: Fix missing vfe_lite clocks check
media: qcom: camss: Fix VFE-480 vfe_disable_output()
media: qcom: camss: Fix VFE-17x vfe_disable_output()
media: qcom: camss: Fix vfe_get() error jump
media: qcom: camss: Fix pm_domain_on sequence in probe
mmc: sdhci-pci-gli: GL9750: Mask the replay timer timeout of AER
r8169: add handling DASH when DASH is disabled
r8169: fix network lost after resume on DASH systems
selftests: mptcp: fix fastclose with csum failure
mptcp: fix setsockopt(IP_TOS) subflow locking
mptcp: add validity check for sending RM_ADDR
mptcp: deal with large GSO size
mm: kmem: drop __GFP_NOFAIL when allocating objcg vectors
mm: fix for negative counter: nr_file_hugepages
mmc: sdhci-pci-gli: A workaround to allow GL9750 to enter ASPM L1.2
riscv: kprobes: allow writing to x0
riscv: correct pt_level name via pgtable_l5/4_enabled
riscv: mm: Update the comment of CONFIG_PAGE_OFFSET
riscv: put interrupt entries into .irqentry.text
riscv: Using TOOLCHAIN_HAS_ZIHINTPAUSE marco replace zihintpause
swiotlb: fix out-of-bounds TLB allocations with CONFIG_SWIOTLB_DYNAMIC
swiotlb: do not free decrypted pages if dynamic
tracing: fprobe-event: Fix to check tracepoint event and return
LoongArch: Mark __percpu functions as always inline
NFSD: Update nfsd_cache_append() to use xdr_stream
nfsd: fix file memleak on client_opens_release
dm-verity: don't use blocking calls from tasklets
dm-bufio: fix no-sleep mode
drm/mediatek/dp: fix memory leak on ->get_edid callback error path
drm/mediatek/dp: fix memory leak on ->get_edid callback audio detection
media: ccs: Correctly initialise try compose rectangle
media: venus: hfi: add checks to handle capabilities from firmware
media: venus: hfi: fix the check to handle session buffer requirement
media: venus: hfi_parser: Add check to keep the number of codecs within range
media: sharp: fix sharp encoding
media: lirc: drop trailing space from scancode transmit
f2fs: split initial and dynamic conditions for extent_cache
f2fs: avoid format-overflow warning
f2fs: set the default 

[Kernel-packages] [Bug 2044125] [NEW] Noble update: v6.6.1 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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

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

** Affects: linux (Ubuntu Noble)
 Importance: Undecided
 Status: Confirmed


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

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

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

Title:
  Noble update: v6.6.1 upstream stable release

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

Bug description:
  
  SRU Justification

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044125/+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 2044126] [NEW] Noble update: v6.6.2 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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


Linux 6.6.2
btrfs: make found_logical_ret parameter mandatory for function 
queue_scrub_stripe()
btrfs: use u64 for buffer sizes in the tree search ioctls
Revert "mmc: core: Capture correct oemid-bits for eMMC cards"
Revert "PCI/ASPM: Disable only ASPM_STATE_L1 when driver, disables L1"
x86/amd_nb: Use Family 19h Models 60h-7Fh Function 4 IDs
io_uring/net: ensure socket is marked connected on connect retry
selftests: mptcp: fix wait_rm_addr/sf parameters
selftests: mptcp: run userspace pm tests slower
eventfs: Check for NULL ef in eventfs_set_attr()
tracing/kprobes: Fix the order of argument descriptions
fbdev: fsl-diu-fb: mark wr_reg_wa() static
ALSA: hda/realtek: Add support dual speaker for Dell
fbdev: imsttfb: fix a resource leak in probe
fbdev: imsttfb: fix double free in probe()
arm64/arm: arm_pmuv3: perf: Don't truncate 64-bit registers
spi: spi-zynq-qspi: add spi-mem to driver kconfig dependencies
ASoC: dapm: fix clock get name
ASoC: hdmi-codec: register hpd callback on component probe
ASoC: mediatek: mt8186_mt6366_rt1019_rt5682s: trivial: fix error messages
ASoC: rt712-sdca: fix speaker route missing issue
drm/syncobj: fix DRM_SYNCOBJ_WAIT_FLAGS_WAIT_AVAILABLE
drm/vc4: tests: Fix UAF in the mock helpers
fs: dlm: Simplify buffer size computation in dlm_create_debug_file()
module/decompress: use kvmalloc() consistently
drivers: perf: Do not broadcast to other cpus when starting a counter
net: ti: icss-iep: fix setting counter value
RISC-V: Don't fail in riscv_of_parent_hartid() for disabled HARTs
net/sched: act_ct: Always fill offloading tuple iifidx
netfilter: nat: fix ipv6 nat redirect with mapped and scoped addresses
netfilter: xt_recent: fix (increase) ipv6 literal buffer length
i2c: iproc: handle invalid slave state
net: enetc: shorten enetc_setup_xdp_prog() error message to fit 
NETLINK_MAX_FMTMSG_LEN
virtio/vsock: Fix uninit-value in virtio_transport_recv_pkt()
r8169: respect userspace disabling IFF_MULTICAST
vsock/virtio: remove socket from connected/bound list on shutdown
blk-core: use pr_warn_ratelimited() in bio_check_ro()
nbd: fix uaf in nbd_open
tg3: power down device only on SYSTEM_POWER_OFF
ice: Fix VF-VF direction matching in drop rule in switchdev
ice: Fix VF-VF filter rules in switchdev mode
ice: lag: in RCU, use atomic allocation
ice: Fix SRIOV LAG disable on non-compliant aggregate
riscv: boot: Fix creation of loader.bin
nvme: fix error-handling for io_uring nvme-passthrough
net/smc: put sk reference if close work was canceled
net/smc: allow cdc msg send rather than drop it with NULL sndbuf_desc
net/smc: fix dangling sock under state SMC_APPFINCLOSEWAIT
octeontx2-pf: Free pending and dropped SQEs
selftests: pmtu.sh: fix result checking
net: stmmac: xgmac: Enable support for multiple Flexible PPS outputs
Fix termination state for idr_for_each_entry_ul()
net: r8169: Disable multicast filter for RTL8168H and RTL8107E
dccp/tcp: Call security_inet_conn_request() after setting IPv6 addresses.
dccp: Call security_inet_conn_request() after setting IPv4 addresses.
net: page_pool: add missing free_percpu when page_pool_init fail
octeontx2-pf: Fix holes in error code
octeontx2-pf: Fix error codes
inet: shrink struct flowi_common
bpf: Check map->usercnt after timer->timer is assigned
rxrpc: Fix two connection reaping bugs
tipc: Change nla_policy for bearer-related names to NLA_NUL_STRING
hsr: Prevent use after free in prp_create_tagged_frame()
llc: verify mac len before reading mac header
watchdog: ixp4xx: Make sure restart always works
watchdog: marvell_gti_wdt: Fix error code in probe()
Input: synaptics-rmi4 - fix use after free in rmi_unregister_function()
pwm: brcmstb: Utilize appropriate clock APIs in suspend/resume
pwm: sti: Reduce number of allocations and drop usage of chip_data
drm/amdgpu: don't put MQDs in VRAM on ARM | ARM64
drm/amdgpu/gfx10,11: use memcpy_to/fromio for MQDs
regmap: prevent noinc writes from clobbering cache
cpupower: fix reference to nonexistent document
media: cec: meson: always include meson sub-directory in Makefile
media: platform: mtk-mdp3: fix uninitialized variable in mdp_path_config()
media: mediatek: vcodec: using encoder device to alloc/free encoder memory
media: imx-jpeg: notify source chagne event when the first picture parsed
media: mediatek: vcodec: Handle invalid encoder vsi
media: verisilicon: Fixes clock list for rk3588 av1 decoder
media: dvb-usb-v2: af9035: fix missing unlock
media: cadence: 

[Kernel-packages] [Bug 2042565] [NEW] zfs-dkms DKMS FTBFS wrt Linux 6.6

[Paolo Pisati]

Public bug reported:

[Impact]

...
/var/lib/dkms/zfs/2.2.0/build/module/os/linux/zfs/zfs_ctldir.c: In function 
‘zfsctl_inode_alloc’:
/var/lib/dkms/zfs/2.2.0/build/module/os/linux/zfs/zfs_ctldir.c:525:13: error: 
‘struct inode’ has no member named ‘i_ctime’; did you mean ‘i_atime’?
  525 | ip->i_ctime = now;
  | ^~~
  | i_atime
...

[Fix]

Apply the attached fix.

[How to test]

Install (and build) the patched package.

[Regression potential]

...

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

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

Title:
  zfs-dkms DKMS FTBFS wrt Linux 6.6

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  [Impact]

  ...
  /var/lib/dkms/zfs/2.2.0/build/module/os/linux/zfs/zfs_ctldir.c: In function 
‘zfsctl_inode_alloc’:
  /var/lib/dkms/zfs/2.2.0/build/module/os/linux/zfs/zfs_ctldir.c:525:13: error: 
‘struct inode’ has no member named ‘i_ctime’; did you mean ‘i_atime’?
525 | ip->i_ctime = now;
| ^~~
| i_atime
  ...

  [Fix]

  Apply the attached fix.

  [How to test]

  Install (and build) the patched package.

  [Regression potential]

  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2042565/+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 2039280] Re: Support IP address protocol

[Paolo Pisati]

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

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

Title:
  Support IP address protocol

Status in iproute2 package in Ubuntu:
  New
Status in iproute2 source package in Mantic:
  New

Bug description:
  [Impact]

  IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
  provenance of the IP address. The attribute is modeled after ip route
  protocols, and essentially allows the administrator or userspace stack to
  tag addresses in some way that makes sense to the actor in question.
  Support for this feature was merged with commit 47f0bd503210 ("net: Add new
  protocol attribute to IP addresses"), for kernel 5.18.

  In this patch, add support for setting the protocol attribute at IP address
  addition, replacement, and listing requests.

  [Fix]

  Apply the attached patch

  [How to test]

  $ cat << EOF > test.sh
  #!/bin/sh

  addr=192.0.2.1/28
  addr2=${addr%/*}2/${addr#*/}
  ifr=test-dummy123

  sudo ip link add name "$ifr" type dummy
  sudo ip link set "$ifr" up

  sudo ip address add dev "$ifr" "$addr2" proto 0x99

  sudo ip link del "$ifr"
  EOF

  $chmod +x test.sh
  $test.sh
  $ echo $?
  0

  if you get an error instead, like:
  Error: either "local" is duplicate, or "proto" is a garbage.

  your iproute2 is not patched.
  Alternativerly, you could download Linux v6.5 source code and run:

  $ cd linux
  $ sudo ./tools/testing/selftests/net/rtnetlink.sh -t kci_test_address_proto

  [Regression potential]

  Two clean upstream cherry-picks, regression potential should be low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2039280/+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 2039280] Re: Support IP address protocol

[Paolo Pisati]

** Patch added: "iproute2_6.1.0-1ubuntu3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2039280/+attachment/5709212/+files/iproute2_6.1.0-1ubuntu3.debdiff

** Description changed:

  [Impact]
  
  IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
  provenance of the IP address. The attribute is modeled after ip route
  protocols, and essentially allows the administrator or userspace stack to
  tag addresses in some way that makes sense to the actor in question.
  Support for this feature was merged with commit 47f0bd503210 ("net: Add new
  protocol attribute to IP addresses"), for kernel 5.18.
  
  In this patch, add support for setting the protocol attribute at IP address
  addition, replacement, and listing requests.
  
  [Fix]
  
  Apply the attached patch
  
  [How to test]
  
  $ cat << EOF > test.sh
  #!/bin/sh
  
  addr=192.0.2.1/28
  addr2=${addr%/*}2/${addr#*/}
  ifr=test-dummy123
  
  sudo ip link add name "$ifr" type dummy
  sudo ip link set "$ifr" up
  
  sudo ip address add dev "$ifr" "$addr2" proto 0x99
  
  sudo ip link del "$ifr"
  EOF
  
  $chmod +x test.sh
  $test.sh
  $ echo $?
  0
  
  if you get an error instead, like:
  Error: either "local" is duplicate, or "proto" is a garbage.
  
  your iproute2 is not patched.
  Alternativerly, you could download Linux v6.5 source code and run:
  
  $ cd linux
  $ sudo ./tools/testing/selftests/net/rtnetlink.sh -t kci_test_address_proto
  
  [Regression potential]
  
- Two clean upstream cherry-picks so regression potential is low.
+ Two clean upstream cherry-picks, low regression potential is low.

** Description changed:

  [Impact]
  
  IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
  provenance of the IP address. The attribute is modeled after ip route
  protocols, and essentially allows the administrator or userspace stack to
  tag addresses in some way that makes sense to the actor in question.
  Support for this feature was merged with commit 47f0bd503210 ("net: Add new
  protocol attribute to IP addresses"), for kernel 5.18.
  
  In this patch, add support for setting the protocol attribute at IP address
  addition, replacement, and listing requests.
  
  [Fix]
  
  Apply the attached patch
  
  [How to test]
  
  $ cat << EOF > test.sh
  #!/bin/sh
  
  addr=192.0.2.1/28
  addr2=${addr%/*}2/${addr#*/}
  ifr=test-dummy123
  
  sudo ip link add name "$ifr" type dummy
  sudo ip link set "$ifr" up
  
  sudo ip address add dev "$ifr" "$addr2" proto 0x99
  
  sudo ip link del "$ifr"
  EOF
  
  $chmod +x test.sh
  $test.sh
  $ echo $?
  0
  
  if you get an error instead, like:
  Error: either "local" is duplicate, or "proto" is a garbage.
  
  your iproute2 is not patched.
  Alternativerly, you could download Linux v6.5 source code and run:
  
  $ cd linux
  $ sudo ./tools/testing/selftests/net/rtnetlink.sh -t kci_test_address_proto
  
  [Regression potential]
  
- Two clean upstream cherry-picks, low regression potential is low.
+ Two clean upstream cherry-picks, regression potential should be low.

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

Title:
  Support IP address protocol

Status in iproute2 package in Ubuntu:
  New

Bug description:
  [Impact]

  IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
  provenance of the IP address. The attribute is modeled after ip route
  protocols, and essentially allows the administrator or userspace stack to
  tag addresses in some way that makes sense to the actor in question.
  Support for this feature was merged with commit 47f0bd503210 ("net: Add new
  protocol attribute to IP addresses"), for kernel 5.18.

  In this patch, add support for setting the protocol attribute at IP address
  addition, replacement, and listing requests.

  [Fix]

  Apply the attached patch

  [How to test]

  $ cat << EOF > test.sh
  #!/bin/sh

  addr=192.0.2.1/28
  addr2=${addr%/*}2/${addr#*/}
  ifr=test-dummy123

  sudo ip link add name "$ifr" type dummy
  sudo ip link set "$ifr" up

  sudo ip address add dev "$ifr" "$addr2" proto 0x99

  sudo ip link del "$ifr"
  EOF

  $chmod +x test.sh
  $test.sh
  $ echo $?
  0

  if you get an error instead, like:
  Error: either "local" is duplicate, or "proto" is a garbage.

  your iproute2 is not patched.
  Alternativerly, you could download Linux v6.5 source code and run:

  $ cd linux
  $ sudo ./tools/testing/selftests/net/rtnetlink.sh -t kci_test_address_proto

  [Regression potential]

  Two clean upstream cherry-picks, regression potential should be low.

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


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

[Kernel-packages] [Bug 2039280] Re: Support IP address protocol

[Paolo Pisati]

** Description changed:

  [Impact]
  
  IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
  provenance of the IP address. The attribute is modeled after ip route
  protocols, and essentially allows the administrator or userspace stack to
  tag addresses in some way that makes sense to the actor in question.
  Support for this feature was merged with commit 47f0bd503210 ("net: Add new
  protocol attribute to IP addresses"), for kernel 5.18.
- 
+ 
  In this patch, add support for setting the protocol attribute at IP address
  addition, replacement, and listing requests.
- 
  
  [Fix]
  
  Apply the attached patch
  
  [How to test]
  
  $ cat << EOF > test.sh
  #!/bin/sh
  
  addr=192.0.2.1/28
  addr2=${addr%/*}2/${addr#*/}
  ifr=test-dummy123
  
  sudo ip link add name "$ifr" type dummy
  sudo ip link set "$ifr" up
  
  sudo ip address add dev "$ifr" "$addr2" proto 0x99
  
  sudo ip link del "$ifr"
  EOF
  
  $chmod +x test.sh
  $test.sh
  $ echo $?
  0
  
  if you get an error instead, like:
  Error: either "local" is duplicate, or "proto" is a garbage.
  
  your iproute2 is not patched.
- Alternativerly, you could download Linux v6.5 and run:
+ Alternativerly, you could download Linux v6.5 source code and run:
  
- $ sudo ./tools/testing/selftests/net/rtnetlink.sh -t
- kci_test_address_proto
- 
+ $ cd linux
+ $ sudo ./tools/testing/selftests/net/rtnetlink.sh -t kci_test_address_proto
  
  [Regression potential]
  
  The cherry-picked patches are 2 upstream commits so regression potential
  is low.

** Description changed:

  [Impact]
  
  IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
  provenance of the IP address. The attribute is modeled after ip route
  protocols, and essentially allows the administrator or userspace stack to
  tag addresses in some way that makes sense to the actor in question.
  Support for this feature was merged with commit 47f0bd503210 ("net: Add new
  protocol attribute to IP addresses"), for kernel 5.18.
  
  In this patch, add support for setting the protocol attribute at IP address
  addition, replacement, and listing requests.
  
  [Fix]
  
  Apply the attached patch
  
  [How to test]
  
  $ cat << EOF > test.sh
  #!/bin/sh
  
  addr=192.0.2.1/28
  addr2=${addr%/*}2/${addr#*/}
  ifr=test-dummy123
  
  sudo ip link add name "$ifr" type dummy
  sudo ip link set "$ifr" up
  
  sudo ip address add dev "$ifr" "$addr2" proto 0x99
  
  sudo ip link del "$ifr"
  EOF
  
  $chmod +x test.sh
  $test.sh
  $ echo $?
  0
  
  if you get an error instead, like:
  Error: either "local" is duplicate, or "proto" is a garbage.
  
  your iproute2 is not patched.
  Alternativerly, you could download Linux v6.5 source code and run:
  
  $ cd linux
  $ sudo ./tools/testing/selftests/net/rtnetlink.sh -t kci_test_address_proto
  
  [Regression potential]
  
- The cherry-picked patches are 2 upstream commits so regression potential
- is low.
+ Two clean upstream cherry-picks so regression potential is low.

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

Title:
  Support IP address protocol

Status in iproute2 package in Ubuntu:
  New

Bug description:
  [Impact]

  IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
  provenance of the IP address. The attribute is modeled after ip route
  protocols, and essentially allows the administrator or userspace stack to
  tag addresses in some way that makes sense to the actor in question.
  Support for this feature was merged with commit 47f0bd503210 ("net: Add new
  protocol attribute to IP addresses"), for kernel 5.18.

  In this patch, add support for setting the protocol attribute at IP address
  addition, replacement, and listing requests.

  [Fix]

  Apply the attached patch

  [How to test]

  $ cat << EOF > test.sh
  #!/bin/sh

  addr=192.0.2.1/28
  addr2=${addr%/*}2/${addr#*/}
  ifr=test-dummy123

  sudo ip link add name "$ifr" type dummy
  sudo ip link set "$ifr" up

  sudo ip address add dev "$ifr" "$addr2" proto 0x99

  sudo ip link del "$ifr"
  EOF

  $chmod +x test.sh
  $test.sh
  $ echo $?
  0

  if you get an error instead, like:
  Error: either "local" is duplicate, or "proto" is a garbage.

  your iproute2 is not patched.
  Alternativerly, you could download Linux v6.5 source code and run:

  $ cd linux
  $ sudo ./tools/testing/selftests/net/rtnetlink.sh -t kci_test_address_proto

  [Regression potential]

  Two clean upstream cherry-picks so regression potential is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2039280/+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 2039280] [NEW] Support IP address protocol

[Paolo Pisati]

Public bug reported:

[Impact]

IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
provenance of the IP address. The attribute is modeled after ip route
protocols, and essentially allows the administrator or userspace stack to
tag addresses in some way that makes sense to the actor in question.
Support for this feature was merged with commit 47f0bd503210 ("net: Add new
protocol attribute to IP addresses"), for kernel 5.18.

In this patch, add support for setting the protocol attribute at IP address
addition, replacement, and listing requests.


[Fix]

Apply the attached patch

[How to test]

$ cat << EOF > test.sh
#!/bin/sh

addr=192.0.2.1/28
addr2=${addr%/*}2/${addr#*/}
ifr=test-dummy123

sudo ip link add name "$ifr" type dummy
sudo ip link set "$ifr" up

sudo ip address add dev "$ifr" "$addr2" proto 0x99

sudo ip link del "$ifr"
EOF

$chmod +x test.sh
$test.sh
$ echo $?
0

if you get an error instead, like:
Error: either "local" is duplicate, or "proto" is a garbage.

your iproute2 is not patched.
Alternativerly, you could download Linux v6.5 and run:

$ sudo ./tools/testing/selftests/net/rtnetlink.sh -t
kci_test_address_proto


[Regression potential]

The cherry-picked patches are 2 upstream commits so regression potential
is low.

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

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

Title:
  Support IP address protocol

Status in iproute2 package in Ubuntu:
  New

Bug description:
  [Impact]

  IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
  provenance of the IP address. The attribute is modeled after ip route
  protocols, and essentially allows the administrator or userspace stack to
  tag addresses in some way that makes sense to the actor in question.
  Support for this feature was merged with commit 47f0bd503210 ("net: Add new
  protocol attribute to IP addresses"), for kernel 5.18.
  
  In this patch, add support for setting the protocol attribute at IP address
  addition, replacement, and listing requests.

  
  [Fix]

  Apply the attached patch

  [How to test]

  $ cat << EOF > test.sh
  #!/bin/sh

  addr=192.0.2.1/28
  addr2=${addr%/*}2/${addr#*/}
  ifr=test-dummy123

  sudo ip link add name "$ifr" type dummy
  sudo ip link set "$ifr" up

  sudo ip address add dev "$ifr" "$addr2" proto 0x99

  sudo ip link del "$ifr"
  EOF

  $chmod +x test.sh
  $test.sh
  $ echo $?
  0

  if you get an error instead, like:
  Error: either "local" is duplicate, or "proto" is a garbage.

  your iproute2 is not patched.
  Alternativerly, you could download Linux v6.5 and run:

  $ sudo ./tools/testing/selftests/net/rtnetlink.sh -t
  kci_test_address_proto

  
  [Regression potential]

  The cherry-picked patches are 2 upstream commits so regression
  potential is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2039280/+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 2031302] Re: test_290_config_hardened_usercopy in ubuntu_qrt_kernel_security failed with J-oem-6.5 / M-linux (HAVE_HARDENED_USERCOPY_ALLOCATOR does not exist anymore)

[Paolo Pisati]

** No longer affects: linux (Ubuntu Mantic)

** No longer affects: linux (Ubuntu)

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

Title:
  test_290_config_hardened_usercopy in ubuntu_qrt_kernel_security failed
  with J-oem-6.5 / M-linux (HAVE_HARDENED_USERCOPY_ALLOCATOR does not
  exist anymore)

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  New

Bug description:
  This test requires HARDENED_USERCOPY to be unset.

  Test log:
   Running 'python3 ./test-kernel-security.py -v 
KernelSecurityConfigTest.test_290_config_hardened_usercopy'
   Running test: './test-kernel-security.py' distro: 'Ubuntu 22.04' kernel: 
'6.5.0-1002.2 (Ubuntu 6.5.0-1002.2-oem 6.5.0-rc4)' arch: 'amd64' init: 
'systemd' uid: 0/0 SUDO_USER: 'ubuntu')
   test_290_config_hardened_usercopy (__main__.KernelSecurityConfigTest)
   Ensure CONFIG_HARDENED_USERCOPY is set ... (skipped: HARDENED_USERCOPY 
depends on the allocator and strict devmem) FAIL
   
   ==
   FAIL: test_290_config_hardened_usercopy (__main__.KernelSecurityConfigTest)
   Ensure CONFIG_HARDENED_USERCOPY is set
   --
   Traceback (most recent call last):
 File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py",
 line 2724, in test_290_config_hardened_usercopy
   self.assertKernelConfigUnset(config_name)
 File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py",
 line 223, in assertKernelConfigUnset
   self.assertFalse(self._test_config(name),
   AssertionError: True is not false : HARDENED_USERCOPY option was expected to 
be unset in the kernel config
   
   --
   Ran 1 test in 0.007s
   
   FAILED (failures=1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/2031302/+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 2031302] Re: test_290_config_hardened_usercopy in ubuntu_qrt_kernel_security failed with J-oem-6.5 / M-linux (HAVE_HARDENED_USERCOPY_ALLOCATOR does not exist anymore)

[Paolo Pisati]

** Summary changed:

- test_290_config_hardened_usercopy in ubuntu_qrt_kernel_security failed with 
J-oem-6.5 (HAVE_HARDENED_USERCOPY_ALLOCATOR does not exist anymore)
+ test_290_config_hardened_usercopy in ubuntu_qrt_kernel_security failed with 
J-oem-6.5 / M-linux (HAVE_HARDENED_USERCOPY_ALLOCATOR does not exist anymore)

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

Title:
  test_290_config_hardened_usercopy in ubuntu_qrt_kernel_security failed
  with J-oem-6.5 / M-linux (HAVE_HARDENED_USERCOPY_ALLOCATOR does not
  exist anymore)

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  New
Status in linux source package in Mantic:
  Incomplete

Bug description:
  This test requires HARDENED_USERCOPY to be unset.

  Test log:
   Running 'python3 ./test-kernel-security.py -v 
KernelSecurityConfigTest.test_290_config_hardened_usercopy'
   Running test: './test-kernel-security.py' distro: 'Ubuntu 22.04' kernel: 
'6.5.0-1002.2 (Ubuntu 6.5.0-1002.2-oem 6.5.0-rc4)' arch: 'amd64' init: 
'systemd' uid: 0/0 SUDO_USER: 'ubuntu')
   test_290_config_hardened_usercopy (__main__.KernelSecurityConfigTest)
   Ensure CONFIG_HARDENED_USERCOPY is set ... (skipped: HARDENED_USERCOPY 
depends on the allocator and strict devmem) FAIL
   
   ==
   FAIL: test_290_config_hardened_usercopy (__main__.KernelSecurityConfigTest)
   Ensure CONFIG_HARDENED_USERCOPY is set
   --
   Traceback (most recent call last):
 File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py",
 line 2724, in test_290_config_hardened_usercopy
   self.assertKernelConfigUnset(config_name)
 File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py",
 line 223, in assertKernelConfigUnset
   self.assertFalse(self._test_config(name),
   AssertionError: True is not false : HARDENED_USERCOPY option was expected to 
be unset in the kernel config
   
   --
   Ran 1 test in 0.007s
   
   FAILED (failures=1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/2031302/+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 2031302] Re: test_290_config_hardened_usercopy in ubuntu_qrt_kernel_security failed with J-oem-6.5 (HAVE_HARDENED_USERCOPY_ALLOCATOR does not exist anymore)

[Paolo Pisati]

I've sent a pull req to fix the test:

https://code.launchpad.net/~p-pisati/qa-regression-testing/+git/qa-
regression-testing/+merge/453326

basically, the HAVE_HARDENED_USERCOPY_ALLOCATOR has been retired in
v6.5-rc1 so the test thinks the option is off and thus the test should
always fail.

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

** No longer affects: linux (Ubuntu Jammy)

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

** Also affects: linux-oem-6.5 (Ubuntu Mantic)
   Importance: Undecided
   Status: Invalid

** No longer affects: linux-oem-6.5 (Ubuntu Mantic)

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

Title:
  test_290_config_hardened_usercopy in ubuntu_qrt_kernel_security failed
  with J-oem-6.5 / M-linux (HAVE_HARDENED_USERCOPY_ALLOCATOR does not
  exist anymore)

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  New
Status in linux source package in Mantic:
  Incomplete

Bug description:
  This test requires HARDENED_USERCOPY to be unset.

  Test log:
   Running 'python3 ./test-kernel-security.py -v 
KernelSecurityConfigTest.test_290_config_hardened_usercopy'
   Running test: './test-kernel-security.py' distro: 'Ubuntu 22.04' kernel: 
'6.5.0-1002.2 (Ubuntu 6.5.0-1002.2-oem 6.5.0-rc4)' arch: 'amd64' init: 
'systemd' uid: 0/0 SUDO_USER: 'ubuntu')
   test_290_config_hardened_usercopy (__main__.KernelSecurityConfigTest)
   Ensure CONFIG_HARDENED_USERCOPY is set ... (skipped: HARDENED_USERCOPY 
depends on the allocator and strict devmem) FAIL
   
   ==
   FAIL: test_290_config_hardened_usercopy (__main__.KernelSecurityConfigTest)
   Ensure CONFIG_HARDENED_USERCOPY is set
   --
   Traceback (most recent call last):
 File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py",
 line 2724, in test_290_config_hardened_usercopy
   self.assertKernelConfigUnset(config_name)
 File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py",
 line 223, in assertKernelConfigUnset
   self.assertFalse(self._test_config(name),
   AssertionError: True is not false : HARDENED_USERCOPY option was expected to 
be unset in the kernel config
   
   --
   Ran 1 test in 0.007s
   
   FAILED (failures=1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/2031302/+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 2028165] Re: nvidia-dkms-* FTBS with linux 6.5

[Paolo Pisati]

** Patch added: "nvidia-graphics-drivers-525_525.125.06-0ubuntu4.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+attachment/5696045/+files/nvidia-graphics-drivers-525_525.125.06-0ubuntu4.debdiff

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
https://bugs.launchpad.net/bugs/2028165

Title:
  nvidia-dkms-* FTBS with linux 6.5

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Mantic:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Mantic:
  In Progress
Status in nvidia-graphics-drivers-525-server source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  ...
  In file included from 
/var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21,
   from 
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function 
‘NV_GET_USER_PAGES_REMOTE’:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing 
argument 1 of ‘get_user_pages_remote’ from incompatible pointer type 
[-Werror=incompatible-pointer-types]
    164 |return get_user_pages_remote(tsk, mm, start, nr_pages, 
flags,
    | ^~~
    | |
    | struct task_struct *
  ...

  
  [Fix]

  Apply the attached fix.

  [How to test]

  Install (and build) the patched packet.

  [Regression potential]

  The fix is composed of two patches:

  1) the first patch simply garbage collect a reference to a function
  that was never used but that had the API changed in Linux 6.5 - so,
  it's a trivial change.

  2) the second patch actually reimplement part of the vma scanning that was 
removed in __get_user_pages_locked() in upstream commit 
b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas
  array from internal GUP functions" - here is where most likely any regression 
could be found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+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 2028165] Re: nvidia-dkms-* FTBS with linux 6.5

[Paolo Pisati]

450-server Linux 6.5 fix.

** Also affects: nvidia-graphics-drivers-450-server (Ubuntu)
   Importance: Undecided
   Status: New

** Patch added: "nvidia-graphics-drivers-450-server_450.248.02-0ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450-server/+bug/2028165/+attachment/5688839/+files/nvidia-graphics-drivers-450-server_450.248.02-0ubuntu2.debdiff

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
https://bugs.launchpad.net/bugs/2028165

Title:
  nvidia-dkms-* FTBS with linux 6.5

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Mantic:
  New
Status in nvidia-graphics-drivers-470 source package in Mantic:
  In Progress
Status in nvidia-graphics-drivers-470-server source package in Mantic:
  In Progress
Status in nvidia-graphics-drivers-525 source package in Mantic:
  In Progress
Status in nvidia-graphics-drivers-525-server source package in Mantic:
  New

Bug description:
  [Impact]

  ...
  In file included from 
/var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21,
   from 
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function 
‘NV_GET_USER_PAGES_REMOTE’:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing 
argument 1 of ‘get_user_pages_remote’ from incompatible pointer type 
[-Werror=incompatible-pointer-types]
    164 |return get_user_pages_remote(tsk, mm, start, nr_pages, 
flags,
    | ^~~
    | |
    | struct task_struct *
  ...

  
  [Fix]

  Apply the attached fix.

  [How to test]

  Install (and build) the patched packet.

  [Regression potential]

  The fix is composed of two patches:

  1) the first patch simply garbage collect a reference to a function
  that was never used but that had the API changed in Linux 6.5 - so,
  it's a trivial change.

  2) the second patch actually reimplement part of the vma scanning that was 
removed in __get_user_pages_locked() in upstream commit 
b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas
  array from internal GUP functions" - here is where most likely any regression 
could be found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+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 2028165] Re: nvidia-dkms-* FTBS with linux 6.5

[Paolo Pisati]

525-server fix for Linux 6.5

** Also affects: nvidia-graphics-drivers-525-server (Ubuntu)
   Importance: Undecided
   Status: New

** Patch added: "nvidia-graphics-drivers-525-server_525.125.06-0ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525-server/+bug/2028165/+attachment/5688552/+files/nvidia-graphics-drivers-525-server_525.125.06-0ubuntu2.debdiff

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
https://bugs.launchpad.net/bugs/2028165

Title:
  nvidia-dkms-* FTBS with linux 6.5

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  In Progress
Status in nvidia-graphics-drivers-470 source package in Mantic:
  In Progress
Status in nvidia-graphics-drivers-470-server source package in Mantic:
  In Progress
Status in nvidia-graphics-drivers-525 source package in Mantic:
  In Progress
Status in nvidia-graphics-drivers-525-server source package in Mantic:
  New

Bug description:
  [Impact]

  ...
  In file included from 
/var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21,
   from 
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function 
‘NV_GET_USER_PAGES_REMOTE’:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing 
argument 1 of ‘get_user_pages_remote’ from incompatible pointer type 
[-Werror=incompatible-pointer-types]
    164 |return get_user_pages_remote(tsk, mm, start, nr_pages, 
flags,
    | ^~~
    | |
    | struct task_struct *
  ...

  
  [Fix]

  Apply the attached fix.

  [How to test]

  Install (and build) the patched packet.

  [Regression potential]

  The fix is composed of two patches:

  1) the first patch simply garbage collect a reference to a function
  that was never used but that had the API changed in Linux 6.5 - so,
  it's a trivial change.

  2) the second patch actually reimplement part of the vma scanning that was 
removed in __get_user_pages_locked() in upstream commit 
b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas
  array from internal GUP functions" - here is where most likely any regression 
could be found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+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 2028165] Re: nvidia-dkms-* FTBS with linux 6.5

[Paolo Pisati]

** Patch added: "nvidia-graphics-drivers-470-server_470.199.02-0ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+attachment/5688347/+files/nvidia-graphics-drivers-470-server_470.199.02-0ubuntu2.debdiff

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

Title:
  nvidia-dkms-* FTBS with linux 6.5

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Mantic:
  In Progress
Status in nvidia-graphics-drivers-470 source package in Mantic:
  In Progress
Status in nvidia-graphics-drivers-470-server source package in Mantic:
  In Progress
Status in nvidia-graphics-drivers-525 source package in Mantic:
  In Progress

Bug description:
  [Impact]

  ...
  In file included from 
/var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21,
   from 
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function 
‘NV_GET_USER_PAGES_REMOTE’:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing 
argument 1 of ‘get_user_pages_remote’ from incompatible pointer type 
[-Werror=incompatible-pointer-types]
    164 |return get_user_pages_remote(tsk, mm, start, nr_pages, 
flags,
    | ^~~
    | |
    | struct task_struct *
  ...

  
  [Fix]

  Apply the attached fix.

  [How to test]

  Install (and build) the patched packet.

  [Regression potential]

  The fix is composed of two patches:

  1) the first patch simply garbage collect a reference to a function
  that was never used but that had the API changed in Linux 6.5 - so,
  it's a trivial change.

  2) the second patch actually reimplement part of the vma scanning that was 
removed in __get_user_pages_locked() in upstream commit 
b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas
  array from internal GUP functions" - here is where most likely any regression 
could be found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+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 2028165] Re: nvidia-dkms-* FTBS with linux 6.5

[Paolo Pisati]

New patch for the 470 driver

** Patch added: "nvidia-graphics-drivers-470_470.199.02-0ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+attachment/5688321/+files/nvidia-graphics-drivers-470_470.199.02-0ubuntu2.debdiff

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

Title:
  nvidia-dkms-* FTBS with linux 6.5

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Mantic:
  In Progress
Status in nvidia-graphics-drivers-470 source package in Mantic:
  In Progress
Status in nvidia-graphics-drivers-470-server source package in Mantic:
  In Progress
Status in nvidia-graphics-drivers-525 source package in Mantic:
  In Progress

Bug description:
  [Impact]

  ...
  In file included from 
/var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21,
   from 
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function 
‘NV_GET_USER_PAGES_REMOTE’:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing 
argument 1 of ‘get_user_pages_remote’ from incompatible pointer type 
[-Werror=incompatible-pointer-types]
    164 |return get_user_pages_remote(tsk, mm, start, nr_pages, 
flags,
    | ^~~
    | |
    | struct task_struct *
  ...

  
  [Fix]

  Apply the attached fix.

  [How to test]

  Install (and build) the patched packet.

  [Regression potential]

  The fix is composed of two patches:

  1) the first patch simply garbage collect a reference to a function
  that was never used but that had the API changed in Linux 6.5 - so,
  it's a trivial change.

  2) the second patch actually reimplement part of the vma scanning that was 
removed in __get_user_pages_locked() in upstream commit 
b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas
  array from internal GUP functions" - here is where most likely any regression 
could be found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+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 2028165] Re: nvidia-dkms-* FTBS with linux 6.5

[Paolo Pisati]

** Also affects: nvidia-graphics-drivers-470-server (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
https://bugs.launchpad.net/bugs/2028165

Title:
  nvidia-dkms-* FTBS with linux 6.5

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New
Status in nvidia-graphics-drivers-470 source package in Mantic:
  New
Status in nvidia-graphics-drivers-470-server source package in Mantic:
  New
Status in nvidia-graphics-drivers-525 source package in Mantic:
  New

Bug description:
  [Impact]

  ...
  In file included from 
/var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21,
   from 
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function 
‘NV_GET_USER_PAGES_REMOTE’:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing 
argument 1 of ‘get_user_pages_remote’ from incompatible pointer type 
[-Werror=incompatible-pointer-types]
    164 |return get_user_pages_remote(tsk, mm, start, nr_pages, 
flags,
    | ^~~
    | |
    | struct task_struct *
  ...

  
  [Fix]

  Apply the attached fix.

  [How to test]

  Install (and build) the patched packet.

  [Regression potential]

  The fix is composed of two patches:

  1) the first patch simply garbage collect a reference to a function
  that was never used but that had the API changed in Linux 6.5 - so,
  it's a trivial change.

  2) the second patch actually reimplement part of the vma scanning that was 
removed in __get_user_pages_locked() in upstream commit 
b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas
  array from internal GUP functions" - here is where most likely any regression 
could be found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+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 2028165] Re: nvidia-dkms-* FTBS with linux 6.5

[Paolo Pisati]

** Patch added: "nvidia-graphics-drivers-470_470.199.02-0ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525/+bug/2028165/+attachment/5688058/+files/nvidia-graphics-drivers-470_470.199.02-0ubuntu2.debdiff

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

Title:
  nvidia-dkms-* FTBS with linux 6.5

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New
Status in nvidia-graphics-drivers-470 source package in Mantic:
  New
Status in nvidia-graphics-drivers-525 source package in Mantic:
  New

Bug description:
  [Impact]

  ...
  In file included from 
/var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21,
   from 
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function 
‘NV_GET_USER_PAGES_REMOTE’:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing 
argument 1 of ‘get_user_pages_remote’ from incompatible pointer type 
[-Werror=incompatible-pointer-types]
    164 |return get_user_pages_remote(tsk, mm, start, nr_pages, 
flags,
    | ^~~
    | |
    | struct task_struct *
  ...

  
  [Fix]

  Apply the attached fix.

  [How to test]

  Install (and build) the patched packet.

  [Regression potential]

  The fix is composed of two patches:

  1) the first patch simply garbage collect a reference to a function
  that was never used but that had the API changed in Linux 6.5 - so,
  it's a trivial change.

  2) the second patch actually reimplement part of the vma scanning that was 
removed in __get_user_pages_locked() in upstream commit 
b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas
  array from internal GUP functions" - here is where most likely any regression 
could be found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+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 2028165] Re: nvidia-dkms-* FTBS with linux 6.5

[Paolo Pisati]

** Also affects: nvidia-graphics-drivers-470 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  nvidia-dkms-* FTBS with linux 6.5

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New
Status in nvidia-graphics-drivers-470 source package in Mantic:
  New
Status in nvidia-graphics-drivers-525 source package in Mantic:
  New

Bug description:
  [Impact]

  ...
  In file included from 
/var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21,
   from 
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function 
‘NV_GET_USER_PAGES_REMOTE’:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing 
argument 1 of ‘get_user_pages_remote’ from incompatible pointer type 
[-Werror=incompatible-pointer-types]
    164 |return get_user_pages_remote(tsk, mm, start, nr_pages, 
flags,
    | ^~~
    | |
    | struct task_struct *
  ...

  
  [Fix]

  Apply the attached fix.

  [How to test]

  Install (and build) the patched packet.

  [Regression potential]

  The fix is composed of two patches:

  1) the first patch simply garbage collect a reference to a function
  that was never used but that had the API changed in Linux 6.5 - so,
  it's a trivial change.

  2) the second patch actually reimplement part of the vma scanning that was 
removed in __get_user_pages_locked() in upstream commit 
b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas
  array from internal GUP functions" - here is where most likely any regression 
could be found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+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 2028165] Re: nvidia-dkms-* FTBS with linux 6.5

[Paolo Pisati]

** Patch added: "nvidia-graphics-drivers-525_525.125.06-0ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525/+bug/2028165/+attachment/5687461/+files/nvidia-graphics-drivers-525_525.125.06-0ubuntu2.debdiff

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

Title:
  nvidia-dkms-* FTBS with linux 6.5

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New
Status in nvidia-graphics-drivers-525 source package in Mantic:
  New

Bug description:
  [Impact]

  ...
  In file included from 
/var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21,
   from 
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function 
‘NV_GET_USER_PAGES_REMOTE’:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing 
argument 1 of ‘get_user_pages_remote’ from incompatible pointer type 
[-Werror=incompatible-pointer-types]
    164 |return get_user_pages_remote(tsk, mm, start, nr_pages, 
flags,
    | ^~~
    | |
    | struct task_struct *
  ...

  
  [Fix]

  Apply the attached fix.

  [How to test]

  Install (and build) the patched packet.

  [Regression potential]

  The fix is composed of two patches:

  1) the first patch simply garbage collect a reference to a function
  that was never used but that had the API changed in Linux 6.5 - so,
  it's a trivial change.

  2) the second patch actually reimplement part of the vma scanning that was 
removed in __get_user_pages_locked() in upstream commit 
b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas
  array from internal GUP functions" - here is where most likely any regression 
could be found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+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 2028165] Re: nvidia-dkms-* FTBS with linux 6.5

[Paolo Pisati]

** Also affects: nvidia-graphics-drivers-525 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  nvidia-dkms-* FTBS with linux 6.5

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New
Status in nvidia-graphics-drivers-525 source package in Mantic:
  New

Bug description:
  [Impact]

  ...
  In file included from 
/var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21,
   from 
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function 
‘NV_GET_USER_PAGES_REMOTE’:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing 
argument 1 of ‘get_user_pages_remote’ from incompatible pointer type 
[-Werror=incompatible-pointer-types]
    164 |return get_user_pages_remote(tsk, mm, start, nr_pages, 
flags,
    | ^~~
    | |
    | struct task_struct *
  ...

  
  [Fix]

  Apply the attached fix.

  [How to test]

  Install (and build) the patched packet.

  [Regression potential]

  The fix is composed of two patches:

  1) the first patch simply garbage collect a reference to a function
  that was never used but that had the API changed in Linux 6.5 - so,
  it's a trivial change.

  2) the second patch actually reimplement part of the vma scanning that was 
removed in __get_user_pages_locked() in upstream commit 
b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas
  array from internal GUP functions" - here is where most likely any regression 
could be found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+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 2028165] Re: nvidia-dkms-* FTBS with linux 6.5

[Paolo Pisati]

** Patch added: "nvidia-graphics-drivers-390_390.157-0ubuntu8.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+attachment/5687148/+files/nvidia-graphics-drivers-390_390.157-0ubuntu8.debdiff

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

Title:
  nvidia-dkms-* FTBS with linux 6.5

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New

Bug description:
  [Impact]

  ...
  In file included from 
/var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21,
   from 
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function 
‘NV_GET_USER_PAGES_REMOTE’:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing 
argument 1 of ‘get_user_pages_remote’ from incompatible pointer type 
[-Werror=incompatible-pointer-types]
    164 |return get_user_pages_remote(tsk, mm, start, nr_pages, 
flags,
    | ^~~
    | |
    | struct task_struct *
  ...

  
  [Fix]

  Apply the attached fix.

  [How to test]

  Install (and build) the patched packet.

  [Regression potential]

  The fix is composed of two patches:

  1) the first patch simply garbage collect a reference to a function
  that was never used but that had the API changed in Linux 6.5 - so,
  it's a trivial change.

  2) the second patch actually reimplement part of the vma scanning that was 
removed in __get_user_pages_locked() in upstream commit 
b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas
  array from internal GUP functions" - here is where most likely any regression 
could be found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+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 2028165] [NEW] nvidia-dkms-* FTBS with linux 6.5

[Paolo Pisati]

Public bug reported:

[Impact]

...
In file included from 
/var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21,
 from 
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13:
/var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function 
‘NV_GET_USER_PAGES_REMOTE’:
/var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing 
argument 1 of ‘get_user_pages_remote’ from incompatible pointer type 
[-Werror=incompatible-pointer-types]
  164 |return get_user_pages_remote(tsk, mm, start, nr_pages, 
flags,
  | ^~~
  | |
  | struct task_struct *
...


[Fix]

Apply the attached fix.

[How to test]

Install (and build) the patched packet.

[Regression potential]

The fix is composed of two patches:

1) the first patch simply garbage collect a reference to a function that
was never used but that had the API changed in Linux 6.5 - so, it's a
trivial change.

2) the second patch actually reimplement part of the vma scanning that was 
removed in __get_user_pages_locked() in upstream commit 
b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas
array from internal GUP functions" - here is where most likely any regression 
could be found.

** Affects: nvidia-graphics-drivers-390 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: nvidia-graphics-drivers-390 (Ubuntu Mantic)
 Importance: Undecided
 Status: New

** Description changed:

  [Impact]
+ 
+ In file included from 
/var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21,
+  from 
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13:
+ /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function 
‘NV_GET_USER_PAGES_REMOTE’:
+ /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing 
argument 1 of ‘get_user_pages_remote’ from incompatible pointer type 
[-Werror=incompatible-pointer-types]
+   164 |return get_user_pages_remote(tsk, mm, start, nr_pages, 
flags,
+   | ^~~
+   | |
+   | struct task_struct *
+ 
  
  [Fix]
  
+ Apply the attached fix.
+ 
  [How to test]
  
+ Install (and build) the patched packet.
+ 
  [Regression potential]
+ 
+ The fix is composed of two patches:

** Description changed:

  [Impact]
  
  In file included from 
/var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21,
-  from 
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13:
+  from 
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function 
‘NV_GET_USER_PAGES_REMOTE’:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing 
argument 1 of ‘get_user_pages_remote’ from incompatible pointer type 
[-Werror=incompatible-pointer-types]
-   164 |return get_user_pages_remote(tsk, mm, start, nr_pages, 
flags,
-   | ^~~
-   | |
-   | struct task_struct *
- 
+   164 |return get_user_pages_remote(tsk, mm, start, nr_pages, 
flags,
+   | ^~~
+   | |
+   | struct task_struct *
  
  [Fix]
  
  Apply the attached fix.
  
  [How to test]
  
  Install (and build) the patched packet.
  
  [Regression potential]
  
  The fix is composed of two patches:
+ 
+ 1) the first patch simply garbage collect a reference to a function that
+ was never used but that had the API changed in Linux 6.5 - so, it's a
+ trivial change.
+ 
+ 2) the second patch actually reimplement part of the vma scanning that was 
removed in __get_user_pages_locked() in upstream commit 
b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas
+ array from internal GUP functions" - here is where most likely any regression 
could be found.

** Also affects: nvidia-graphics-drivers-390 (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Description changed:

  [Impact]
  
+ ...
  In file included from 
/var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21,
   from 
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function 
‘NV_GET_USER_PAGES_REMOTE’:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing 
argument 1 of ‘get_user_pages_remote’ from incompatible pointer type 
[-Werror=incompatible-pointer-types]
    164 |return get_user_pages_remote(tsk, mm, start, nr_pages, 
flags,
    |  

[Kernel-packages] [Bug 2025266] Re: nvidia-dkms-* FTBS with linux 6.4

[Paolo Pisati]

** Also affects: nvidia-graphics-drivers-515 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-510 (Ubuntu Mantic)
   Status: New => Won't Fix

** Changed in: nvidia-graphics-drivers-515 (Ubuntu Mantic)
   Status: New => Won't Fix

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

Title:
  nvidia-dkms-* FTBS with linux 6.4

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New
Status in nvidia-graphics-drivers-470 source package in Mantic:
  New
Status in nvidia-graphics-drivers-510 source package in Mantic:
  Won't Fix
Status in nvidia-graphics-drivers-515 source package in Mantic:
  Won't Fix

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c: In function 
‘nv_drm_update_drm_driver_features’:
  /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c:769:18: error: 
‘struct drm_driver’ has no member named ‘dumb_destroy’
769 | nv_drm_driver.dumb_destroy = nv_drm_dumb_destroy;
|  ^
  make[2]: *** [scripts/Makefile.build:260: 
/var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.o] Error 1

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2025266/+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 2025266] Re: nvidia-dkms-* FTBS with linux 6.4

[Paolo Pisati]

** Also affects: nvidia-graphics-drivers-510 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  nvidia-dkms-* FTBS with linux 6.4

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New
Status in nvidia-graphics-drivers-470 source package in Mantic:
  New
Status in nvidia-graphics-drivers-510 source package in Mantic:
  New

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c: In function 
‘nv_drm_update_drm_driver_features’:
  /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c:769:18: error: 
‘struct drm_driver’ has no member named ‘dumb_destroy’
769 | nv_drm_driver.dumb_destroy = nv_drm_dumb_destroy;
|  ^
  make[2]: *** [scripts/Makefile.build:260: 
/var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.o] Error 1

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2025266/+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 2025266] Re: nvidia-dkms-* FTBS with linux 6.4

[Paolo Pisati]

** Patch added: "nvidia-graphics-drivers-470_470.182.03-0ubuntu3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2025266/+attachment/5682856/+files/nvidia-graphics-drivers-470_470.182.03-0ubuntu3.debdiff

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

Title:
  nvidia-dkms-* FTBS with linux 6.4

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New
Status in nvidia-graphics-drivers-470 source package in Mantic:
  New

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c: In function 
‘nv_drm_update_drm_driver_features’:
  /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c:769:18: error: 
‘struct drm_driver’ has no member named ‘dumb_destroy’
769 | nv_drm_driver.dumb_destroy = nv_drm_dumb_destroy;
|  ^
  make[2]: *** [scripts/Makefile.build:260: 
/var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.o] Error 1

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2025266/+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 2025266] Re: nvidia-dkms-* FTBS with linux 6.4

[Paolo Pisati]

** Also affects: nvidia-graphics-drivers-470 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  nvidia-dkms-* FTBS with linux 6.4

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New
Status in nvidia-graphics-drivers-470 source package in Mantic:
  New

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c: In function 
‘nv_drm_update_drm_driver_features’:
  /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c:769:18: error: 
‘struct drm_driver’ has no member named ‘dumb_destroy’
769 | nv_drm_driver.dumb_destroy = nv_drm_dumb_destroy;
|  ^
  make[2]: *** [scripts/Makefile.build:260: 
/var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.o] Error 1

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2025266/+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 2025266] Re: nvidia-dkms-* FTBS with linux 6.4

[Paolo Pisati]

** Patch added: "nvidia-graphics-drivers-390_390.157-0ubuntu7.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2025266/+attachment/5682792/+files/nvidia-graphics-drivers-390_390.157-0ubuntu7.debdiff

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

Title:
  nvidia-dkms-* FTBS with linux 6.4

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c: In function 
‘nv_drm_update_drm_driver_features’:
  /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c:769:18: error: 
‘struct drm_driver’ has no member named ‘dumb_destroy’
769 | nv_drm_driver.dumb_destroy = nv_drm_dumb_destroy;
|  ^
  make[2]: *** [scripts/Makefile.build:260: 
/var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.o] Error 1

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2025266/+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 2025266] [NEW] nvidia-dkms-* FTBS with linux 6.4

[Paolo Pisati]

Public bug reported:

[Impact]

/var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c: In function 
‘nv_drm_update_drm_driver_features’:
/var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c:769:18: error: 
‘struct drm_driver’ has no member named ‘dumb_destroy’
  769 | nv_drm_driver.dumb_destroy = nv_drm_dumb_destroy;
  |  ^
make[2]: *** [scripts/Makefile.build:260: 
/var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.o] Error 1

[Fix]

Apply the attached patch.

[How to test]

Build the dkms package and install it.

[Regression potential]

This patch doesn't come from NVIDIA itself, so there's a regression
potential, though i can't state how severe that could be.

** Affects: nvidia-graphics-drivers-390 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: nvidia-graphics-drivers-390 (Ubuntu Mantic)
 Importance: Undecided
 Status: New

** Also affects: nvidia-graphics-drivers-390 (Ubuntu Mantic)
   Importance: Undecided
   Status: New

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

Title:
  nvidia-dkms-* FTBS with linux 6.4

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c: In function 
‘nv_drm_update_drm_driver_features’:
  /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c:769:18: error: 
‘struct drm_driver’ has no member named ‘dumb_destroy’
769 | nv_drm_driver.dumb_destroy = nv_drm_dumb_destroy;
|  ^
  make[2]: *** [scripts/Makefile.build:260: 
/var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.o] Error 1

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2025266/+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 2024469] [NEW] Mantic update: v6.3.6 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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

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

** Affects: linux (Ubuntu Mantic)
 Importance: Undecided
 Status: Confirmed


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

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

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

Title:
  Mantic update: v6.3.6 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Mantic:
  Confirmed

Bug description:
  
  SRU Justification

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024469/+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 2024470] [NEW] Mantic update: v6.3.7 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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

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

** Affects: linux (Ubuntu Mantic)
 Importance: Undecided
 Status: Confirmed


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

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

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

Title:
  Mantic update: v6.3.7 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Mantic:
  Confirmed

Bug description:
  
  SRU Justification

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024470/+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 2024471] [NEW] Mantic update: v6.3.8 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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

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

** Affects: linux (Ubuntu Mantic)
 Importance: Undecided
 Status: Confirmed


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

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

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

Title:
  Mantic update: v6.3.8 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Mantic:
  Confirmed

Bug description:
  
  SRU Justification

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024471/+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 2019979] Re: nvidia-dkms-* FTBS with linux 6.3

[Paolo Pisati]

** Patch added: "nvidia-graphics-drivers-515_515.105.01-0ubuntu3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019979/+attachment/5678457/+files/nvidia-graphics-drivers-515_515.105.01-0ubuntu3.debdiff

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
https://bugs.launchpad.net/bugs/2019979

Title:
  nvidia-dkms-* FTBS with linux 6.3

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-510 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function 
‘nvidia_mmap_helper’:
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment 
of read-only member ‘vm_flags’
474 | vma->vm_flags |= VM_IO;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:536:23: error: assignment 
of read-only member ‘vm_flags’
536 | vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:537:23: error: assignment 
of read-only member ‘vm_flags’
537 | vma->vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:543:23: error: assignment 
of read-only member ‘vm_flags’
543 | vma->vm_flags &= ~VM_WRITE;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:544:23: error: assignment 
of read-only member ‘vm_flags’
544 | vma->vm_flags &= ~VM_MAYWRITE;
|   ^~

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019979/+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 2022326] [NEW] Mantic update: v6.3.5 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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


Linux 6.3.5
Revert "arm64: dts: imx8mp: Drop simple-bus from fsl,imx8mp-media-blk-ctrl"
net: phy: mscc: add VSC8502 to MODULE_DEVICE_TABLE
net: ethernet: mtk_eth_soc: fix QoS on DSA MAC on non MTK_NETSYS_V2 SoCs
page_pool: fix inconsistency for page_pool_ring_[un]lock()
3c589_cs: Fix an error handling path in tc589_probe()
net/smc: Reset connection when trying to use SMCRv2 fails.
regulator: mt6359: add read check for PMIC MT6359
firmware: arm_ffa: Set reserved/MBZ fields to zero in the memory descriptors
arm64: dts: imx8mn-var-som: fix PHY detection bug by adding deassert delay
net/mlx5: Devcom, serialize devcom registration
net/mlx5: Devcom, fix error flow in mlx5_devcom_register_device
net/mlx5: Collect command failures data only for known commands
net/mlx5: Fix error message when failing to allocate device memory
net/mlx5: DR, Check force-loopback RC QP capability independently from RoCE
net/mlx5: Handle pairing of E-switch via uplink un/load APIs
net/mlx5: DR, Fix crc32 calculation to work on big-endian (BE) CPUs
net/mlx5e: do as little as possible in napi poll when budget is 0
net/mlx5e: Use correct encap attribute during invalidation
net/mlx5e: Fix deadlock in tc route query code
net/mlx5e: Fix SQ wake logic in ptp napi_poll context
platform/mellanox: mlxbf-pmc: fix sscanf() error checking
forcedeth: Fix an error handling path in nv_probe()
sctp: fix an issue that plpmtu can never go to complete state
cxl: Move cxl_await_media_ready() to before capacity info retrieval
cxl: Wait Memory_Info_Valid before access memory related info
ASoC: Intel: avs: Access path components under lock
ASoC: Intel: avs: Fix declaration of enum avs_channel_config
ASoC: Intel: Skylake: Fix declaration of enum skl_ch_cfg
x86/show_trace_log_lvl: Ensure stack pointer is aligned, again
xen/pvcalls-back: fix double frees with pvcalls_new_active_socket()
x86/pci/xen: populate MSI sysfs entries
ARM: dts: imx6qdl-mba6: Add missing pvcie-supply regulator
coresight: Fix signedness bug in tmc_etr_buf_insert_barrier_packet()
platform/x86: ISST: Remove 8 socket limit
regulator: pca9450: Fix BUCK2 enable_mask
fs: fix undefined behavior in bit shift for SB_NOUSER
firmware: arm_ffa: Fix FFA device names for logical partitions
firmware: arm_ffa: Check if ffa_driver remove is present before executing
optee: fix uninited async notif value
power: supply: sbs-charger: Fix INHIBITED bit for Status reg
power: supply: bq24190: Call power_supply_changed() after updating input current
power: supply: bq25890: Call power_supply_changed() after updating input 
current or voltage
power: supply: bq27xxx: After charger plug in/out wait 0.5s for things to 
stabilize
power: supply: bq27xxx: Ensure power_supply_changed() is called on current sign 
changes
power: supply: bq27xxx: Move bq27xxx_battery_update() down
power: supply: bq27xxx: Add cache parameter to 
bq27xxx_battery_current_and_status()
power: supply: bq27xxx: Fix poll_interval handling and races on remove
power: supply: bq27xxx: Fix I2C IRQ race on remove
power: supply: bq27xxx: Fix bq27xxx_battery_update() race condition
power: supply: mt6360: add a check of devm_work_autocancel in 
mt6360_charger_probe
power: supply: leds: Fix blink to LED on transition
cifs: mapchars mount option ignored
ipv6: Fix out-of-bounds access in ipv6_find_tlv()
lan966x: Fix unloading/loading of the driver
bpf: fix a memory leak in the LRU and LRU_PERCPU hash maps
bpf: Fix mask generation for 32-bit narrow loads of 64-bit fields
octeontx2-pf: Fix TSOv6 offload
selftests: fib_tests: mute cleanup error message
drm: fix drmm_mutex_init()
net: fix skb leak in __skb_tstamp_tx()
ASoC: lpass: Fix for KASAN use_after_free out of bounds
media: radio-shark: Add endpoint checks
USB: sisusbvga: Add endpoint checks
USB: core: Add routines for endpoint checks in old drivers
udplite: Fix NULL pointer dereference in __sk_mem_raise_allocated().
net: fix stack overflow when LRO is disabled for virtual interfaces
fbdev: udlfb: Fix endpoint check
debugobjects: Don't wake up kswapd from fill_pool()
irqchip/mips-gic: Use raw spinlock for gic_lock
irqchip/mips-gic: Don't touch vl_map if a local interrupt is not routable
x86/topology: Fix erroneous smp_num_siblings on Intel Hybrid platforms
perf/x86/uncore: Correct the number of CHAs on SPR
drm/amd/amdgpu: limit one queue per gang
binder: fix UAF of alloc->vma in race with munmap()
binder: fix UAF caused by faulty buffer cleanup
binder: add 

[Kernel-packages] [Bug 2019979] Re: nvidia-dkms-* FTBS with linux 6.3

[Paolo Pisati]

** Patch added: "nvidia-graphics-drivers-450-server_450.236.01-0ubuntu3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019979/+attachment/5677154/+files/nvidia-graphics-drivers-450-server_450.236.01-0ubuntu3.debdiff

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

Title:
  nvidia-dkms-* FTBS with linux 6.3

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Mantic:
  New
Status in nvidia-graphics-drivers-470 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-510 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function 
‘nvidia_mmap_helper’:
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment 
of read-only member ‘vm_flags’
474 | vma->vm_flags |= VM_IO;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:536:23: error: assignment 
of read-only member ‘vm_flags’
536 | vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:537:23: error: assignment 
of read-only member ‘vm_flags’
537 | vma->vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:543:23: error: assignment 
of read-only member ‘vm_flags’
543 | vma->vm_flags &= ~VM_WRITE;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:544:23: error: assignment 
of read-only member ‘vm_flags’
544 | vma->vm_flags &= ~VM_MAYWRITE;
|   ^~

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019979/+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 2020780] [NEW] Lunar update: v6.3.2 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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

** Affects: linux-raspi (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: linux-raspi (Ubuntu Lunar)
 Importance: Undecided
 Status: New


** Tags: kernel-stable-tracking-bug

** Changed in: linux-raspi (Ubuntu)
   Status: New => Confirmed

** Tags added: kernel-stable-tracking-bug

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

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

Title:
  Lunar update: v6.3.2 upstream stable release

Status in linux-raspi package in Ubuntu:
  Confirmed
Status in linux-raspi source package in Lunar:
  New

Bug description:
  
  SRU Justification

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2020780/+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 2020779] [NEW] Lunar update: v6.3.1 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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

** Affects: linux-raspi (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: linux-raspi (Ubuntu Lunar)
 Importance: Undecided
 Status: New


** Tags: kernel-stable-tracking-bug

** Changed in: linux-raspi (Ubuntu)
   Status: New => Confirmed

** Tags added: kernel-stable-tracking-bug

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

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

Title:
  Lunar update: v6.3.1 upstream stable release

Status in linux-raspi package in Ubuntu:
  Confirmed
Status in linux-raspi source package in Lunar:
  New

Bug description:
  
  SRU Justification

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2020779/+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 2020781] [NEW] Lunar update: v6.3.3 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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

** Affects: linux-raspi (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: linux-raspi (Ubuntu Lunar)
 Importance: Undecided
 Status: New


** Tags: kernel-stable-tracking-bug

** Changed in: linux-raspi (Ubuntu)
   Status: New => Confirmed

** Tags added: kernel-stable-tracking-bug

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

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

Title:
  Lunar update: v6.3.3 upstream stable release

Status in linux-raspi package in Ubuntu:
  Confirmed
Status in linux-raspi source package in Lunar:
  New

Bug description:
  
  SRU Justification

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2020781/+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 2020783] [NEW] Lunar update: v6.3.4 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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

** Affects: linux-raspi (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: linux-raspi (Ubuntu Lunar)
 Importance: Undecided
 Status: New


** Tags: kernel-stable-tracking-bug

** Changed in: linux-raspi (Ubuntu)
   Status: New => Confirmed

** Tags added: kernel-stable-tracking-bug

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

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

Title:
  Lunar update: v6.3.4 upstream stable release

Status in linux-raspi package in Ubuntu:
  Confirmed
Status in linux-raspi source package in Lunar:
  New

Bug description:
  
  SRU Justification

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2020783/+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 2019979] Re: nvidia-dkms-* FTBS with linux 6.3

[Paolo Pisati]

** Patch added: "nvidia-graphics-drivers-470-server_470.182.03-0ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470-server/+bug/2019979/+attachment/5674711/+files/nvidia-graphics-drivers-470-server_470.182.03-0ubuntu2.debdiff

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

Title:
  nvidia-dkms-* FTBS with linux 6.3

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Mantic:
  New
Status in nvidia-graphics-drivers-470 source package in Mantic:
  New
Status in nvidia-graphics-drivers-470-server source package in Mantic:
  New
Status in nvidia-graphics-drivers-510 source package in Mantic:
  New
Status in nvidia-graphics-drivers-515 source package in Mantic:
  New
Status in nvidia-graphics-drivers-515-server source package in Mantic:
  New

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function 
‘nvidia_mmap_helper’:
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment 
of read-only member ‘vm_flags’
474 | vma->vm_flags |= VM_IO;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:536:23: error: assignment 
of read-only member ‘vm_flags’
536 | vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:537:23: error: assignment 
of read-only member ‘vm_flags’
537 | vma->vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:543:23: error: assignment 
of read-only member ‘vm_flags’
543 | vma->vm_flags &= ~VM_WRITE;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:544:23: error: assignment 
of read-only member ‘vm_flags’
544 | vma->vm_flags &= ~VM_MAYWRITE;
|   ^~

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019979/+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 2019979] Re: nvidia-dkms-* FTBS with linux 6.3

[Paolo Pisati]

** Patch added: "nvidia-graphics-drivers-450-server_450.236.01-0ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470-server/+bug/2019979/+attachment/5674704/+files/nvidia-graphics-drivers-450-server_450.236.01-0ubuntu2.debdiff

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

Title:
  nvidia-dkms-* FTBS with linux 6.3

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Mantic:
  New
Status in nvidia-graphics-drivers-470 source package in Mantic:
  New
Status in nvidia-graphics-drivers-470-server source package in Mantic:
  New
Status in nvidia-graphics-drivers-510 source package in Mantic:
  New
Status in nvidia-graphics-drivers-515 source package in Mantic:
  New
Status in nvidia-graphics-drivers-515-server source package in Mantic:
  New

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function 
‘nvidia_mmap_helper’:
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment 
of read-only member ‘vm_flags’
474 | vma->vm_flags |= VM_IO;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:536:23: error: assignment 
of read-only member ‘vm_flags’
536 | vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:537:23: error: assignment 
of read-only member ‘vm_flags’
537 | vma->vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:543:23: error: assignment 
of read-only member ‘vm_flags’
543 | vma->vm_flags &= ~VM_WRITE;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:544:23: error: assignment 
of read-only member ‘vm_flags’
544 | vma->vm_flags &= ~VM_MAYWRITE;
|   ^~

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019979/+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 2019979] Re: nvidia-dkms-390|470|510|515|515-server FTBS with linux 6.3

[Paolo Pisati]

** Also affects: nvidia-graphics-drivers-450-server (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-470-server (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- nvidia-dkms-390|470|510|515|515-server FTBS with linux 6.3
+ nvidia-dkms-* FTBS with linux 6.3

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

Title:
  nvidia-dkms-* FTBS with linux 6.3

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Mantic:
  New
Status in nvidia-graphics-drivers-470 source package in Mantic:
  New
Status in nvidia-graphics-drivers-470-server source package in Mantic:
  New
Status in nvidia-graphics-drivers-510 source package in Mantic:
  New
Status in nvidia-graphics-drivers-515 source package in Mantic:
  New
Status in nvidia-graphics-drivers-515-server source package in Mantic:
  New

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function 
‘nvidia_mmap_helper’:
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment 
of read-only member ‘vm_flags’
474 | vma->vm_flags |= VM_IO;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:536:23: error: assignment 
of read-only member ‘vm_flags’
536 | vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:537:23: error: assignment 
of read-only member ‘vm_flags’
537 | vma->vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:543:23: error: assignment 
of read-only member ‘vm_flags’
543 | vma->vm_flags &= ~VM_WRITE;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:544:23: error: assignment 
of read-only member ‘vm_flags’
544 | vma->vm_flags &= ~VM_MAYWRITE;
|   ^~

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019979/+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 2019979] Re: nvidia-dkms-390|470|510|515|515-server FTBS with linux 6.3

[Paolo Pisati]

** Summary changed:

- nvidia-dkms-390|470|510|515 FTBS with linux 6.3
+ nvidia-dkms-390|470|510|515|515-server FTBS with linux 6.3

** Also affects: nvidia-graphics-drivers-515-server (Ubuntu)
   Importance: Undecided
   Status: New

** Patch added: "nvidia-graphics-drivers-515-server_515.105.01-0ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-515-server/+bug/2019979/+attachment/5674127/+files/nvidia-graphics-drivers-515-server_515.105.01-0ubuntu2.debdiff

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

Title:
  nvidia-dkms-390|470|510|515|515-server FTBS with linux 6.3

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Mantic:
  New
Status in nvidia-graphics-drivers-510 source package in Mantic:
  New
Status in nvidia-graphics-drivers-515 source package in Mantic:
  New
Status in nvidia-graphics-drivers-515-server source package in Mantic:
  New

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function 
‘nvidia_mmap_helper’:
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment 
of read-only member ‘vm_flags’
474 | vma->vm_flags |= VM_IO;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:536:23: error: assignment 
of read-only member ‘vm_flags’
536 | vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:537:23: error: assignment 
of read-only member ‘vm_flags’
537 | vma->vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:543:23: error: assignment 
of read-only member ‘vm_flags’
543 | vma->vm_flags &= ~VM_WRITE;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:544:23: error: assignment 
of read-only member ‘vm_flags’
544 | vma->vm_flags &= ~VM_MAYWRITE;
|   ^~

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019979/+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 2019979] Re: nvidia-dkms-390|470|510|515 FTBS with linux 6.3

[Paolo Pisati]

** Patch added: "nvidia-graphics-drivers-515_515.105.01-0ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/2019979/+attachment/5673905/+files/nvidia-graphics-drivers-515_515.105.01-0ubuntu2.debdiff

** Also affects: nvidia-graphics-drivers-515 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  nvidia-dkms-390|470|510|515 FTBS with linux 6.3

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Mantic:
  New
Status in nvidia-graphics-drivers-510 source package in Mantic:
  New
Status in nvidia-graphics-drivers-515 source package in Mantic:
  New

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function 
‘nvidia_mmap_helper’:
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment 
of read-only member ‘vm_flags’
474 | vma->vm_flags |= VM_IO;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:536:23: error: assignment 
of read-only member ‘vm_flags’
536 | vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:537:23: error: assignment 
of read-only member ‘vm_flags’
537 | vma->vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:543:23: error: assignment 
of read-only member ‘vm_flags’
543 | vma->vm_flags &= ~VM_WRITE;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:544:23: error: assignment 
of read-only member ‘vm_flags’
544 | vma->vm_flags &= ~VM_MAYWRITE;
|   ^~

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019979/+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 2019979] Re: nvidia-dkms-390|470|510|515 FTBS with linux 6.3

[Paolo Pisati]

** Summary changed:

- nvidia-dkms-390|470|510 FTBS with linux 6.3
+ nvidia-dkms-390|470|510|515 FTBS with linux 6.3

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

Title:
  nvidia-dkms-390|470|510|515 FTBS with linux 6.3

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New
Status in nvidia-graphics-drivers-470 source package in Mantic:
  New
Status in nvidia-graphics-drivers-510 source package in Mantic:
  New

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function 
‘nvidia_mmap_helper’:
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment 
of read-only member ‘vm_flags’
474 | vma->vm_flags |= VM_IO;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:536:23: error: assignment 
of read-only member ‘vm_flags’
536 | vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:537:23: error: assignment 
of read-only member ‘vm_flags’
537 | vma->vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:543:23: error: assignment 
of read-only member ‘vm_flags’
543 | vma->vm_flags &= ~VM_WRITE;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:544:23: error: assignment 
of read-only member ‘vm_flags’
544 | vma->vm_flags &= ~VM_MAYWRITE;
|   ^~

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019979/+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 2019979] Re: nvidia-dkms-390|470|510 FTBS with linux 6.3

[Paolo Pisati]

** Patch added: "nvidia-graphics-drivers-510_510.108.03-0ubuntu3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/2019979/+attachment/5673845/+files/nvidia-graphics-drivers-510_510.108.03-0ubuntu3.debdiff

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

Title:
  nvidia-dkms-390|470|510 FTBS with linux 6.3

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New
Status in nvidia-graphics-drivers-470 source package in Mantic:
  New
Status in nvidia-graphics-drivers-510 source package in Mantic:
  New

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function 
‘nvidia_mmap_helper’:
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment 
of read-only member ‘vm_flags’
474 | vma->vm_flags |= VM_IO;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:536:23: error: assignment 
of read-only member ‘vm_flags’
536 | vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:537:23: error: assignment 
of read-only member ‘vm_flags’
537 | vma->vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:543:23: error: assignment 
of read-only member ‘vm_flags’
543 | vma->vm_flags &= ~VM_WRITE;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:544:23: error: assignment 
of read-only member ‘vm_flags’
544 | vma->vm_flags &= ~VM_MAYWRITE;
|   ^~

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019979/+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 2019979] Re: nvidia-dkms-390|470 FTBS with linux 6.3

[Paolo Pisati]

** Also affects: nvidia-graphics-drivers-510 (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- nvidia-dkms-390|470 FTBS with linux 6.3
+ nvidia-dkms-390|470|510 FTBS with linux 6.3

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

Title:
  nvidia-dkms-390|470|510 FTBS with linux 6.3

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New
Status in nvidia-graphics-drivers-470 source package in Mantic:
  New
Status in nvidia-graphics-drivers-510 source package in Mantic:
  New

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function 
‘nvidia_mmap_helper’:
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment 
of read-only member ‘vm_flags’
474 | vma->vm_flags |= VM_IO;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:536:23: error: assignment 
of read-only member ‘vm_flags’
536 | vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:537:23: error: assignment 
of read-only member ‘vm_flags’
537 | vma->vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:543:23: error: assignment 
of read-only member ‘vm_flags’
543 | vma->vm_flags &= ~VM_WRITE;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:544:23: error: assignment 
of read-only member ‘vm_flags’
544 | vma->vm_flags &= ~VM_MAYWRITE;
|   ^~

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019979/+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 2019979] Re: nvidia-dkms-390|470 FTBS with linux 6.3

[Paolo Pisati]

** Patch added: "nvidia-graphics-drivers-470_470.182.03-0ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2019979/+attachment/5673813/+files/nvidia-graphics-drivers-470_470.182.03-0ubuntu2.debdiff

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

Title:
  nvidia-dkms-390|470 FTBS with linux 6.3

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New
Status in nvidia-graphics-drivers-470 source package in Mantic:
  New

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function 
‘nvidia_mmap_helper’:
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment 
of read-only member ‘vm_flags’
474 | vma->vm_flags |= VM_IO;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:536:23: error: assignment 
of read-only member ‘vm_flags’
536 | vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:537:23: error: assignment 
of read-only member ‘vm_flags’
537 | vma->vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:543:23: error: assignment 
of read-only member ‘vm_flags’
543 | vma->vm_flags &= ~VM_WRITE;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:544:23: error: assignment 
of read-only member ‘vm_flags’
544 | vma->vm_flags &= ~VM_MAYWRITE;
|   ^~

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019979/+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 2019979] Re: nvidia-dkms-390|470 FTBS with linux 6.3

[Paolo Pisati]

** Summary changed:

- nvidia-dkms-390 FTBS with linux 6.3
+ nvidia-dkms-390|470 FTBS with linux 6.3

** Also affects: nvidia-graphics-drivers-470 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  nvidia-dkms-390|470 FTBS with linux 6.3

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New
Status in nvidia-graphics-drivers-470 source package in Mantic:
  New

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function 
‘nvidia_mmap_helper’:
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment 
of read-only member ‘vm_flags’
474 | vma->vm_flags |= VM_IO;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:536:23: error: assignment 
of read-only member ‘vm_flags’
536 | vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:537:23: error: assignment 
of read-only member ‘vm_flags’
537 | vma->vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:543:23: error: assignment 
of read-only member ‘vm_flags’
543 | vma->vm_flags &= ~VM_WRITE;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:544:23: error: assignment 
of read-only member ‘vm_flags’
544 | vma->vm_flags &= ~VM_MAYWRITE;
|   ^~

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019979/+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 2019979] Re: nvidia-dkms-390 FTBS with linux 6.3

[Paolo Pisati]

** Patch added: "nvidia-graphics-drivers-390_390.157-0ubuntu6.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019979/+attachment/5673790/+files/nvidia-graphics-drivers-390_390.157-0ubuntu6.debdiff

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

Title:
  nvidia-dkms-390 FTBS with linux 6.3

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function 
‘nvidia_mmap_helper’:
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment 
of read-only member ‘vm_flags’
474 | vma->vm_flags |= VM_IO;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:536:23: error: assignment 
of read-only member ‘vm_flags’
536 | vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:537:23: error: assignment 
of read-only member ‘vm_flags’
537 | vma->vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:543:23: error: assignment 
of read-only member ‘vm_flags’
543 | vma->vm_flags &= ~VM_WRITE;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:544:23: error: assignment 
of read-only member ‘vm_flags’
544 | vma->vm_flags &= ~VM_MAYWRITE;
|   ^~

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019979/+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 2019979] [NEW] nvidia-dkms-390 FTBS with linux 6.3

[Paolo Pisati]

Public bug reported:

[Impact]

/var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function 
‘nvidia_mmap_helper’:
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment 
of read-only member ‘vm_flags’
  474 | vma->vm_flags |= VM_IO;
  |   ^~
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:536:23: error: assignment 
of read-only member ‘vm_flags’
  536 | vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED);
  |   ^~
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:537:23: error: assignment 
of read-only member ‘vm_flags’
  537 | vma->vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP);
  |   ^~
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:543:23: error: assignment 
of read-only member ‘vm_flags’
  543 | vma->vm_flags &= ~VM_WRITE;
  |   ^~
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:544:23: error: assignment 
of read-only member ‘vm_flags’
  544 | vma->vm_flags &= ~VM_MAYWRITE;
  |   ^~

[Fix]

Apply the attached patch.

[How to test]

Build the dkms package and install it.

[Regression potential]

This patch doesn't come from NVIDIA itself, so there's a regression
potential, though i can't state how severe that could be.

** Affects: nvidia-graphics-drivers-390 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: nvidia-graphics-drivers-390 (Ubuntu Mantic)
 Importance: Undecided
 Status: New

** Also affects: nvidia-graphics-drivers-390 (Ubuntu Mantic)
   Importance: Undecided
   Status: New

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

Title:
  nvidia-dkms-390 FTBS with linux 6.3

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function 
‘nvidia_mmap_helper’:
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment 
of read-only member ‘vm_flags’
474 | vma->vm_flags |= VM_IO;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:536:23: error: assignment 
of read-only member ‘vm_flags’
536 | vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:537:23: error: assignment 
of read-only member ‘vm_flags’
537 | vma->vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:543:23: error: assignment 
of read-only member ‘vm_flags’
543 | vma->vm_flags &= ~VM_WRITE;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:544:23: error: assignment 
of read-only member ‘vm_flags’
544 | vma->vm_flags &= ~VM_MAYWRITE;
|   ^~

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019979/+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 2017685] Re: package linux-generic 6.2.0.20.20 failed to install/upgrade: problemas de dependência - deixando desconfigurado

[Paolo Pisati]

Temporary workaround:

$ sudo apt-get autoremove

will fix your installation issue.

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

Title:
  package linux-generic 6.2.0.20.20 failed to install/upgrade: problemas
  de dependência - deixando desconfigurado

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  o problema persiste a algum tempo

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-generic 6.2.0.20.20
  ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nayara 1645 F wireplumber
   /dev/snd/seq:nayara 1642 F pipewire
  CasperMD5CheckResult: unknown
  Date: Tue Apr 25 13:40:25 2023
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-kbl+X28
  ErrorMessage: problemas de dependência - deixando desconfigurado
  InstallationDate: Installed on 2022-05-25 (335 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3481
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic 
root=UUID=33934e39-9f9a-4ddc-a384-df26b027f0ba ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-generic 6.2.0.20.20 failed to install/upgrade: problemas 
de dependência - deixando desconfigurado
  UpgradeStatus: Upgraded to lunar on 2023-04-25 (0 days ago)
  dmi.bios.date: 06/04/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.0
  dmi.board.name: 0YK2K8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.0:bd06/04/2020:br1.9:svnDellInc.:pnInspiron3481:pvr:rvnDellInc.:rn0YK2K8:rvrA00:cvnDellInc.:ct10:cvr:sku08CE:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3481
  dmi.product.sku: 08CE
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017685/+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 2017219] [NEW] Lunar update: v6.2.12 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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

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

** Affects: linux (Ubuntu Lunar)
 Importance: Undecided
 Status: Confirmed


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Lunar)
   Importance: Undecided
   Status: Confirmed

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

Title:
  Lunar update: v6.2.12 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Lunar:
  Confirmed

Bug description:
  
  SRU Justification

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017219/+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 2016879] [NEW] Lunar update: v6.2.11 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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


Linux 6.2.11
mm: enable maple tree RCU mode by default.
maple_tree: add RCU lock checking to rcu callback functions
maple_tree: add smp_rmb() to dead node detection
maple_tree: remove extra smp_wmb() from mas_dead_leaves()
maple_tree: fix freeing of nodes in rcu mode
maple_tree: detect dead nodes in mas_start()
maple_tree: refine ma_state init from mas_start()
maple_tree: be more cautious about dead nodes
maple_tree: fix mas_prev() and mas_find() state handling
maple_tree: fix handle of invalidated state in mas_wr_store_setup()
maple_tree: reduce user error potential
maple_tree: fix potential rcu issue
maple_tree: remove GFP_ZERO from kmem_cache_alloc() and kmem_cache_alloc_bulk()
mm: take a page reference when removing device exclusive entries
drm/bridge: lt9611: Fix PLL being unable to lock
drm/amdgpu: skip psp suspend for IMU enabled ASICs mode2 reset
drm/amdgpu: for S0ix, skip SDMA 5.x+ suspend/resume
drm/amd/display: Clear MST topology if it fails to resume
maple_tree: fix a potential concurrency bug in RCU mode
maple_tree: fix get wrong data_end in mtree_lookup_walk()
mm/hugetlb: fix uffd wr-protection for CoW optimization path
mm/swap: fix swap_info_struct race between swapoff and get_swap_pages()
ring-buffer: Fix race while reader and writer are on the same page
drm/i915: fix race condition UAF in i915_perf_add_config_ioctl
drm/i915: Fix context runtime accounting
drm/nouveau/disp: Support more modes by checking with lower bpc
drm/panfrost: Fix the panfrost_mmu_map_fault_addr() error path
ublk: read any SQE values upfront
wifi: mt76: ignore key disable commands
wifi: mt76: mt7921: fix fw used for offload check for mt7922
mm: vmalloc: avoid warn_alloc noise caused by fatal signal
zsmalloc: document freeable stats
tracing/synthetic: Make lastcmd_mutex static
perf/core: Fix the same task check in perf_event_set_output
perf: Optimize perf_pmu_migrate_context()
block: don't set GD_NEED_PART_SCAN if scan partition failed
block: ublk: make sure that block size is set correctly
cifs: sanitize paths in cifs_update_super_prepath.
nvme: fix discard support without oncs
scsi: iscsi_tcp: Check that sock is valid before iscsi_set_param()
scsi: qla2xxx: Fix memory leak in qla2x00_probe_one()
io_uring: fix memory leak when removing provided buffers
io_uring: fix return value when removing provided buffers
iio: adc: ad7791: fix IRQ flags
ASoC: SOF: avoid a NULL dereference with unsupported widgets
ASoC: hdac_hdmi: use set_stream() instead of set_tdm_slots()
iommufd: Do not corrupt the pfn list when doing batch carry
iommufd: Fix unpinning of pages when an access is present
iommufd: Check for uptr overflow
tracing: Free error logs of tracing instances
tracing/osnoise: Fix notify new tracing_max_latency
tracing/timerlat: Notify new max thread latency
tracing/synthetic: Fix races on freeing last_cmd
net: stmmac: Add queue reset into stmmac_xdp_open() function
ACPI: video: Add acpi_backlight=video quirk for Lenovo ThinkPad W530
ACPI: video: Add acpi_backlight=video quirk for Apple iMac14,1 and iMac14,2
ACPI: video: Make acpi_backlight=video work independent from GPU driver
ACPI: video: Add auto_detect arg to __acpi_video_get_backlight_type()
can: isotp: isotp_recvmsg(): use sock_recv_cmsgs() to get SOCK_RXQ_OVFL infos
can: isotp: isotp_ops: fix poll() to not report false EPOLLOUT events
can: isotp: fix race between isotp_sendsmg() and isotp_release()
can: j1939: j1939_tp_tx_dat_new(): fix out-of-bounds memory access
fs: drop peer group ids under namespace lock
ftrace: Fix issue that 'direct->addr' not restored in modify_ftrace_direct()
ftrace: Mark get_lock_parent_ip() __always_inline
blk-mq: directly poll requests
counter: 104-quad-8: Fix Synapse action reported for Index signals
counter: 104-quad-8: Fix race condition between FLAG and CNTR reads
coresight-etm4: Fix for() loop drvdata->nr_addr_cmp range bug
coresight: etm4x: Do not access TRCIDR1 for identification
mm: kfence: fix handling discontiguous page
mm: kfence: fix PG_slab and memcg_data clearing
KVM: SVM: Flush Hyper-V TLB when required
KVM: nVMX: Do not report error code when synthesizing VM-Exit from Real Mode
KVM: x86: Clear "has_error_code", not "error_code", for RM exception injection
x86/ACPI/boot: Use FADT version to check support for online capable
x86/acpi/boot: Correct acpi_is_processor_usable() check
ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook
ALSA: hda/realtek: Add quirk for Clevo 

[Kernel-packages] [Bug 2016876] [NEW] Lunar update: v6.2.8 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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


Linux 6.2.8
powerpc/64: Replace -mcpu=e500mc64 by -mcpu=e5500
powerpc: Disable CPU unknown by CLANG when CC_IS_CLANG
perf: Fix check before add_event_to_groups() in perf_group_detach()
virt/coco/sev-guest: Add throttling awareness
virt/coco/sev-guest: Convert the sw_exit_info_2 checking to a switch-case
virt/coco/sev-guest: Do some code style cleanups
virt/coco/sev-guest: Carve out the request issuing logic into a helper
virt/coco/sev-guest: Remove the disable_vmpck label in handle_guest_request()
virt/coco/sev-guest: Simplify extended guest request handling
virt/coco/sev-guest: Check SEV_SNP attribute at probe time
powerpc: Pass correct CPU reference to assembler
x86/resctrl: Clear staged_config[] before and after it is used
x86/mm: Fix use of uninitialized buffer in sme_enable()
x86/mce: Make sure logged MCEs are processed after sysfs update
ASoC: qcom: q6prm: fix incorrect clk_root passed to ADSP
ASoC: Intel: soc-acpi: fix copy-paste issue in topology names
cpuidle: psci: Iterate backwards over list in psci_pd_remove()
io_uring/msg_ring: let target know allocated index
RISC-V: mm: Support huge page in vmalloc_fault()
fbdev: Fix incorrect page mapping clearance at fb_deferred_io_release()
net: phy: nxp-c45-tja11xx: fix MII_BASIC_CONFIG_REV bit
ACPI: PPTT: Fix to avoid sleep in the atomic context when PPTT is absent
trace/hwlat: Do not start per-cpu thread if it is already running
trace/hwlat: Do not wipe the contents of per-cpu thread data
fbdev: stifb: Provide valid pixelclock and add fb_check_var() checks
mmc: sdhci_am654: lower power-on failed message severity
powerpc/boot: Don't always pass -mcpu=powerpc when building 32-bit uImage
powerpc/64: Set default CPU in Kconfig
mm: teach mincore_hugetlb about pte markers
mm/userfaultfd: propagate uffd-wp bit when PTE-mapping the huge zeropage
vp_vdpa: fix the crash in hot unplug with vp_vdpa
ice: avoid bonding causing auxiliary plug/unplug under RTNL lock
nvme-pci: add NVME_QUIRK_BOGUS_NID for Netac NV3000
ocfs2: fix data corruption after failed write
ftrace: Fix invalid address access in lookup_rec() when index is 0
mptcp: fix lockdep false positive in mptcp_pm_nl_create_listen_socket()
mptcp: avoid setting TCP_CLOSE state twice
mptcp: add ro_after_init for tcp{,v6}_prot_override
mptcp: fix UaF in listener shutdown
mptcp: use the workqueue to destroy unaccepted sockets
mptcp: refactor passive socket initialization
mptcp: fix possible deadlock in subflow_error_report
drm/amd/display: Write to correct dirty_rect
drm/amd/display: disconnect MPCC only on OTG change
drm/amd/display: Do not set DRR on pipe Commit
drm/amd/pm: bump SMU 13.0.4 driver_if header version
drm/amdgpu/vcn: Disable indirect SRAM on Vangogh broken BIOSes
drm/amd/pm: Fix sienna cichlid incorrect OD volage after resume
drm/amdgpu: Don't resume IOMMU after incomplete init
drm/i915/dg2: Add HDMI pixel clock frequencies 267.30 and 319.89 MHz
drm/i915/active: Fix misuse of non-idle barriers as fence trackers
drm/sun4i: fix missing component unbind on bind errors
drm/shmem-helper: Remove another errant put in error path
drm/edid: fix info leak when failing to get panel id
riscv: asid: Fixup stale TLB entry cause application crash
Revert "riscv: mm: notify remote harts about mmu cache updates"
ALSA: hda/realtek: fix speaker, mute/micmute LEDs not work on a HP platform
ALSA: hda/realtek: Fix the speaker output on Samsung Galaxy Book2 Pro
ALSA: hda: intel-dsp-config: add MTL PCI id
KVM: nVMX: add missing consistency checks for CR0 and CR4
KVM: SVM: Modify AVIC GATag to support max number of 512 vCPUs
KVM: SVM: Fix a benign off-by-one bug in AVIC physical table mask
cifs: use DFS root session instead of tcon ses
cifs: return DFS root session id in DebugData
cifs: fix use-after-free bug in refresh_cache_worker()
cifs: set DFS root session in cifs_get_smb_ses()
cifs: Fix smb2_set_path_size()
tracing: Make tracepoint lockdep check actually test something
tracing: Check field value in hist_field_name()
tracing: Do not let histogram values have some modifiers
tracing: Make splice_read available again
cifs: generate signkey for the channel that's reconnecting
md: select BLOCK_LEGACY_AUTOLOAD
interconnect: exynos: fix registration race
interconnect: exynos: fix node leak in probe PM QoS error path
interconnect: qcom: msm8974: fix registration race
interconnect: qcom: rpmh: fix registration race
interconnect: qcom: rpmh: fix probe child-node error handling

[Kernel-packages] [Bug 2016875] [NEW] Lunar update: v6.2.7 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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


Linux 6.2.7
UML: define RUNTIME_DISCARD_EXIT
RISC-V: fix taking the text_mutex twice during sifive errata patching
Revert "bpf, test_run: fix _frame misplacement for LIVE_FRAMES"
filelocks: use mount idmapping for setlease permission check
drm/amd/display: adjust MALL size available for DCN32 and DCN321
drm/amd/display: Allow subvp on vactive pipes that are 2560x1440@60
media: rc: gpio-ir-recv: add remove function
media: ov5640: Fix analogue gain control
scripts: handle BrokenPipeError for python scripts
PCI: Add SolidRun vendor ID
macintosh: windfarm: Use unsigned type for 1-bit bitfields
alpha: fix R_ALPHA_LITERAL reloc for large modules
powerpc/kcsan: Exclude udelay to prevent recursive instrumentation
powerpc/64: Move paca allocation to early_setup()
powerpc/64: Fix task_cpu in early boot when booting non-zero cpuid
powerpc/bpf/32: Only set a stack frame when necessary
powerpc: Remove __kernel_text_address() in show_instructions()
clk: renesas: rcar-gen3: Disable R-Car H3 ES1.*
powerpc/iommu: fix memory leak with using debugfs_lookup()
powerpc/64: Don't recurse irq replay
MIPS: Fix a compilation issue
tpm/eventlog: Don't abort tpm_read_log on faulty ACPI address
watch_queue: fix IOC_WATCH_QUEUE_SET_SIZE alloc error paths
drm/amdgpu/soc21: Add video cap query support for VCN_4_0_4
drm/amdgpu/soc21: don't expose AV1 if VCN0 is harvested
RISC-V: take text_mutex during alternative patching
ext4: Fix deadlock during directory rename
drm/amdgpu: fix return value check in kfd
RISC-V: Don't check text_mutex during stop_machine
riscv: Use READ_ONCE_NOCHECK in imprecise unwinding stack mode
erofs: Revert "erofs: fix kvcalloc() misuse with __GFP_NOFAIL"
af_unix: fix struct pid leaks in OOB support
net: dsa: mt7530: permit port 5 to work without port 6 on MT7621 SoC
SUNRPC: Fix a server shutdown leak
octeontx2-af: Unlock contexts in the queue context cache in case of fault 
detection
net/smc: fix fallback failed while sendmsg with fastopen
ethernet: ice: avoid gcc-9 integer overflow warning
ice: Fix DSCP PFC TLV creation
NFSD: Protect against filesystem freezing
block: fix wrong mode for blkdev_put() from disk_scan_partitions()
platform: x86: MLX_PLATFORM: select REGMAP instead of depending on it
platform: mellanox: select REGMAP instead of depending on it
platform/x86: dell-ddv: Fix temperature scaling
platform/x86: dell-ddv: Return error if buffer is empty
netfilter: conntrack: adopt safer max chain length
scsi: sd: Fix wrong zone_write_granularity value during revalidate
scsi: megaraid_sas: Update max supported LD IDs to 240
net: tls: fix device-offloaded sendpage straddling records
net: ethernet: mtk_eth_soc: fix RX data corruption issue
net: phy: smsc: fix link up detection in forced irq mode
btf: fix resolving BTF_KIND_VAR after ARRAY, STRUCT, UNION, PTR
bpf, test_run: fix _frame misplacement for LIVE_FRAMES
btrfs: fix extent map logging bit not cleared for split maps after dropping 
range
m68k: mm: Move initrd phys_to_virt handling after paging_init()
netfilter: tproxy: fix deadlock due to missing BH disable
netfilter: ctnetlink: revert to dumping mark regardless of event type
bnxt_en: Avoid order-5 memory allocation for TPA data
net: phylib: get rid of unnecessary locking
net: stmmac: add to set device wake up flag when stmmac init phy
drm/msm/dpu: clear DSPP reservations in rm release
drm/msm/disp/dpu: fix sc7280_pp base offset
drm/msm/dpu: fix clocks settings for msm8998 SSPP blocks
drm/msm/dpu: drop DPU_DIM_LAYER from MIXER_MSM8998_MASK
drm/msm/dpu: correct sm6115 scaler
drm/msm/dpu: correct sm8250 and sm8350 scaler
drm/msm/dpu: fix sm6115 and qcm2290 mixer width limits
drm/msm/dpu: fix len of sc7180 ctl blocks
bpf, sockmap: Fix an infinite loop error when len is 0 in 
tcp_bpf_recvmsg_parser()
nfp: fix esp-tx-csum-offload doesn't take effect
nfp: fix incorrectly set csum flag for nfd3 path
ice: copy last block omitted in ice_get_module_eeprom()
net: caif: Fix use-after-free in cfusbl_device_notify()
net: lan78xx: fix accessing the LAN7800's internal phy specific registers from 
the MAC driver
perf stat: Fix counting when initial delay configured
net: use indirect calls helpers for sk_exit_memory_pressure()
net: tls: fix possible race condition between do_tls_getsockopt_conf() and 
do_tls_setsockopt_conf()
netfilter: nft_quota: copy content when cloning expression
netfilter: nft_last: copy content when cloning expression
selftests: nft_nat: ensuring the 

[Kernel-packages] [Bug 2016877] [NEW] Lunar update: v6.2.9 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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


Linux 6.2.9
sched/fair: Sanitize vruntime of entity being migrated
sched/fair: sanitize vruntime of entity being placed
dm crypt: avoid accessing uninitialized tasklet
dm crypt: add cond_resched() to dmcrypt_write()
dm stats: check for and propagate alloc_percpu failure
i2c: xgene-slimpro: Fix out-of-bounds bug in xgene_slimpro_i2c_xfer()
bus: imx-weim: fix branch condition evaluates to a garbage value
mm/ksm: fix race with VMA iteration and mm_struct teardown
soc: qcom: llcc: Fix slice configuration values for SC8280XP
arm64: dts: qcom: sm8150: Fix the iommu mask used for PCIe controllers
arm64: dts: qcom: sc7280: Mark PCIe controller as cache coherent
arm64: dts: qcom: sc8280xp-x13s: mark s11b regulator as always-on
firmware: arm_scmi: Fix device node validation for mailbox transport
tee: amdtee: fix race condition in amdtee_open_session
riscv: Handle zicsr/zifencei issues between clang and binutils
riscv: mm: Fix incorrect ASID argument when flushing TLB
drm/amdgpu: reposition the gpu reset checking for reuse
drm/amdgpu: skip ASIC reset for APUs when go to S4
drm/i915: Preserve crtc_state->inherited during state clearing
drm/i915/active: Fix missing debug object activation
drm/amdgpu/nv: Apply ASPM quirk on Intel ADL + AMD Navi
drm/meson: fix missing component unbind on bind errors
drm/amd/display: fix wrong index used in dccg32_set_dpstreamclk
drm/bridge: lt8912b: return EPROBE_DEFER if bridge is not found
nilfs2: fix kernel-infoleak in nilfs_ioctl_wrap_copy()
wifi: mac80211: Serialize ieee80211_handle_wake_tx_queue()
wifi: mac80211: fix qos on mesh interfaces
ksmbd: return unsupported error on smb1 mount
ksmbd: return STATUS_NOT_SUPPORTED on unsupported smb2.0 dialect
ksmbd: don't terminate inactive sessions after a few seconds
ksmbd: set FILE_NAMED_STREAMS attribute in FS_ATTRIBUTE_INFORMATION
ksmbd: fix wrong signingkey creation when encryption is AES256
maple_tree: fix mas_skip_node() end slot detection
test_maple_tree: add more testing for mas_empty_area()
kcsan: avoid passing -g for test
Revert "kasan: drop skip_kasan_poison variable in free_pages_prepare"
io_uring/rsrc: fix null-ptr-deref in io_file_bitmap_get()
io_uring/net: avoid sending -ECONNABORTED on repeated connection requests
kfence: avoid passing -g for test
mm: kfence: fix using kfence_metadata without initialization in show_object()
usb: ucsi_acpi: Increase the command completion timeout
usb: ucsi: Fix NULL pointer deref in ucsi_connector_change()
usb: dwc3: gadget: Add 1ms delay after end transfer command without IOC
usb: chipidea: core: fix possible concurrent when switch role
usb: chipdea: core: fix return -EINVAL if request role is the same with current 
role
usb: cdnsp: changes PCI Device ID to fix conflict with CNDS3 driver
usb: cdnsp: Fixes issue with redundant Status Stage
usb: cdns3: Fix issue with using incorrect PCI device function
usb: typec: tcpm: fix warning when handle discover_identity message
usb: typec: tcpm: fix create duplicate source-capabilities file
dm thin: fix deadlock when swapping to thin device
igb: revert rtnl_lock() that causes deadlock
arm64: dts: imx8mm-nitrogen-r2: fix WM8960 clock name
lockd: set file_lock start and end when decoding nlm4 testargs
fsverity: Remove WQ_UNBOUND from fsverity read workqueue
fscrypt: destroy keyring after security_sb_delete()
arm64: efi: Set NX compat flag in PE/COFF header
efi/libstub: zboot: Mark zboot EFI application as NX compatible
mm/slab: Fix undefined init_cache_node_node() for NUMA and !SMP
efi: sysfb_efi: Fix DMI quirks not working for simpledrm
Bluetooth: Fix race condition in hci_cmd_sync_clear
btrfs: zoned: fix btrfs_can_activate_zone() to support DUP profile
usb: gadget: u_audio: don't let userspace block driver unbind
block/io_uring: pass in issue_flags for uring_cmd task_work handling
usb: dwc2: fix a devres leak in hw_enable upon suspend resume
usb: dwc2: drd: fix inconsistent mode if role-switch-default-mode="host"
usb: dwc2: fix a race, don't power off/on phy for dual-role mode
usb: misc: onboard-hub: add support for Microchip USB2517 USB 2.0 hub
scsi: core: Add BLIST_SKIP_VPD_PAGES for SKhynix H28U74301AMR
selftests/x86/amx: Add a ptrace test
x86/fpu/xstate: Prevent false-positive warning in __copy_xstate_uabi_buf()
x86/mm: Do not shuffle CPU entry areas without KASLR
cifs: fix dentry lookups in directory handle cache
cifs: print session id while listing open files
cifs: dump pending mids for all 

[Kernel-packages] [Bug 2016878] [NEW] Lunar update: v6.2.10 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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


Linux 6.2.10
Revert "cpuidle, intel_idle: Fix CPUIDLE_FLAG_IRQ_ENABLE *again*"
x86/PVH: avoid 32-bit build warning when obtaining VGA console info
hsr: ratelimit only when errors are printed
drm/amdkfd: Get prange->offset after svm_range_vram_node_new
libbpf: Fix btf_dump's packed struct determination
selftests/bpf: Add few corner cases to test padding handling of btf_dump
libbpf: Fix BTF-to-C converter's padding logic
usb: ucsi: Fix ucsi->connector race
KVM: arm64: Check for kvm_vma_mte_allowed in the critical section
KVM: arm64: Disable interrupts while walking userspace PTs
KVM: arm64: Retry fault if vma_lookup() results become invalid
KVM: arm64: PMU: Don't save PMCR_EL0.{C,P} for the vCPU
KVM: arm64: PMU: Fix GET_ONE_REG for vPMC regs to return the current value
drm/i915: Move CSC load back into .color_commit_arm() when PSR is enabled on 
skl/glk
drm/i915: Split icl_color_commit_noarm() from skl_color_commit_noarm()
drm/i915: Disable DC states for all commits
drm/i915/dpt: Treat the DPT BO as a framebuffer
drm/i915/gem: Flush lmem contents after construction
drm/amd/display: Take FEC Overhead into Timeslot Calculation
drm/amd/display: Add DSC Support for Synaptics Cascaded MST Hub
drm/amdgpu: allow more APUs to do mode2 reset when go to S4
drm/etnaviv: fix reference leak when mmaping imported buffer
s390: reintroduce expoline dependence to scripts
s390/uaccess: add missing earlyclobber annotations to __clear_user()
dt-bindings: mtd: jedec,spi-nor: Document CPOL/CPHA support
rcu: Fix rcu_torture_read ftrace event
xtensa: fix KASAN report for show_stack
ALSA: hda/realtek: Add quirk for Lenovo ZhaoYang CF4620Z
ALSA: hda/realtek: Add quirks for some Clevo laptops
ALSA: usb-audio: Fix regression on detection of Roland VS-100
ALSA: hda/conexant: Partial revert of a quirk for Lenovo
NFSv4: Fix hangs when recovering open state after a server reboot
powerpc/64s: Fix __pte_needs_flush() false positive warning
powerpc/pseries/vas: Ignore VAS update for DLPAR if copy/paste is not enabled
powerpc: Don't try to copy PPR for task with NULL pt_regs
thermal: intel: int340x: processor_thermal: Fix additional deadlock
platform/x86: ideapad-laptop: Stop sending KEY_TOUCHPAD_TOGGLE
pinctrl: at91-pio4: fix domain name assignment
pinctrl: amd: Disable and mask interrupts on resume
modpost: Fix processing of CRCs on 32-bit build machines
net: phy: dp83869: fix default value for tx-/rx-internal-delay
xen/netback: don't do grant copy across page boundary
can: j1939: prevent deadlock by moving j1939_sk_errqueue()
dm: fix __send_duplicate_bios() to always allow for splitting IO
zonefs: Always invalidate last cached page on append write
vmxnet3: use gro callback when UPT is enabled
io_uring: fix poll/netmsg alloc caches
io_uring/rsrc: fix rogue rsrc node grabbing
io_uring/poll: clear single/double poll flags on poll arming
zonefs: Do not propagate iomap_dio_rw() ENOTBLK error to user space
btrfs: ignore fiemap path cache when there are multiple paths for a node
btrfs: scan device in non-exclusive mode
btrfs: fix race between quota disable and quota assign ioctls
btrfs: fix deadlock when aborting transaction during relocation with scrub
Input: goodix - add Lenovo Yoga Book X90F to nine_bytes_report DMI table
Input: i8042 - add quirk for Fujitsu Lifebook A574/H
cifs: fix DFS traversal oops without CONFIG_CIFS_DFS_UPCALL
cifs: prevent infinite recursion in CIFSGetDFSRefer()
Input: focaltech - use explicitly signed char type
Input: alps - fix compatibility with -funsigned-char
Input: i8042 - add TUXEDO devices to i8042 quirk tables for partial fix
Revert "venus: firmware: Correct non-pix start and end addresses"
iommu/vt-d: Allow zero SAGAW if second-stage not supported
Input: xpad - fix incorrectly applied patch for MAP_PROFILE_BUTTON
pinctrl: ocelot: Fix alt mode for ocelot
net: ethernet: mtk_eth_soc: add missing ppe cache flush when deleting a flow
net: ethernet: mtk_eth_soc: fix L2 offloading with DSA untag offload
net: ethernet: mtk_eth_soc: fix flow block refcounting logic
net: dsa: sync unicast and multicast addresses for VLAN filters too
net: dsa: mv88e6xxx: Enable IGMP snooping on user ports only
bnxt_en: Add missing 200G link speed reporting
bnxt_en: Fix typo in PCI id to device description string mapping
bnxt_en: Fix reporting of test result in ethtool selftest
i40e: fix registers dump after run ethtool adapter self test
bnx2x: use the right build_skb() helper
net: ipa: 

[Kernel-packages] [Bug 2013236] Re: Failed to install bcmwl wireless driver during the install

[Paolo Pisati]

With the broadcom-sta-dkms package installed, can you blacklist bcma,
reboot, and see if wireless shows up?

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

Title:
  Failed to install bcmwl wireless driver during the install

Status in linux-firmware package in Ubuntu:
  Invalid
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Specifically for Lunar - using a Macbook Air 2012, its wireless driver
  was not enabled even though I ticked the wireless tickbox on the
  installer.

  A quick look at the installer logs reveals various issues

  syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [   43.063747] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [   43.063802] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063862] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063908] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2

  I will attach the installer logs manually since this was captured
  after the installation

  Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was
  installed correctly during the install so this is a regression with
  the 6.2 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+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 2015867] Re: Kernel 6.1 bumped the disk consumption on default images by 15%

[Paolo Pisati]

These are the size of linux-kvm debs at the time of this writing[1]:

linux-buildinfo-6.2.0-1003-kvm_6.2.0-1003.3_amd64.deb (397.9 KiB)
linux-headers-6.2.0-1003-kvm_6.2.0-1003.3_amd64.deb (15.9 MiB)
linux-image-unsigned-6.2.0-1003-kvm-dbgsym_6.2.0-1003.3_amd64.ddeb (203.2 
MiB)
linux-image-unsigned-6.2.0-1003-kvm_6.2.0-1003.3_amd64.deb (8.5 MiB)
linux-kvm-headers-6.2.0-1003_6.2.0-1003.3_all.deb (12.5 MiB)
linux-kvm-tools-6.2.0-1003_6.2.0-1003.3_amd64.deb (7.2 MiB)
linux-kvm_6.2.0-1003.3.diff.gz (5.1 MiB)
linux-kvm_6.2.0-1003.3.dsc (4.6 KiB)
linux-kvm_6.2.0.orig.tar.gz (208.4 MiB)
linux-modules-6.2.0-1003-kvm_6.2.0-1003.3_amd64.deb (17.0 MiB)
linux-tools-6.2.0-1003-kvm_6.2.0-1003.3_amd64.deb (1.7 KiB)

that looks different from the above numbers.

1: https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/bootstrap/+packages?field.name_filter=_filter=published_filter=lunar

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

Title:
  Kernel 6.1 bumped the disk consumption on default images by 15%

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  in the regular monitoring of metrics there was a bump in disk size last week.
  The default image once installed consumes now 994 (formerly 859) megabytes.

  Looking at the consumers there was much noise, but the biggest change
  was

  linux-headers-5.19.0-1008-kvm 25197 -> linux-headers-6.2.0-1002-kvm 108072 
  linux-modules-5.19.0-1008-kvm 76090 -> linux-modules-6.2.0-1002-kvm 97221

  I haven't looked deeper yet. Is that an accident and will be fixed
  soon, is that a change we can do nothing about, anything in between?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015867/+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 2012908] Re: nvidia driver 515 fails to boot on kernel 6.2

[Paolo Pisati]

New drivers are available in proposed (e.g. 515.105.01-0ubuntu1), can
you test them and and report your results?

Thanks!

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

Title:
  nvidia driver 515 fails to boot on kernel 6.2

Status in linux-signed package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  In Progress

Bug description:
  I just updated my Lunar install, which brought me the 6.2 kernel, and
  it failed to start, stalling after enumerating my USB devices, until
  something times out with a message saying that the udev event queue
  failed to be drained.

  When attempting to move on to the normal graphics boot from rescue
  mode once the timeout is hit, I simply get a black screen.

  I'm blaming this on the nvidia driver because of this appearing in the
  log:

  mars 27 10:33:54 gandalf kernel: INFO: task systemd-udevd:304 blocked for 
more than 120 seconds.
  mars 27 10:33:54 gandalf kernel:   Tainted: P   OE  
6.2.0-18-generic #18-Ubuntu
  mars 27 10:33:54 gandalf kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  mars 27 10:33:54 gandalf kernel: task:systemd-udevd   state:D stack:0 
pid:304   ppid:258flags:0x4006
  mars 27 10:33:54 gandalf kernel: Call Trace:
  mars 27 10:33:54 gandalf kernel:  
  mars 27 10:33:54 gandalf kernel:  __schedule+0x2aa/0x610
  mars 27 10:33:54 gandalf kernel:  schedule+0x63/0x110
  mars 27 10:33:54 gandalf kernel:  schedule_preempt_disabled+0x15/0x30
  mars 27 10:33:54 gandalf kernel:  __mutex_lock.constprop.0+0x3f8/0x7a0
  mars 27 10:33:54 gandalf kernel:  ? __kmem_cache_alloc_node+0x19d/0x340
  mars 27 10:33:54 gandalf kernel:  ? nv_drm_calloc+0x1e/0x40 [nvidia_drm]
  mars 27 10:33:54 gandalf kernel:  __mutex_lock_slowpath+0x13/0x20
  mars 27 10:33:54 gandalf kernel:  mutex_lock+0x3c/0x50
  mars 27 10:33:54 gandalf kernel:  
__nv_drm_connector_detect_internal+0x15c/0x2f0 [nvidia_drm]
  mars 27 10:33:54 gandalf kernel:  nv_drm_connector_detect+0xe/0x20 
[nvidia_drm]
  mars 27 10:33:54 gandalf kernel:  drm_helper_probe_detect_ctx+0xa3/0x120 
[drm_kms_helper]
  mars 27 10:33:54 gandalf kernel:  check_connector_changed+0x52/0x200 
[drm_kms_helper]
  mars 27 10:33:54 gandalf kernel:  drm_helper_hpd_irq_event+0xbc/0x170 
[drm_kms_helper]
  mars 27 10:33:54 gandalf kernel:  nv_drm_load+0x2e7/0x480 [nvidia_drm]
  mars 27 10:33:54 gandalf kernel:  ? __pfx_nv_drm_event_callback+0x10/0x10 
[nvidia_drm]
  mars 27 10:33:54 gandalf kernel:  drm_dev_register+0x10e/0x250 [drm]
  mars 27 10:33:54 gandalf kernel:  nv_drm_probe_devices+0x111/0x200 
[nvidia_drm]
  mars 27 10:33:54 gandalf kernel:  ? __pfx_init_module+0x10/0x10 [nvidia_drm]
  mars 27 10:33:54 gandalf kernel:  nv_drm_init+0x1e/0x60 [nvidia_drm]
  mars 27 10:33:54 gandalf kernel:  nv_linux_drm_init+0xe/0xff0 [nvidia_drm]
  mars 27 10:33:54 gandalf kernel:  do_one_initcall+0x5e/0x250
  mars 27 10:33:54 gandalf kernel:  do_init_module+0x7b/0x260
  mars 27 10:33:54 gandalf kernel:  load_module+0xc76/0xd60
  mars 27 10:33:54 gandalf kernel:  ? kernel_read_file+0x2a4/0x320
  mars 27 10:33:54 gandalf kernel:  __do_sys_finit_module+0xc4/0x140
  mars 27 10:33:54 gandalf kernel:  ? __do_sys_finit_module+0xc4/0x140
  mars 27 10:33:54 gandalf kernel:  __x64_sys_finit_module+0x18/0x30
  mars 27 10:33:54 gandalf kernel:  do_syscall_64+0x5b/0x90
  mars 27 10:33:54 gandalf kernel:  ? ksys_mmap_pgoff+0x120/0x260
  mars 27 10:33:54 gandalf kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
  mars 27 10:33:54 gandalf kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
  mars 27 10:33:54 gandalf kernel:  ? syscall_exit_to_user_mode+0x29/0x50
  mars 27 10:33:54 gandalf kernel:  ? do_syscall_64+0x67/0x90
  mars 27 10:33:54 gandalf kernel:  ? do_syscall_64+0x67/0x90
  mars 27 10:33:54 gandalf kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
  mars 27 10:33:54 gandalf kernel:  ? syscall_exit_to_user_mode+0x29/0x50
  mars 27 10:33:54 gandalf kernel:  ? do_syscall_64+0x67/0x90
  mars 27 10:33:54 gandalf kernel:  ? syscall_exit_to_user_mode+0x29/0x50
  mars 27 10:33:54 gandalf kernel:  ? do_syscall_64+0x67/0x90
  mars 27 10:33:54 gandalf kernel:  ? do_syscall_64+0x67/0x90
  mars 27 10:33:54 gandalf kernel:  entry_SYSCALL_64_after_hwframe+0x72/0xdc
  mars 27 10:33:54 gandalf kernel: RIP: 0033:0x7fd3dc85d89d
  mars 27 10:33:54 gandalf kernel: RSP: 002b:7ffc801034a8 EFLAGS: 0246 
ORIG_RAX: 0139
  mars 27 10:33:54 gandalf kernel: RAX: ffda RBX: 55f373907c60 
RCX: 7fd3dc85d89d
  mars 27 10:33:54 gandalf kernel: RDX:  RSI: 55f373889af0 
RDI: 0012
  mars 27 10:33:54 gandalf kernel: RBP: 55f373889af0 R08:  
R09: 7ffc801035d0
  mars 27 10:33:54 gandalf kernel: R10: 0012 R11: 0246 
R12: 0002
  mars 27 10:33:54 

[Kernel-packages] [Bug 2012559] Re: 6.2 kernel won't boot, may be nvidia related?

[Paolo Pisati]

** Also affects: nvidia-graphics-drivers-515 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-515 (Ubuntu)
   Status: New => In Progress

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

Title:
  6.2 kernel won't boot, may be nvidia related?

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  In Progress

Bug description:
  After installing most recent Lunar updates, linux-
  image-6.2.0-18-generic won't boot. First attempt to boot hung with
  gpu-manager service and other services blocked, something related to
  nvidia seemed to be going wrong. Subsequent attempts blocked at
  systemd-modules, I believe. Reverting to 6.1, boots fine.

  It did boot up enough on one attempt that I was able to SSH in, even
  though I couldn't log in on the console because it never got the point
  of starting up the session manager or init on the other VTs. I'm
  attaching a journalctl log from before the first reboot attempt.
  Perhaps there is something illuminating in there; I honestly can't
  tell.

  Note that while trying to get it to finish booting the first time when
  I was SSH'd in I did kill some processes, so you'll see that in the
  log.

  But just to reiterate, I attempted booting several times after that
  and it never came up to the point of being on the network.

  I thought maybe it might be a DisplayLink issue, but the problem
  persisted even when I rebooted without the DisplayLink hub plugged in.

  Note also that as I said above I had to revert to 6.1 to get it to
  boot, so you'll see that as the last (successful) boot attempt in the
  log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-18-generic 6.2.0-18.18
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 22 16:33:06 2023
  InstallationDate: Installed on 2019-01-02 (1540 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Predator G6-710
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.1.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.1.0-16-generic N/A
   linux-backports-modules-6.1.0-16-generic  N/A
   linux-firmware20230316.gitc761dbe8-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2022-11-24 (118 days ago)
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012559/+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 2012908] Re: nvidia driver 515 fails to boot on kernel 6.2

[Paolo Pisati]

** Changed in: nvidia-graphics-drivers-515 (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  nvidia driver 515 fails to boot on kernel 6.2

Status in linux-signed package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  In Progress

Bug description:
  I just updated my Lunar install, which brought me the 6.2 kernel, and
  it failed to start, stalling after enumerating my USB devices, until
  something times out with a message saying that the udev event queue
  failed to be drained.

  When attempting to move on to the normal graphics boot from rescue
  mode once the timeout is hit, I simply get a black screen.

  I'm blaming this on the nvidia driver because of this appearing in the
  log:

  mars 27 10:33:54 gandalf kernel: INFO: task systemd-udevd:304 blocked for 
more than 120 seconds.
  mars 27 10:33:54 gandalf kernel:   Tainted: P   OE  
6.2.0-18-generic #18-Ubuntu
  mars 27 10:33:54 gandalf kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  mars 27 10:33:54 gandalf kernel: task:systemd-udevd   state:D stack:0 
pid:304   ppid:258flags:0x4006
  mars 27 10:33:54 gandalf kernel: Call Trace:
  mars 27 10:33:54 gandalf kernel:  
  mars 27 10:33:54 gandalf kernel:  __schedule+0x2aa/0x610
  mars 27 10:33:54 gandalf kernel:  schedule+0x63/0x110
  mars 27 10:33:54 gandalf kernel:  schedule_preempt_disabled+0x15/0x30
  mars 27 10:33:54 gandalf kernel:  __mutex_lock.constprop.0+0x3f8/0x7a0
  mars 27 10:33:54 gandalf kernel:  ? __kmem_cache_alloc_node+0x19d/0x340
  mars 27 10:33:54 gandalf kernel:  ? nv_drm_calloc+0x1e/0x40 [nvidia_drm]
  mars 27 10:33:54 gandalf kernel:  __mutex_lock_slowpath+0x13/0x20
  mars 27 10:33:54 gandalf kernel:  mutex_lock+0x3c/0x50
  mars 27 10:33:54 gandalf kernel:  
__nv_drm_connector_detect_internal+0x15c/0x2f0 [nvidia_drm]
  mars 27 10:33:54 gandalf kernel:  nv_drm_connector_detect+0xe/0x20 
[nvidia_drm]
  mars 27 10:33:54 gandalf kernel:  drm_helper_probe_detect_ctx+0xa3/0x120 
[drm_kms_helper]
  mars 27 10:33:54 gandalf kernel:  check_connector_changed+0x52/0x200 
[drm_kms_helper]
  mars 27 10:33:54 gandalf kernel:  drm_helper_hpd_irq_event+0xbc/0x170 
[drm_kms_helper]
  mars 27 10:33:54 gandalf kernel:  nv_drm_load+0x2e7/0x480 [nvidia_drm]
  mars 27 10:33:54 gandalf kernel:  ? __pfx_nv_drm_event_callback+0x10/0x10 
[nvidia_drm]
  mars 27 10:33:54 gandalf kernel:  drm_dev_register+0x10e/0x250 [drm]
  mars 27 10:33:54 gandalf kernel:  nv_drm_probe_devices+0x111/0x200 
[nvidia_drm]
  mars 27 10:33:54 gandalf kernel:  ? __pfx_init_module+0x10/0x10 [nvidia_drm]
  mars 27 10:33:54 gandalf kernel:  nv_drm_init+0x1e/0x60 [nvidia_drm]
  mars 27 10:33:54 gandalf kernel:  nv_linux_drm_init+0xe/0xff0 [nvidia_drm]
  mars 27 10:33:54 gandalf kernel:  do_one_initcall+0x5e/0x250
  mars 27 10:33:54 gandalf kernel:  do_init_module+0x7b/0x260
  mars 27 10:33:54 gandalf kernel:  load_module+0xc76/0xd60
  mars 27 10:33:54 gandalf kernel:  ? kernel_read_file+0x2a4/0x320
  mars 27 10:33:54 gandalf kernel:  __do_sys_finit_module+0xc4/0x140
  mars 27 10:33:54 gandalf kernel:  ? __do_sys_finit_module+0xc4/0x140
  mars 27 10:33:54 gandalf kernel:  __x64_sys_finit_module+0x18/0x30
  mars 27 10:33:54 gandalf kernel:  do_syscall_64+0x5b/0x90
  mars 27 10:33:54 gandalf kernel:  ? ksys_mmap_pgoff+0x120/0x260
  mars 27 10:33:54 gandalf kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
  mars 27 10:33:54 gandalf kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
  mars 27 10:33:54 gandalf kernel:  ? syscall_exit_to_user_mode+0x29/0x50
  mars 27 10:33:54 gandalf kernel:  ? do_syscall_64+0x67/0x90
  mars 27 10:33:54 gandalf kernel:  ? do_syscall_64+0x67/0x90
  mars 27 10:33:54 gandalf kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
  mars 27 10:33:54 gandalf kernel:  ? syscall_exit_to_user_mode+0x29/0x50
  mars 27 10:33:54 gandalf kernel:  ? do_syscall_64+0x67/0x90
  mars 27 10:33:54 gandalf kernel:  ? syscall_exit_to_user_mode+0x29/0x50
  mars 27 10:33:54 gandalf kernel:  ? do_syscall_64+0x67/0x90
  mars 27 10:33:54 gandalf kernel:  ? do_syscall_64+0x67/0x90
  mars 27 10:33:54 gandalf kernel:  entry_SYSCALL_64_after_hwframe+0x72/0xdc
  mars 27 10:33:54 gandalf kernel: RIP: 0033:0x7fd3dc85d89d
  mars 27 10:33:54 gandalf kernel: RSP: 002b:7ffc801034a8 EFLAGS: 0246 
ORIG_RAX: 0139
  mars 27 10:33:54 gandalf kernel: RAX: ffda RBX: 55f373907c60 
RCX: 7fd3dc85d89d
  mars 27 10:33:54 gandalf kernel: RDX:  RSI: 55f373889af0 
RDI: 0012
  mars 27 10:33:54 gandalf kernel: RBP: 55f373889af0 R08:  
R09: 7ffc801035d0
  mars 27 10:33:54 gandalf kernel: R10: 0012 R11: 0246 
R12: 0002
  mars 27 10:33:54 gandalf kernel: R13: 

[Kernel-packages] [Bug 2004146] [NEW] Lunar update: v6.1.7 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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


Linux 6.1.7
pinctrl: amd: Add dynamic debugging for active GPIOs
Revert "usb: ulpi: defer ulpi_register on ulpi_read_id timeout"
block: handle bio_split_to_limits() NULL return
io_uring/io-wq: only free worker if it was allocated for creation
io_uring/io-wq: free worker if task_work creation is canceled
drm/i915: Fix CFI violations in gt_sysfs
io_uring/poll: attempt request issue after racy poll wakeup
io_uring: lock overflowing for IOPOLL
efi: fix NULL-deref in init error path
ALSA: usb-audio: Fix possible NULL pointer dereference in 
snd_usb_pcm_has_fixed_rate()
platform/x86/amd: Fix refcount leak in amd_pmc_probe
platform/surface: aggregator: Add missing call to ssam_request_sync_free()
bnxt: make sure we return pages to the pool
net: hns3: fix wrong use of rss size during VF rss config
net: lan966x: check for ptp to be enabled in lan966x_ptp_deinit()
igc: Fix PPS delta between two synchronized end-points
perf kmem: Support field "node" in evsel__process_alloc_event() coping with 
recent tracepoint restructuring
perf kmem: Support legacy tracepoints
perf build: Properly guard libbpf includes
octeontx2-pf: Fix resource leakage in VF driver unbind
selftests/net: l2_tos_ttl_inherit.sh: Ensure environment cleanup on failure.
selftests/net: l2_tos_ttl_inherit.sh: Run tests in their own netns.
selftests/net: l2_tos_ttl_inherit.sh: Set IPv6 addresses with "nodad".
net/mlx5e: Fix macsec possible null dereference when updating MAC security 
entity (SecY)
net/mlx5e: Fix macsec ssci attribute handling in offload path
net/mlx5e: Don't support encap rules with gbp option
net/mlx5: Fix ptp max frequency adjustment range
net/mlx5e: IPoIB, Fix child PKEY interface stats on rx path
net/mlx5e: IPoIB, Block PKEY interfaces with less rx queues than parent
net/mlx5e: IPoIB, Block queue count configuration when sub interfaces are 
present
net/mlx5e: Verify dev is present for fix features ndo
net/mlx5: Fix command stats access after free
net/mlx5e: TC, Keep mod hdr actions after mod hdr alloc
net/mlx5: check attr pointer validity before dereferencing it
Revert "r8169: disable detection of chip version 36"
net/sched: act_mpls: Fix warning during failed attribute validation
drm/vmwgfx: Remove rcu locks from user resources
drm/vmwgfx: Remove vmwgfx_hashtab
drm/vmwgfx: Refactor ttm reference object hashtable to use linux/hashtable.
drm/vmwgfx: Refactor resource validation hashtable to use linux/hashtable 
implementation.
drm/vmwgfx: Remove ttm object hashtable
drm/vmwgfx: Refactor resource manager's hashtable to use linux/hashtable 
implementation.
drm/vmwgfx: Write the driver id registers
ice: Add check for kzalloc
ice: Fix potential memory leak in ice_gnss_tty_write()
drm/amdgpu: Fix potential NULL dereference
tools/nolibc: fix the O_* fcntl/open macro definitions for riscv
tools/nolibc: restore mips branch ordering in the _start block
ASoC: qcom: Fix building APQ8016 machine driver without SOUNDWIRE
af_unix: selftest: Fix the size of the parameter to connect()
gro: take care of DODGY packets
gro: avoid checking for a failed search
nfc: pn533: Wait for out_urb's completion in pn533_usb_send_frame()
hvc/xen: lock console list traversal
sched/core: Fix arch_scale_freq_tick() on tickless systems
octeontx2-af: Fix LMAC config in cgx_lmac_rx_tx_enable
nfsd: fix handling of cached open files in nfsd4_open codepath
nfsd: rework refcounting in filecache
NFSD: Add an nfsd_file_fsync tracepoint
nfsd: reorganize filecache.c
nfsd: remove the pages_flushed statistic from filecache
NFSD: Add an NFSD_FILE_GC flag to enable nfsd_file garbage collection
NFSD: Revert "NFSD: NFSv4 CLOSE should release an nfsd_file immediately"
NFSD: Pass the target nfsd_file to nfsd_commit()
tipc: fix unexpected link reset due to discovery messages
stmmac: dwmac-mediatek: remove the dwmac_fix_mac_speed
ALSA: usb-audio: Relax hw constraints for implicit fb sync
ALSA: usb-audio: Make sure to stop endpoints before closing EPs
mtd: cfi: allow building spi-intel standalone
mtd: parsers: scpart: fix __udivdi3 undefined on mips
ASoC: wm8904: fix wrong outputs volume after power reactivation
drm/msm/dpu: Fix memory leak in msm_mdss_parse_data_bus_icc_path
drm/msm/dpu: Fix some kernel-doc comments
ASoC: Intel: sof-nau8825: fix module alias overflow
ASoC: Intel: sof_nau8825: support rt1015p speaker amplifier
ASoC: Intel: fix sof-nau8825 link failure
scsi: ufs: core: WLUN suspend SSU/enter hibern8 fail recovery
scsi: 

[Kernel-packages] [Bug 2004147] [NEW] Lunar update: v6.1.8 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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


Linux 6.1.8
soc: qcom: apr: Make qcom,protection-domain optional again
Revert "wifi: mac80211: fix memory leak in ieee80211_if_add()"
block: mq-deadline: Rename deadline_is_seq_writes()
net/mlx5: fix missing mutex_unlock in mlx5_fw_fatal_reporter_err_work()
octeontx2-pf: Fix the use of GFP_KERNEL in atomic context on rt
net/ulp: use consistent error code when blocking ULP
octeontx2-pf: Avoid use of GFP_KERNEL in atomic context
drm/amdgpu: correct MEC number for gfx11 APUs
drm/amdgpu: add tmz support for GC IP v11.0.4
drm/amdgpu: add tmz support for GC 11.0.1
drm/amdgpu: enable GFX Clock Gating control for GC IP v11.0.4
drm/amdgpu: enable GFX Power Gating for GC IP v11.0.4
drm/amdgpu: enable GFX IP v11.0.4 CG support
drm/amdgpu: enable PSP IP v13.0.11 support
drm/amdgpu/discovery: enable nbio support for NBIO v7.7.1
drm/amdgpu/pm: use the specific mailbox registers only for SMU IP v13.0.4
drm/amdgpu/soc21: add mode2 asic reset for SMU IP v13.0.11
drm/amdgpu/pm: add GFXOFF control IP version check for SMU IP v13.0.11
drm/amdgpu: add smu 13 support for smu 13.0.11
drm/amdgpu/pm: enable swsmu for SMU IP v13.0.11
drm/amdgpu/discovery: add PSP IP v13.0.11 support
drm/amdgpu: add gmc v11 support for GC 11.0.4
drm/amdgpu: add gfx support for GC 11.0.4
drm/amdgpu/discovery: set the APU flag for GC 11.0.4
drm/amdgpu: set GC 11.0.4 family
drm/amdgpu/discovery: enable mes support for GC v11.0.4
drm/amdgpu/discovery: enable gfx v11 for GC 11.0.4
drm/amdgpu/discovery: enable gmc v11 for GC 11.0.4
drm/amdgpu/discovery: enable soc21 common for GC 11.0.4
x86/fpu: Use _Alignof to avoid undefined behavior in TYPE_ALIGN
exit: Use READ_ONCE() for all oops/warn limit reads
docs: Fix path paste-o for /sys/kernel/warn_count
panic: Expose "warn_count" to sysfs
panic: Introduce warn_limit
panic: Consolidate open-coded panic_on_warn checks
exit: Allow oops_limit to be disabled
exit: Expose "oops_count" to sysfs
exit: Put an upper limit on how often we can oops
panic: Separate sysctl logic from CONFIG_SMP
efi: rt-wrapper: Add missing include
arm64: efi: Execute runtime services from a dedicated stack
fs/ntfs3: Fix attr_punch_hole() null pointer derenference
cifs: reduce roundtrips on create/qinfo requests
drm/amd/display: disable S/G display on DCN 3.1.4
drm/amd/display: disable S/G display on DCN 3.1.5
drm/amd/display: Fix COLOR_SPACE_YCBCR2020_TYPE matrix
drm/amd/display: Calculate output_color_space after pixel encoding adjustment
drm/amd/display: Fix set scaling doesn's work
drm/i915: Remove unused variable
drm/i915: Allow switching away via vga-switcheroo if uninitialized
drm/i915/display: Check source height is > 0
drm/i915: re-disable RC6p on Sandy Bridge
drm/amdgpu: Correct the power calcultion for Renior/Cezanne.
drm/amdgpu: allow multipipe policy on ASICs with one MEC
drm/amdgpu: fix amdgpu_job_free_resources v2
ARM: omap1: fix !ARCH_OMAP1_ANY link failures
ARM: dts: qcom: apq8084-ifc6540: fix overriding SDHCI
VMCI: Use threaded irqs instead of tasklets
mei: me: add meteor lake point M DID
mei: bus: fix unlink on bus in error path
gsmi: fix null-deref in gsmi_get_variable
serial: exar: Add support for Sealevel 7xxxC serial cards
serial: atmel: fix incorrect baudrate setup
serial: amba-pl011: fix high priority character transmission in rs486 mode
dmaengine: idxd: Do not call DMX TX callbacks during workqueue disable
dmaengine: idxd: Prevent use after free on completion memory
dmaengine: idxd: Let probe fail when workqueue cannot be enabled
dmaengine: tegra210-adma: fix global intr clear
dmaengine: lgm: Move DT parsing after initialization
serial: pch_uart: Pass correct sg to dma_unmap_sg()
dt-bindings: phy: g12a-usb3-pcie-phy: fix compatible string documentation
dt-bindings: phy: g12a-usb2-phy: fix compatible string documentation
arm64: dts: imx8mp: correct usb clocks
usb-storage: apply IGNORE_UAS only for HIKSEMI MD202 on RTL9210
usb: gadget: f_ncm: fix potential NULL ptr deref in ncm_bitrate()
USB: gadget: Add ID numbers to configfs-gadget driver names
usb: gadget: g_webcam: Send color matching descriptor per frame
usb: typec: altmodes/displayport: Fix pin assignment calculation
usb: typec: altmodes/displayport: Add pin assignment helper
usb: typec: tcpm: Fix altmode re-registration causes sysfs create fail
usb: musb: fix error return code in omap2430_probe()
usb: host: ehci-fsl: Fix module alias
usb: cdns3: remove fetched trb from cache before dequeuing
USB: serial: 

[Kernel-packages] [Bug 2003688] [NEW] Lunar update: v6.1.5 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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


Linux 6.1.5
wifi: ath11k: Send PME message during wakeup from D3cold
efi: random: combine bootloader provided RNG seed with RNG protocol output
drm/i915/dsi: fix MIPI_BKLT_EN_1 native GPIO index
drm/i915/dsi: add support for ICL+ native MIPI GPIO sequence
ksmbd: check nt_len to be at least CIFS_ENCPWD_SIZE in 
ksmbd_decode_ntlmssp_auth_blob
ksmbd: send proper error response in smb2_tree_connect()
ksmbd: fix infinite loop in ksmbd_conn_handler_loop()
btrfs: handle case when repair happens with dev-replace
drm/amd/display: Uninitialized variables causing 4k60 UCLK to stay at DPM1 and 
not DPM0
drm/amd/display: Add check for DET fetch latency hiding for dcn32
virtio_blk: Fix signedness bug in virtblk_prep_rq()
virtio-blk: use a helper to handle request queuing errors
drm/i915/gvt: fix vgpu debugfs clean in remove
drm/i915/gvt: fix gvt debugfs destroy
drm/amdkfd: Fix kernel warning during topology setup
drm/plane-helper: Add the missing declaration of drm_atomic_state
of/fdt: run soc memory setup when early_init_dt_scan_memory fails
riscv, kprobes: Stricter c.jr/c.jalr decoding
riscv: uaccess: fix type of 0 variable on error in get_user()
thermal: int340x: Add missing attribute for data rate base
vhost_vdpa: fix the crash in unmap a large memory
tpm: Allow system suspend to continue when TPM suspend fails
io_uring: fix CQ waiting timeout handling
io_uring: pin context while queueing deferred tw
block: don't allow splitting of a REQ_NOWAIT bio
net: dsa: tag_qca: fix wrong MGMT_DATA2 size
net: dsa: qca8k: fix wrong length value for mgmt eth packet
Revert "net: dsa: qca8k: cache lo and hi for mdio write"
Revert "drm/amd/display: Enable Freesync Video Mode by default"
bpf: Fix panic due to wrong pageattr of im->image
fbdev: matroxfb: G200eW: Increase max memory from 1 MB to 16 MB
nfsd: fix handling of readdir in v4root vs. mount upcall timeout
x86/bugs: Flush IBP in ib_prctl_set()
x86/kexec: Fix double-free of elf header buffer
ASoC: SOF: Intel: pci-tgl: unblock S5 entry if DMA stop has failed"
nvme: also return I/O command effects from nvme_command_effects
nvmet: use NVME_CMD_EFFECTS_CSUPP instead of open coding it
kunit: alloc_string_stream_fragment error handling bug fix
io_uring: check for valid register opcode earlier
ACPI: video: Don't enable fallback path for creating ACPI backlight by default
drm/amd/display: Report to ACPI video if no panels were found
ACPI: video: Allow GPU drivers to report no panels
nvme: fix multipath crash caused by flush request when blktrace is enabled
io_uring/cancel: re-grab ctx mutex after finishing wait
drm/amdkfd: Fix double release compute pasid
drm/amdkfd: Fix kfd_process_device_init_vm error handling
drm/amdgpu: Fix size validation for non-exclusive domains (v4)
ASoC: SOF: mediatek: initialize panic_info to zero
ASoC: Intel: bytcr_rt5640: Add quirk for the Advantech MICA-071 tablet
9p/client: fix data race on req->status
ASoC: SOF: Revert: "core: unregister clients and machine drivers in .shutdown"
hfs/hfsplus: avoid WARN_ON() for sanity check, use proper error handling
usb: dwc3: xilinx: include linux/gpio/consumer.h
udf: Fix extension of the last extent in the file
caif: fix memory leak in cfctrl_linkup_request()
net/ulp: prevent ULP without clone op from entering the LISTEN status
qed: allow sleep in qed_mcp_trace_dump()
ublk: honor IO_URING_F_NONBLOCK for handling control command
drm/i915/gvt: fix double free bug in split_2MB_gtt_entry
drm/i915: unpin on error in intel_vgpu_shadow_mm_pin()
perf stat: Fix handling of --for-each-cgroup with --bpf-counters to match non 
BPF mode
perf stat: Fix handling of unsupported cgroup events when using BPF counters
perf lock contention: Fix core dump related to not finding the 
"__sched_text_end" symbol on s/390
usb: rndis_host: Secure rndis_query check against int overflow
octeontx2-pf: Fix lmtst ID used in aura free
drivers/net/bonding/bond_3ad: return when there's no aggregator
fs/ntfs3: don't hold ni_lock when calling truncate_setsize()
drm/imx: ipuv3-plane: Fix overlay plane width
perf tools: Fix resources leak in perf_data__open_dir()
drm/virtio: Fix memory leak in virtio_gpu_object_create()
netfilter: ipset: Rework long task execution when adding/deleting entries
netfilter: ipset: fix hash:net,port,net hang with /0 subnet
net: sparx5: Fix reading of the MAC address
vxlan: Fix memory leaks in error path
net: sched: cbq: dont intepret cls results when asked to drop
net: sched: 

[Kernel-packages] [Bug 2003686] [NEW] Lunar update: v6.1.3 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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


Linux 6.1.3
kcsan: Instrument memcpy/memset/memmove with newer Clang
SUNRPC: Don't leak netobj memory when gss_read_proxy_verf() fails
tpm: tpm_tis: Add the missed acpi_put_table() to fix memory leak
tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak
tpm: acpi: Call acpi_put_table() to fix memory leak
mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING
block: Do not reread partition table on exclusively open device
f2fs: allow to read node block after shutdown
f2fs: should put a page when checking the summary info
mm, compaction: fix fast_isolate_around() to stay within boundaries
md: fix a crash in mempool_free
mfd: mt6360: Add bounds checking in Regmap read/write call-backs
pnode: terminate at peers of source
ALSA: hda/hdmi: Static PCM mapping again with AMD HDMI codecs
ALSA: line6: fix stack overflow in line6_midi_transmit
ALSA: line6: correct midi status byte when receiving data from podxt
ovl: update ->f_iocb_flags when ovl_change_flags() modifies ->f_flags
ovl: Use ovl mounter's fsuid and fsgid in ovl_link()
binfmt: Fix error return code in load_elf_fdpic_binary()
ACPI: x86: s2idle: Stop using AMD specific codepath for Rembrandt+
ACPI: x86: s2idle: Force AMD GUID/_REV 2 on HP Elitebook 865
hfsplus: fix bug causing custom uid and gid being unable to be assigned with 
mount
pstore/zone: Use GFP_ATOMIC to allocate zone buffer
pstore: Properly assign mem_type property
kmsan: include linux/vmalloc.h
kmsan: export kmsan_handle_urb
mm/mempolicy: fix memory leak in set_mempolicy_home_node system call
mm, mremap: fix mremap() expanding vma with addr inside vma
rtmutex: Add acquire semantics for rtmutex lock acquisition slow path
futex: Fix futex_waitv() hrtimer debug object leak on kcalloc error
HID: plantronics: Additional PIDs for double volume key presses quirk
HID: multitouch: fix Asus ExpertBook P2 P2451FA trackpoint
kprobes: kretprobe events missing on 2-core KVM guest
NFSD: fix use-after-free in __nfs42_ssc_open()
rtc: msc313: Fix function prototype mismatch in msc313_rtc_probe()
powerpc/rtas: avoid scheduling in rtas_os_term()
powerpc/rtas: avoid device tree lookups in rtas_os_term()
iommu/mediatek: Fix crash on isr after kexec()
objtool: Fix SEGFAULT
fs/ntfs3: Fix slab-out-of-bounds in r_page
fs/ntfs3: Delete duplicate condition in ntfs_read_mft()
fs/ntfs3: Use __GFP_NOWARN allocation at ntfs_fill_super()
fs/ntfs3: Use __GFP_NOWARN allocation at wnd_init()
fs/ntfs3: Validate index root when initialize NTFS security
phy: sun4i-usb: Add support for the H616 USB PHY
phy: sun4i-usb: Introduce port2 SIDDQ quirk
soundwire: dmi-quirks: add quirk variant for LAPBC710 NUC15
fs/ntfs3: Fix slab-out-of-bounds read in run_unpack
fs/ntfs3: Validate resident attribute name
fs/ntfs3: Validate buffer length while parsing index
fs/ntfs3: Validate attribute name offset
fs/ntfs3: Add null pointer check for inode operations
fs/ntfs3: Fix memory leak on ntfs_fill_super() error path
fs/ntfs3: Add null pointer check to attr_load_runs_vcn
fs/ntfs3: Validate data run offset
fs/ntfs3: Add overflow check for attribute size
fs/ntfs3: Validate BOOT record_size
nvmet: don't defer passthrough commands with trivial effects to the workqueue
nvme: fix the NVME_CMD_EFFECTS_CSE_MASK definition
ata: ahci: Fix PCS quirk application for suspend
block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq
ACPI: video: Fix Apple GMUX backlight detection
ACPI: resource: Add Asus ExpertBook B2502 to Asus quirks
ACPI: resource: do IRQ override on Lenovo 14ALC7
ACPI: resource: do IRQ override on XMG Core 15
nvme-pci: fix page size checks
nvme-pci: fix mempool alloc size
nvme-pci: fix doorbell buffer value endianness
io_uring: pass in EPOLL_URING_WAKE for eventfd signaling and wakeups
eventfd: provide a eventfd_signal_mask() helper
eventpoll: add EPOLL_URING_WAKE poll wakeup flag

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

** Affects: linux (Ubuntu Lunar)
 Importance: Undecided
 Status: Confirmed


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Lunar)
   Importance: Undecided
   Status: Confirmed

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

Title:
  Lunar update: v6.1.3 

[Kernel-packages] [Bug 2003687] [NEW] Lunar update: v6.1.4 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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


Linux 6.1.4
drm/amd/pm: correct the fan speed retrieving in PWM for some SMU13 asics
drm/amd/pm: bump SMU13.0.0 driver_if header to version 0x34
drm/amd/pm: add missing SMU13.0.7 mm_dpm feature mapping
drm/amd/pm: add missing SMU13.0.0 mm_dpm feature mapping
drm/i915/migrate: Account for the reserved_space
drm/i915: improve the catch-all evict to handle lock contention
drm/amdgpu: make display pinning more flexible (v2)
drm/amdgpu: handle polaris10/11 overlap asics (v2)
drm/amd/display: Add DCN314 display SG Support
drm/i915/ttm: consider CCS for backup objects
ext4: allocate extended attribute value in vmalloc area
ext4: avoid unaccounted block allocation when expanding inode
ext4: initialize quota before expanding inode in setproject ioctl
ext4: fix inode leak in ext4_xattr_inode_create() on an error path
ext4: fix kernel BUG in 'ext4_write_inline_data_end()'
ext4: fix deadlock due to mbcache entry corruption
ext4: avoid BUG_ON when creating xattrs
ext4: fix corrupt backup group descriptors after online resize
ext4: dont return EINVAL from GETFSUUID when reporting UUID length
ext4: fix bad checksum after online resize
ext4: fix error code return to user-space in ext4_get_branch()
ext4: fix corruption when online resizing a 1K bigalloc fs
ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline
ext4: don't fail GETFSUUID when the caller provides a long buffer
ext4: init quota for 'old.inode' in 'ext4_rename'
ext4: fix uninititialized value in 'ext4_evict_inode'
ext4: fix off-by-one errors in fast-commit block filling
ext4: fix unaligned memory access in ext4_fc_reserve_space()
ext4: add missing validation of fast-commit record lengths
ext4: don't set up encryption key during jbd2 transaction
ext4: fix leaking uninitialized memory in fast-commit journal
ext4: disable fast-commit of encrypted dir operations
ext4: don't allow journal inode to have encrypt flag
ext4: fix bug_on in __es_tree_search caused by bad boot loader inode
ext4: check and assert if marking an no_delete evicting inode dirty
ext4: journal_path mount options should follow links
ext4: fix reserved cluster accounting in __es_remove_extent()
ext4: fix bug_on in __es_tree_search caused by bad quota inode
ext4: add helper to check quota inums
ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode
ext4: fix undefined behavior in bit shift for ext4_check_flag_values
ext4: fix use-after-free in ext4_orphan_cleanup
fs: ext4: initialize fsdata in pagecache_write()
ext4: correct inconsistent error msg in nojournal mode
ext4: remove trailing newline from ext4_msg() message
ext4: add inode table check in __ext4_get_inode_loc to aovid possible infinite 
loop
ext4: silence the warning when evicting inode with dioread_nolock
drm/etnaviv: reap idle mapping if it doesn't match the softpin address
drm/ingenic: Fix missing platform_driver_unregister() call in ingenic_drm_init()
drm/i915/dsi: fix VBT send packet port selection for dual link DSI
drm/etnaviv: move idle mapping reaping into separate function
drm/mgag200: Fix PLL setup for G200_SE_A rev >=4
drm/vmwgfx: Validate the box size for the snooped cursor
drm/connector: send hotplug uevent on connector cleanup
device_cgroup: Roll back to original exceptions after copy failure
parisc: Drop PMD_SHIFT from calculation in pgtable.h
parisc: Drop duplicate kgdb_pdc console
parisc: Add missing FORCE prerequisites in Makefile
parisc: Fix locking in pdc_iodc_print() firmware call
parisc: Drop locking in pdc console code
parisc: led: Fix potential null-ptr-deref in start_task()
remoteproc: imx_rproc: Correct i.MX93 DRAM mapping
remoteproc: core: Do pm_relax when in RPROC_OFFLINE state
remoteproc: imx_dsp_rproc: Add mutex protection for workqueue
hugetlb: really allocate vma lock for all sharable vmas
test_kprobes: Fix implicit declaration error of test_kprobes
iommu/amd: Fix ill-formed ivrs_ioapic, ivrs_hpet and ivrs_acpihid options
iommu/amd: Fix ivrs_acpihid cmdline parsing code
phy: qcom-qmp-combo: fix sc8180x reset
phy: qcom-qmp-combo: fix sdm845 reset
bus: mhi: host: Fix race between channel preparation and M0 event
driver core: Fix bus_type.match() error handling in __driver_attach()
crypto: ccp - Add support for TEE for PCI ID 0x14CA
crypto: n2 - add missing hash statesize
riscv: mm: notify remote harts about mmu cache updates
riscv: stacktrace: Fixup ftrace_graph_ret_addr retp argument
RISC-V: kexec: Fix memory leak of elf header 

[Kernel-packages] [Bug 2003689] [NEW] Lunar update: v6.1.6 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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


Linux 6.1.6
ALSA: hda: cs35l41: Check runtime suspend capability at runtime_idle
ALSA: hda - Enable headset mic on another Dell laptop with ALC3254
ALSA: hda: cs35l41: Don't return -EINVAL from system suspend/resume
ALSA: hda/realtek: fix mute/micmute LEDs don't work for a HP platform
ALSA: hda/hdmi: Add a HP device 0x8715 to force connect list
ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF
net: sched: disallow noqueue for qdisc classes
gcc: disable -Warray-bounds for gcc-11 too
Revert "SUNRPC: Use RMW bitops in single-threaded hot paths"
selftests/vm/pkeys: Add a regression test for setting PKRU through ptrace
x86/fpu: Emulate XRSTOR's behavior if the xfeatures PKRU bit is not set
x86/fpu: Allow PKRU to be (once again) written by ptrace.
x86/fpu: Add a pkru argument to copy_uabi_to_xstate()
x86/fpu: Add a pkru argument to copy_uabi_from_kernel_to_xstate().
x86/fpu: Take task_struct* in copy_sigframe_from_user_to_xstate()
parisc: Align parisc MADV_XXX constants with all other architectures

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

** Affects: linux (Ubuntu Lunar)
 Importance: Undecided
 Status: Confirmed


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Lunar)
   Importance: Undecided
   Status: Confirmed

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

Title:
  Lunar update: v6.1.6 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Lunar:
  Confirmed

Bug description:
  
  SRU Justification

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

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

  
  Linux 6.1.6
  ALSA: hda: cs35l41: Check runtime suspend capability at runtime_idle
  ALSA: hda - Enable headset mic on another Dell laptop with ALC3254
  ALSA: hda: cs35l41: Don't return -EINVAL from system suspend/resume
  ALSA: hda/realtek: fix mute/micmute LEDs don't work for a HP platform
  ALSA: hda/hdmi: Add a HP device 0x8715 to force connect list
  ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF
  net: sched: disallow noqueue for qdisc classes
  gcc: disable -Warray-bounds for gcc-11 too
  Revert "SUNRPC: Use RMW bitops in single-threaded hot paths"
  selftests/vm/pkeys: Add a regression test for setting PKRU through ptrace
  x86/fpu: Emulate XRSTOR's behavior if the xfeatures PKRU bit is not set
  x86/fpu: Allow PKRU to be (once again) written by ptrace.
  x86/fpu: Add a pkru argument to copy_uabi_to_xstate()
  x86/fpu: Add a pkru argument to copy_uabi_from_kernel_to_xstate().
  x86/fpu: Take task_struct* in copy_sigframe_from_user_to_xstate()
  parisc: Align parisc MADV_XXX constants with all other architectures

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003689/+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 1998106] Re: Fix AMD-PState driver for Genoa CPU

[Paolo Pisati]

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

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

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

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

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

** Changed in: linux-oem-5.14 (Ubuntu Jammy)
   Status: New => Invalid

** Changed in: linux-oem-5.14 (Ubuntu Kinetic)
   Status: New => Invalid

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

Title:
  Fix AMD-PState driver for Genoa CPU

Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  New
Status in linux-oem-5.17 package in Ubuntu:
  New
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  New
Status in linux-oem-5.17 source package in Focal:
  New
Status in linux source package in Jammy:
  Incomplete
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  New
Status in linux source package in Kinetic:
  Incomplete
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  [Impact]

  During AMD Genoa development, the datacenter team identified
  performance regressions that were root caused in the amd-pstate
  driver. A first round of fixes already landed upstream (v6.1-rc7) in
  the amd-pstate driver, and should be backported to all the affected
  kernels.

  [Fix]

  Backport the upstream amd-pstate fixes:

  https://lore.kernel.org/linux-
  
pm/20221117073541.3350600-1-perry.y...@amd.com/T/#m4616d857ca472937d1e1d31131ddc3261fa17b2a

  [Regression potential]

  Clean cherry-picks of already upstream (v6.1-rc7) fixes, impact a
  single driver (amd-pstate) and the new mode (passive) is disabled by
  default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998106/+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 1998106] [NEW] Fix AMD-PState driver for Genoa CPU

[Paolo Pisati]

Public bug reported:

[Impact]

During AMD Genoa development, the datacenter team identified performance
regressions that were root caused in the amd-pstate driver. A first
round of fixes already landed upstream (v6.1-rc7) in the amd-pstate
driver, and should be backported to all the affected kernels.

[Fix]

Backport the upstream amd-pstate fixes:

https://lore.kernel.org/linux-
pm/20221117073541.3350600-1-perry.y...@amd.com/T/#m4616d857ca472937d1e1d31131ddc3261fa17b2a

[Regression potential]

Clean cherry-picks of already upstream (v6.1-rc7) fixes, impact a single
driver (amd-pstate) and the new mode (passive) is disabled by default.

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

** Affects: linux-oem-5.17 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Jammy)
 Importance: Undecided
 Status: Incomplete

** Affects: linux-oem-5.17 (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Kinetic)
 Importance: Undecided
 Status: Incomplete

** Affects: linux-oem-5.17 (Ubuntu Kinetic)
 Importance: Undecided
 Status: Invalid

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

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

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

** Changed in: linux-oem-5.17 (Ubuntu Kinetic)
   Status: New => Invalid

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

Title:
  Fix AMD-PState driver for Genoa CPU

Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.17 package in Ubuntu:
  New
Status in linux source package in Jammy:
  Incomplete
Status in linux-oem-5.17 source package in Jammy:
  New
Status in linux source package in Kinetic:
  Incomplete
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  [Impact]

  During AMD Genoa development, the datacenter team identified
  performance regressions that were root caused in the amd-pstate
  driver. A first round of fixes already landed upstream (v6.1-rc7) in
  the amd-pstate driver, and should be backported to all the affected
  kernels.

  [Fix]

  Backport the upstream amd-pstate fixes:

  https://lore.kernel.org/linux-
  
pm/20221117073541.3350600-1-perry.y...@amd.com/T/#m4616d857ca472937d1e1d31131ddc3261fa17b2a

  [Regression potential]

  Clean cherry-picks of already upstream (v6.1-rc7) fixes, impact a
  single driver (amd-pstate) and the new mode (passive) is disabled by
  default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998106/+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 1994693] Re: Align annotations with master kernel

[Paolo Pisati]

** Description changed:

  [Issue]
  
- The linux-kvm wasn't using annotations from debian.master, and that
- induced a skew in important options between master and kvm.
+ linux-kvm wasn't using annotations from debian.master, and that induced a
+ skew in fundamental config options between main and kvm kernels.
  
  [Fix]
  
- Apply the attached series.
+ The attached series (broken down in pieces to ease review) make linux-kvm use
+ annotations from debian.master and override options that are meant to be
+ different.
+ 
+ Must be applied on top of "[SRU][KINETIC linux-kvm][PATCH] UBUNTU: [Config]
+ Update SQUASHFS configs" already posted on the mailing list.
  
  [How to test]
  
- Crank updateconfigs shouldn't report any check-config error.
+ Crank updateconfigs shouldn't report any check-config error afterward.
+ 
+ [Regression potential]
+ 
+ These five patches:
+ 
+   UBUNTU: [Config] align IMA config with debian.master
+   UBUNTU: [Config] align UBSAN config with debian.master
+   UBUNTU: [Config] disable X86_KERNEL_IBT
+   UBUNTU: [Config] align LSM_MMAP_MIN_ADDR with master
+   UBUNTU: [Config] align LSM with master
+ 
+ are the only changes in kvm config, everything else is annotations fix
+ up.

** Summary changed:

- Align annotations with master kernel
+ linux-kvm: use annotations from debian.master

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

Title:
  linux-kvm: use annotations from debian.master

Status in linux-kvm package in Ubuntu:
  New
Status in linux-kvm source package in Kinetic:
  New

Bug description:
  [Issue]

  linux-kvm wasn't using annotations from debian.master, and that induced a
  skew in fundamental config options between main and kvm kernels.

  [Fix]

  The attached series (broken down in pieces to ease review) make linux-kvm use
  annotations from debian.master and override options that are meant to be
  different.

  Must be applied on top of "[SRU][KINETIC linux-kvm][PATCH] UBUNTU: [Config]
  Update SQUASHFS configs" already posted on the mailing list.

  [How to test]

  Crank updateconfigs shouldn't report any check-config error afterward.

  [Regression potential]

  These five patches:

UBUNTU: [Config] align IMA config with debian.master
UBUNTU: [Config] align UBSAN config with debian.master
UBUNTU: [Config] disable X86_KERNEL_IBT
UBUNTU: [Config] align LSM_MMAP_MIN_ADDR with master
UBUNTU: [Config] align LSM with master

  are the only changes in kvm config, everything else is annotations fix
  up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1994693/+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 1994693] [NEW] Align annotations with master kernel

[Paolo Pisati]

Public bug reported:

[Issue]

The linux-kvm wasn't using annotations from debian.master, and that
induced a skew in important options between master and kvm.

[Fix]

Apply the attached series.

[How to test]

Crank updateconfigs shouldn't report any check-config error.

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

** Affects: linux-kvm (Ubuntu Kinetic)
 Importance: Undecided
 Status: New

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

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

Title:
  Align annotations with master kernel

Status in linux-kvm package in Ubuntu:
  New
Status in linux-kvm source package in Kinetic:
  New

Bug description:
  [Issue]

  The linux-kvm wasn't using annotations from debian.master, and that
  induced a skew in important options between master and kvm.

  [Fix]

  Apply the attached series.

  [How to test]

  Crank updateconfigs shouldn't report any check-config error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1994693/+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 1990851] Re: Unable to boot 5.19.0-18 with modeset

[Paolo Pisati]

Could you test this kernel - 5.19.0-19.19+i915fix - and report if it
fixes your issue?

https://kernel.ubuntu.com/~arighi/lp-1991703/

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

Title:
  Unable to boot 5.19.0-18 with modeset

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to `linux-image-5.19.0-18-generic`, system seems freeze
  during the boot.

  Boot to earlier 5.19 kernel, looks fine.

  And 5.19.0-18 with `nomodeset` also works.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-18-generic 5.19.0-18.18
  ProcVersionSignature: Ubuntu 5.19.0-18.18-generic 5.19.7
  Uname: Linux 5.19.0-18-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm2004 F pipewire
    gdm2008 F wireplumber
   /dev/snd/controlC0:  gdm2008 F wireplumber
  CasperMD5CheckResult: unknown
  Date: Mon Sep 26 21:25:44 2022
  MachineType: LENOVO 82TF
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-18-generic 
root=/dev/mapper/vgroot-lvroot ro recovery nomodeset dis_ucode_ldr
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-18-generic N/A
   linux-backports-modules-5.19.0-18-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to kinetic on 2022-09-07 (19 days ago)
  dmi.bios.date: 06/16/2022
  dmi.bios.release: 1.39
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JYCN39WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76479WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y9000X IAH7
  dmi.ec.firmware.release: 1.39
  dmi.modalias: 
dmi:bvnLENOVO:bvrJYCN39WW:bd06/16/2022:br1.39:efr1.39:svnLENOVO:pn82TF:pvrLegionY9000XIAH7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrLegionY9000XIAH7:skuLENOVO_MT_82TF_BU_idea_FM_LegionY9000XIAH7:
  dmi.product.family: Legion Y9000X IAH7
  dmi.product.name: 82TF
  dmi.product.sku: LENOVO_MT_82TF_BU_idea_FM_Legion Y9000X IAH7
  dmi.product.version: Legion Y9000X IAH7
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990851/+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 1991704] Re: Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen

[Paolo Pisati]

Could you test this kernel - 5.19.0-19.19+i915fix - and report if it
fixes your issue?

https://kernel.ubuntu.com/~arighi/lp-1991703/

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

Title:
  Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen

Status in linux package in Ubuntu:
  Triaged

Bug description:
  After today's Kinetic update my Framework laptop won't boot.

  The boot hangs after this output:

  [0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci 
:00:07.1: DPC: RP PIO log size 8 is invalid
  [0.815754] pci :00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci 
:00:07.3: DPC: RP PIO log size 0 is invalid
  [2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst
  ead

  Falling back to 5.19.0-15-generic works.

  My Thinkpad X1 Carbon 6th gen does not have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-15-generic 5.19.0-15.15
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jik4014 F wireplumber
   /dev/snd/seq:jik4009 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  4 13:55:09 2022
  InstallationDate: Installed on 2022-09-17 (16 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Framework Laptop (12th Gen Intel Core)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-15-generic N/A
   linux-backports-modules-5.19.0-15-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago)
  dmi.bios.date: 07/15/2022
  dmi.bios.release: 3.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.04
  dmi.board.asset.tag: *
  dmi.board.name: FRANMACP04
  dmi.board.vendor: Framework
  dmi.board.version: A4
  dmi.chassis.asset.tag: FRANDACPA423350021
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A4
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04:
  dmi.product.family: 13in Laptop
  dmi.product.name: Laptop (12th Gen Intel Core)
  dmi.product.sku: FRANDACP04
  dmi.product.version: A4
  dmi.sys.vendor: Framework

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+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 1987869] Re: Remove linux-oem-5.17 from kinetic

[Paolo Pisati]

According to excuses[1], linux is blocked on nvidia-* drivers, and
nvidia-* are blocked on linux-oem-5.17 and linux-iotg[2] - we first need
to "unblock" oem-5.17 and iotg if we want oem-22.04 metapackages to
promote.

1: https://people.canonical.com/~ubuntu-archive/proposed-
migration/update_excuses.html#nvidia-graphics-drivers-510

2: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-
signatures-intel-iotg/+bug/1987870

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

Title:
  Remove linux-oem-5.17 from kinetic

Status in linux-meta-oem-5.17 package in Ubuntu:
  Incomplete
Status in linux-oem-5.17 package in Ubuntu:
  Triaged
Status in linux-restricted-modules-oem-5.17 package in Ubuntu:
  Triaged
Status in linux-restricted-signatures-oem-5.17 package in Ubuntu:
  Triaged
Status in linux-signed-oem-5.17 package in Ubuntu:
  Triaged

Bug description:
  Remove linux-oem-5.17 from kinetic

  this kernel should not exist in kinetic-release, as it is jammy-only
  thing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-5.17/+bug/1987869/+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 1983357] Re: test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 AMD64

[Paolo Pisati]

Some instances, show the same issue with test_021_aslr_dapper_mmap

FAIL: test_021_aslr_dapper_mmap (__main__.KernelSecurityTest)
ASLR of mmap

Traceback (most recent call last):
File "./test-kernel-security.py", line 1755, in test_021_aslr_dapper_mmap
  self._test_aslr('mmap', expected)
File "./test-kernel-security.py", line 1727, in _test_aslr
  self._test_aslr_all(area, expected, "default %s" % area)
File "./test-kernel-security.py", line 1720, in _test_aslr_all
  self._test_aslr_exec(area, expected, target, name)
File "./test-kernel-security.py", line 1703, in _test_aslr_exec
  self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area, 
"--verbose"], msg="%s:\n" % name)
File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1203, in assertShellExitEquals
  self.assertEqual(expected, rc, msg + result + report)
AssertionError: default mmap COMPAT:
Got exit code 1, expected 0
Command: './aslr32', 'mmap', '--verbose'
Output:
Checking ASLR of mmap:
  0xf7aff010
  0xf7aff010
  0xf7aff010
ASLR not functional (mmap always at 0xf7aff010)

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

Title:
  test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on
  K-5.19 AMD64

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Kinetic:
  Incomplete

Bug description:
  Issue found on 5.19.0-9.9 Kinetic AMD64 systems

  Test log:
   Running test: './test-kernel-security.py' distro: 'Ubuntu 22.10' kernel: 
'5.19.0-9.9 (Ubuntu 5.19.0-9.9-generic 5.19.0-rc5)' arch: 'amd64' uid: 0/0 
SUDO_USER: 'ubuntu')
   test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
   ASLR of libs ... (default libs native) (default libs native rekey) (default 
libs COMPAT) FAIL
   
   ==
   FAIL: test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
   ASLR of libs
   --
   Traceback (most recent call last):
 File "./test-kernel-security.py", line 1770, in test_021_aslr_dapper_libs
   self._test_aslr('libs', expected)
 File "./test-kernel-security.py", line 1727, in _test_aslr
   self._test_aslr_all(area, expected, "default %s" % area)
 File "./test-kernel-security.py", line 1720, in _test_aslr_all
   self._test_aslr_exec(area, expected, target, name)
 File "./test-kernel-security.py", line 1703, in _test_aslr_exec
   self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area, 
"--verbose"], msg="%s:\n" % name)
 File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1203, in assertShellExitEquals
   self.assertEqual(expected, rc, msg + result + report)
   AssertionError: default libs COMPAT:
   Got exit code 1, expected 0
   Command: './aslr32', 'libs', '--verbose'
   Output:
   Checking ASLR of libs:
   0xf7c81790
   0xf7c81790
   0xf7c81790
   FAIL: ASLR not functional (libs always at 0xf7c81790)
   
   
   --
   Ran 1 test in 0.144s
   
   FAILED (failures=1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1983357/+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 1977721] [NEW] Jammy update: v5.17.13 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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


Linux 5.17.13
ALSA: usb-audio: Optimize TEAC clock quirk
bpf: Check PTR_TO_MEM | MEM_RDONLY in check_helper_mem_access
bpf: Reject writes for PTR_TO_MAP_KEY in check_helper_mem_access
bpf: Fix excessive memory allocation in stack_map_alloc()
bpf: Fix usage of trace RCU in local storage.
bpf: Enlarge offset check value to INT_MAX in bpf_skb_{load,store}_bytes
bpf: Fix combination of jit blinding and pointers to bpf subprogs.
bpf: Fix potential array overflow in bpf_trampoline_get_progs()
NFSD: Fix possible sleep during nfsd4_release_lockowner()
NFS: Memory allocation failures are not server fatal errors
docs: submitting-patches: Fix crossref to 'The canonical patch format'
tpm: ibmvtpm: Correct the return value in tpm_ibmvtpm_probe()
tpm: Fix buffer access in tpm2_get_tpm_pt()
media: i2c: imx412: Fix power_off ordering
media: i2c: imx412: Fix reset GPIO polarity
x86/sgx: Ensure no data in PCMD page after truncate
x86/sgx: Fix race between reclaimer and page fault handler
x86/sgx: Obtain backing storage page with enclave mutex held
x86/sgx: Mark PCMD page as dirty when modifying contents
x86/sgx: Disconnect backing page references from dirty status
HID: multitouch: add quirks to enable Lenovo X12 trackpoint
HID: multitouch: Add support for Google Whiskers Touchpad
fs/ntfs3: validate BOOT sectors_per_clusters
raid5: introduce MD_BROKEN
dm verity: set DM_TARGET_IMMUTABLE feature flag
dm stats: add cond_resched when looping over entries
dm crypt: make printing of the key constant-time
dm integrity: fix error code in dm_integrity_ctr()
ARM: dts: s5pv210: Correct interrupt name for bluetooth in Aries
Bluetooth: hci_qca: Use del_timer_sync() before freeing
ALSA: usb-audio: Configure sync endpoints before data
ALSA: usb-audio: Add missing ep_idx in fixed EP quirks
ALSA: usb-audio: Workaround for clock setup on TEAC devices
tools/memory-model/README: Update klitmus7 compat table
zsmalloc: fix races between asynchronous zspage free and page migration
crypto: ecrdsa - Fix incorrect use of vli_cmp
crypto: caam - fix i.MX6SX entropy delay value
KVM: SVM: Use kzalloc for sev ioctl interfaces to prevent kernel data leak
KVM: x86/mmu: Don't rebuild page when the page is synced and no tlb flushing is 
required
KVM: x86: Drop WARNs that assert a triple fault never "escapes" from L2
KVM: x86: Fix the intel_pt PMI handling wrongly considered from guest
KVM: x86: avoid loading a vCPU after .vm_destroy was called
KVM: x86: avoid calling x86 emulator without a decoded instruction
KVM: x86: fix typo in __try_cmpxchg_user causing non-atomicness
KVM: x86: Use __try_cmpxchg_user() to emulate atomic accesses
KVM: x86: Use __try_cmpxchg_user() to update guest PTE A/D bits
x86/uaccess: Implement macros for CMPXCHG on user addresses
x86, kvm: use correct GFP flags for preemption disabled
x86/kvm: Alloc dummy async #PF token outside of raw spinlock
x86/fpu: KVM: Set the base guest FPU uABI size to sizeof(struct kvm_xsave)
KVM: PPC: Book3S HV: fix incorrect NULL check on list iterator
netfilter: conntrack: re-fetch conntrack after insertion
netfilter: nf_tables: double hook unregistration in netns path
netfilter: nf_tables: hold mutex on netns pre_exit path
netfilter: nf_tables: sanitize nft_set_desc_concat_parse()
netfilter: nft_limit: Clone packet limits' cost value
exfat: check if cluster num is valid
drm/i915: Fix -Wstringop-overflow warning in call to intel_read_wm_latency()
net: ipa: compute proper aggregation limit
pipe: Fix missing lock in pipe_resize_ring()
pipe: make poll_usage boolean and annotate its access
assoc_array: Fix BUG_ON during garbage collect
i2c: ismt: prevent memory corruption in ismt_access()
netfilter: nf_tables: disallow non-stateful expression in sets earlier
drivers: i2c: thunderx: Allow driver to work with ACPI defined TWSI controllers
i2c: ismt: Provide a DMA buffer for Interrupt Cause Logging
net: ftgmac100: Disable hardware checksum on AST2600
nfc: pn533: Fix buggy cleanup order
net: af_key: check encryption module availability consistency
percpu_ref_init(): clean ->percpu_count_ref on failure
KVM: arm64: Don't hypercall before EL2 init
pinctrl: sunxi: fix f1c100s uart2 function
ALSA: hda/realtek: Add quirk for the Framework Laptop
ALSA: hda/realtek: Add quirk for Dell Latitude 7520
ALSA: usb-audio: Don't get sample rate for MCT Trigger 5 USB-to-HDMI

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

** Affects: linux 

[Kernel-packages] [Bug 1976470] [NEW] Jammy update: v5.17.12 upstream stable release

[Paolo Pisati]

Public bug reported:


SRU Justification

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

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


Linux 5.17.12
ALSA: ctxfi: Add SB046x PCI ID
ACPI: sysfs: Fix BERT error region memory mapping
random: check for signals after page of pool writes
random: wire up fops->splice_{read,write}_iter()
random: convert to using fops->write_iter()
random: convert to using fops->read_iter()
random: unify batched entropy implementations
random: move randomize_page() into mm where it belongs
random: move initialization functions out of hot pages
random: make consistent use of buf and len
random: use proper return types on get_random_{int,long}_wait()
random: remove extern from functions in header
random: use static branch for crng_ready()
random: credit architectural init the exact amount
random: handle latent entropy and command line from random_init()
random: use proper jiffies comparison macro
random: remove ratelimiting for in-kernel unseeded randomness
random: move initialization out of reseeding hot path
random: avoid initializing twice in credit race
random: use symbolic constants for crng_init states
siphash: use one source of truth for siphash permutations
random: help compiler out with fast_mix() by using simpler arguments
random: do not use input pool from hard IRQs
random: order timer entropy functions below interrupt functions
random: do not pretend to handle premature next security model
random: use first 128 bits of input as fast init
random: do not use batches when !crng_ready()
random: insist on random_get_entropy() existing in order to simplify
xtensa: use fallback for random_get_entropy() instead of zero
sparc: use fallback for random_get_entropy() instead of zero
um: use fallback for random_get_entropy() instead of zero
x86/tsc: Use fallback for random_get_entropy() instead of zero
nios2: use fallback for random_get_entropy() instead of zero
arm: use fallback for random_get_entropy() instead of zero
mips: use fallback for random_get_entropy() instead of just c0 random
riscv: use fallback for random_get_entropy() instead of zero
m68k: use fallback for random_get_entropy() instead of zero
timekeeping: Add raw clock fallback for random_get_entropy()
powerpc: define get_cycles macro for arch-override
alpha: define get_cycles macro for arch-override
parisc: define get_cycles macro for arch-override
s390: define get_cycles macro for arch-override
ia64: define get_cycles macro for arch-override
init: call time_init() before rand_initialize()
random: fix sysctl documentation nits
random: document crng_fast_key_erasure() destination possibility
random: make random_get_entropy() return an unsigned long
random: allow partial reads if later user copies fail
random: check for signals every PAGE_SIZE chunk of /dev/[u]random
random: check for signal_pending() outside of need_resched() check
random: do not allow user to keep crng key around on stack
random: do not split fast init input in add_hwgenerator_randomness()
random: mix build-time latent entropy into pool at init
random: re-add removed comment about get_random_{u32,u64} reseeding
random: treat bootloader trust toggle the same way as cpu trust toggle
random: skip fast_init if hwrng provides large chunk of entropy
random: check for signal and try earlier when generating entropy
random: reseed more often immediately after booting
random: make consistent usage of crng_ready()
random: use SipHash as interrupt entropy accumulator
random: replace custom notifier chain with standard one
random: don't let 644 read-only sysctls be written to
random: give sysctl_random_min_urandom_seed a more sensible value
random: do crng pre-init loading in worker rather than irq
random: unify cycles_t and jiffies usage and types
random: cleanup UUID handling
random: only wake up writers after zap if threshold was passed
random: round-robin registers as ulong, not u32
random: clear fast pool, crng, and batches in cpuhp bring up
random: pull add_hwgenerator_randomness() declaration into random.h
random: check for crng_init == 0 in add_device_randomness()
random: unify early init crng load accounting
random: do not take pool spinlock at boot
random: defer fast pool mixing to worker
random: rewrite header introductory comment
random: group sysctl functions
random: group userspace read/write functions
random: group entropy collection functions
random: group entropy extraction functions
random: group crng functions
random: group initialization wait functions
random: remove whitespace and reorder includes
random: remove useless