[Kernel-packages] [Bug 2064561] [NEW] Focal update: v5.4.273 upstream stable release
OMAIN instead of depending on it
serial: 8250_exar: Don't remove GPIO device on suspend
staging: greybus: fix get_channel_from_mode() failure path
usb: gadget: net2272: Use irqflags in the call to net2272_probe_fin
octeontx2-af: Use matching wake_up API variant in CGX command interface
s390/vtime: fix average steal time calculation
hsr: Fix uninit-value access in hsr_get_node()
packet: annotate data-races around ignore_outgoing
rds: introduce acquire/release ordering in acquire/release_in_xmit()
hsr: Handle failures in module init
net/bnx2x: Prevent access to a freed page in page_pool
octeontx2-af: Use separate handlers for interrupts
ARM: dts: sun8i-h2-plus-bananapi-m2-zero: add regulator nodes vcc-dram and
vcc1v2
netfilter: nf_tables: do not compare internal table flags on updates
rcu: add a helper to report consolidated flavor QS
bpf: report RCU QS in cpumap kthread
spi: spi-mt65xx: Fix NULL pointer access in interrupt handler
regmap: Add missing map->bus check
Linux 5.4.273
UBUNTU: Upstream stable to v5.4.273
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Focal)
Importance: Medium
Assignee: Portia Stephens (portias)
Status: In Progress
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Portia Stephens (portias)
** Description changed:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.4.273 upstream stable release
from git://git.kernel.org/
-
+ io_uring/unix: drop usage of io_uring socket
+ io_uring: drop any code related to SCM_RIGHTS
+ selftests: tls: use exact comparison in recv_partial
+ ASoC: rt5645: Make LattePanda board DMI match more precise
+ x86/xen: Add some null pointer checking to smp.c
+ MIPS: Clear Cause.BD in instruction_pointer_set
+ HID: multitouch: Add required quirk for Synaptics 0xcddc device
+ RDMA/mlx5: Relax DEVX access upon modify commands
+ net/iucv: fix the allocation size of iucv_path_table array
+ parisc/ftrace: add missing CONFIG_DYNAMIC_FTRACE check
+ block: sed-opal: handle empty atoms when parsing response
+ dm-verity, dm-crypt: align "struct bvec_iter" correctly
+ btrfs: fix data race at btrfs_use_block_rsv() when accessing block reserve
+ scsi: mpt3sas: Prevent sending diag_reset when the controller is ready
+ Bluetooth: rfcomm: Fix null-ptr-deref in rfcomm_check_security
+ firewire: core: use long bus reset on gap count error
+ ASoC: Intel: bytcr_rt5640: Add an extra entry for the Chuwi Vi8 tablet
+ Input: gpio_keys_polled - suppress deferred probe error for gpio
+ ASoC: wm8962: Enable oscillator if selecting WM8962_FLL_OSC
+ ASoC: wm8962: Enable both SPKOUTR_ENA and SPKOUTL_ENA in mono mode
+ ASoC: wm8962: Fix up incorrect error message in wm8962_set_fll
+ do_sys_name_to_handle(): use kzalloc() to fix kernel-infoleak
+ fs/select: rework stack allocation hack for clang
+ aoe: fix the potential use-after-free problem in aoecmd_cfg_pkts
+ timekeeping: Fix cross-timestamp interpolation on counter wrap
+ timekeeping: Fix cross-timestamp interpolation corner case decision
+ timekeeping: Fix cross-timestamp interpolation for non-x86
+ wifi: ath10k: fix NULL pointer dereference in
ath10k_wmi_tlv_op_pull_mgmt_tx_compl_ev()
+ b43: dma: Fix use true/false for bool type variable
+ wifi: b43: Stop/wake correct queue in DMA Tx path when QoS is disabled
+ wifi: b43: Stop/wake correct queue in PIO Tx path when QoS is disabled
+ b43: main: Fix use true/false for bool type
+ wifi: b43: Stop correct queue in DMA worker when QoS is disabled
+ wifi: b43: Disable QoS for bcm4331
+ wifi: wilc1000: fix declarations ordering
+ wifi: wilc1000: fix RCU usage in connect path
+ wifi: mwifiex: debugfs: Drop unnecessary error check for debugfs_create_dir()
+ sock_diag: annotate data-races around sock_diag_handlers[family]
+ af_unix: Annotate data-race of gc_in_progress in wait_for_unix_gc().
+ net: blackhole_dev: fix build warning for ethh set but not used
+ wifi: libertas: fix some memleaks in lbs_allocate_cmd_buffer()
+ arm64: dts: mediatek: mt7622: add missing "device_type" to memory node
[Kernel-packages] [Bug 2064555] [NEW] Focal update: v5.4.272 upstream stable release
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.4.272 upstream stable release
from git://git.kernel.org/
lan78xx: Fix white space and style issues
lan78xx: Add missing return code checks
lan78xx: Fix partial packet errors on suspend/resume
lan78xx: Fix race conditions in suspend/resume handling
net: lan78xx: fix runtime PM count underflow on link stop
ixgbe: {dis, en}able irqs in ixgbe_txrx_ring_{dis, en}able
geneve: make sure to pull inner header in geneve_rx()
net: ice: Fix potential NULL pointer dereference in ice_bridge_setlink()
net/ipv6: avoid possible UAF in ip6_route_mpath_notify()
net/rds: fix WARNING in rds_conn_connect_if_down
netfilter: nft_ct: fix l3num expectations with inet pseudo family
netfilter: nf_conntrack_h323: Add protection for bmp length out of range
netrom: Fix a data-race around sysctl_netrom_default_path_quality
netrom: Fix a data-race around sysctl_netrom_obsolescence_count_initialiser
netrom: Fix data-races around sysctl_netrom_network_ttl_initialiser
netrom: Fix a data-race around sysctl_netrom_transport_timeout
netrom: Fix a data-race around sysctl_netrom_transport_maximum_tries
netrom: Fix a data-race around sysctl_netrom_transport_acknowledge_delay
netrom: Fix a data-race around sysctl_netrom_transport_busy_delay
netrom: Fix a data-race around sysctl_netrom_transport_requested_window_size
netrom: Fix a data-race around sysctl_netrom_transport_no_activity_timeout
netrom: Fix a data-race around sysctl_netrom_routing_control
netrom: Fix a data-race around sysctl_netrom_link_fails_count
netrom: Fix data-races around sysctl_net_busy_read
selftests: mm: fix map_hugetlb failure on 64K page size systems
um: allow not setting extra rpaths in the linux binary
serial: max310x: Use devm_clk_get_optional() to get the input clock
serial: max310x: Try to get crystal clock rate from property
serial: max310x: fail probe if clock crystal is unstable
serial: max310x: Make use of device properties
serial: max310x: use regmap methods for SPI batch operations
serial: max310x: use a separate regmap for each port
serial: max310x: prevent infinite while() loop in port startup
Input: i8042 - fix strange behavior of touchpad on Clevo NS70PU
hv_netvsc: Make netvsc/VF binding check both MAC and serial number
hv_netvsc: use netif_is_bond_master() instead of open code
hv_netvsc: Register VF in netvsc_probe if NET_DEVICE_REGISTER missed
y2038: rusage: use __kernel_old_timeval
getrusage: add the "signal_struct *sig" local variable
getrusage: move thread_group_cputime_adjusted() outside of lock_task_sighand()
getrusage: use __for_each_thread()
getrusage: use sig->stats_lock rather than lock_task_sighand()
serial: max310x: Unprepare and disable clock in error path
regmap: allow to define reg_update_bits for no bus configuration
regmap: Add bulk read/write callbacks into regmap_config
serial: max310x: make accessing revision id interface-agnostic
serial: max310x: implement I2C support
serial: max310x: fix IO data corruption in batched operations
arm64: dts: qcom: add PDC interrupt controller for SDM845
arm64: dts: qcom: sdm845: fix USB DP/DM HS PHY interrupts
Linux 5.4.272
UBUNTU: Upstream stable to v5.4.272
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Focal)
Importance: Medium
Assignee: Portia Stephens (portias)
Status: In Progress
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Portia Stephens (portias)
** Description changed:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.4.272 upstream stable release
from git://git.kernel.org/
-
+ lan78xx: Fix white spac
[Kernel-packages] [Bug 2055241] Re: Update on-chip oscillator clock nodes for Kria
@Sagar - thanks, I've updated the tags. In the future, "If the problem is solved, change the tag 'verification-needed-jammy-linux-xilinx- zynqmp' to 'verification-done-jammy-linux-xilinx-zynqmp'." -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2055241 Title: Update on-chip oscillator clock nodes for Kria Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Jammy: Fix Committed Bug description: [ Impact ] * This models on-chip oscillator clock nodes in KV/KR/KD board device trees built for Xilinx products to be in sync with the corresponding board schematic * Currently a few clocks were not modelled which are planned to be included now. * Most clocks in board device trees are currently included so this should have minimal size impact. * The correct and cleanest approach is to model clock sources in Xilinx's application dtsi's in order to reference these clock nodes from the board device tree rather than having duplicated nodes in application overlay dtbo's [ Test Plan ] * Normal certification will test that the device tree changes did not introduce a regression on any certified platform. * Xilinx will verify they can load the dtbo's for the FPGA during runtime [ Where problems could occur ] * There could be an unexpected impact since there are discrepancies between some revA vs revB board device trees, all clock nodes not being modelled to be in sync with board schematics [ Other Info ] * Changes are pulled from Xilinx' 6.6 tree https://github.com/Xilinx/linux-xlnx/commit/bd1a7261325afa7526ed12fbaeb8f2e939bd02f8 https://github.com/Xilinx/linux-xlnx/commit/d9d492b32494611dbcc422d9f365a59df20c69b1 https://github.com/Xilinx/linux-xlnx/commit/a0fe3083d290f8507922a68daa60cb92d76d56b2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2055241/+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 2058321] Re: Unsupported platform 'ZynqMP KV260 revB
** Tags removed: verification-needed-jammy-linux-xilinx-zynqmp ** Tags added: verification-done-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2058321 Title: Unsupported platform 'ZynqMP KV260 revB Status in linux-xilinx-zynqmp package in Ubuntu: Invalid Status in linux-xilinx-zynqmp source package in Jammy: Fix Committed Bug description: [ Impact ] * flash-kernel uses the model string in the kernel's device tree to determine what platform is running. Thus there is a dependency between the two packages * A change in the model string for KR platforms was made to support rev B (LP #2046280) which breaks older versions of flash-kernel. [ Test Plan ] * Kernel regression testing uses flash-kernel and will test this change * certification testing uses flash-kernel and will test this change [ Where problems could occur ] * This will cause flash-kernel to be updated automatically when the kernel is updated . This may introduce other issues caused by previous flash-kernel changes that users were not running [ Other info ] * flash-kernel SRU https://bugs.launchpad.net/ubuntu/+source/flash- kernel/+bug/2054556 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2058321/+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 2055241] Re: Update on-chip oscillator clock nodes for Kria
** Tags removed: verification-needed-jammy-linux-xilinx-zynqmp ** Tags added: verification-done-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2055241 Title: Update on-chip oscillator clock nodes for Kria Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Jammy: Fix Committed Bug description: [ Impact ] * This models on-chip oscillator clock nodes in KV/KR/KD board device trees built for Xilinx products to be in sync with the corresponding board schematic * Currently a few clocks were not modelled which are planned to be included now. * Most clocks in board device trees are currently included so this should have minimal size impact. * The correct and cleanest approach is to model clock sources in Xilinx's application dtsi's in order to reference these clock nodes from the board device tree rather than having duplicated nodes in application overlay dtbo's [ Test Plan ] * Normal certification will test that the device tree changes did not introduce a regression on any certified platform. * Xilinx will verify they can load the dtbo's for the FPGA during runtime [ Where problems could occur ] * There could be an unexpected impact since there are discrepancies between some revA vs revB board device trees, all clock nodes not being modelled to be in sync with board schematics [ Other Info ] * Changes are pulled from Xilinx' 6.6 tree https://github.com/Xilinx/linux-xlnx/commit/bd1a7261325afa7526ed12fbaeb8f2e939bd02f8 https://github.com/Xilinx/linux-xlnx/commit/d9d492b32494611dbcc422d9f365a59df20c69b1 https://github.com/Xilinx/linux-xlnx/commit/a0fe3083d290f8507922a68daa60cb92d76d56b2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2055241/+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 2058707] Re: Backport AXI 1-wire host driver
** Tags removed: verification-needed-jammy-linux-xilinx-zynqmp ** Tags added: verification-done-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2058707 Title: Backport AXI 1-wire host driver Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Jammy: Fix Committed Status in linux-xilinx-zynqmp source package in Noble: New Bug description: [ Impact ] * Backport AXI 1-wire host driver. * The driver is used to interface with FPGA IP logic. * The driver is only loaded when device tree overlay is applied on platforms that require the driver. [ Test Plan ] * Xilinx will test the functionality on a KD240 with an FPGA bitstream that has the required IP logic. [ Where problems could occur ] * We are unable to run certification testing with the driver loaded which creates a risk of breaking the driver in the future. [ Other info ] * Private LP bug: https://bugs.launchpad.net/limerick/+bug/2052477 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2058707/+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 1995465] Re: linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security.
** Changed in: linux-xilinx-zynqmp (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/1995465 Title: linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security. Status in linux-xilinx-zynqmp package in Ubuntu: Fix Released Status in linux-xilinx-zynqmp source package in Focal: Fix Released Bug description: [SRU Justification] [Impact] The linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security regression test due to kernel config options. The kernel configs were changed to match the Xilinx provided kernel configs which resulted in these configs being disabled. [Fix] Enable all configs checked in ubuntu_qrt_kernel_security. [Testcase] ubuntu_qrt_kernel caught this isuse and will continue to test whether these configs are enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/1995465/+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 1992912] Re: linux-xilinx-zynqmp/focal: main(): sched_setscheduler(): Operation not permitted
** Changed in: linux-xilinx-zynqmp (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/1992912 Title: linux-xilinx-zynqmp/focal: main(): sched_setscheduler(): Operation not permitted Status in ubuntu-kernel-tests: New Status in linux-xilinx-zynqmp package in Ubuntu: Fix Released Status in linux-xilinx-zynqmp source package in Focal: Fix Committed Bug description: [SRU Justification] [Impact] The focal kernel is failing the ubuntu_ltp:sched:time-schedule01, ubuntu_ltp:sched:trace_sched01 and ubuntu_ltp:irq:irqbalance0 regression test due to sched_setscheduler being unable to a task class to SCHED_FIFO. This is due to have having CONFIG_RT_GROUP_SCHED enabled. Once RT_GROUP_SCHED is enabled it is impossible to schedule realtime tasks for non-root users until you allocate realtime bandwidth for them. There are multiple known issues with CONFIG_RT_GROUP_SCHED that are reported in the debian.master/config/annotations file: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284731 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873315 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665 [Fix] CONFIG_RT_GROUP_SCHED should be disabled. The config was enabled when we copied the Xilinx default config settings and there is not a justification for this exact config. There may even be a negative impact, from the kernel.org documentation: “The default values for sched_rt_period_us (100 or 1s) and sched_rt_runtime_us (95 or 0.95s). This gives 0.05s to be used by SCHED_OTHER (non-RT tasks).” This suggests this option will benefit RT systems, but be detrimental to non-RT systems, [Testcase] The annotations file will enforce that CONFIG_RT_GROUP_SCHED is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1992912/+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 2055237] Re: Backport ps uart RS485 driver
** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2055237 Title: Backport ps uart RS485 driver Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Jammy: Incomplete Status in linux-xilinx-zynqmp source package in Noble: New Bug description: [ Impact ] * Backports support for rs485 to the uartps driver from the tty staging tree [ Test Plan ] * Testing is needed to ensure this doesn't break the serial console on current platforms. QA will develop a new automated test to be integrated into cert testing * Testing of the RS485 port will be integrated into the cert testing for the KD240 [ Where problems could occur ] * The patches have not landed in mainline and are being pulled from the maintainers tree. There is a risk they will be rejected from mainline. [ Other info ] * The following 3 patches are required from the tty-dev tree. All other patches were pulled in to support the backport. 1. https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-next=32152467ffac3b79eae7313959c310946b0e6072 2. https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-next=74231ab6cc2d02303ddf1fabd878756c52f788a5 3. https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-next=fccc9d9233f918ee50cf2955ae7134a7f3418351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2055237/+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 2064179] [NEW] Forward port linux-xlnx 6.6 patches to Noble
Public bug reported: Xilinx vendor tree patches need to be forward ported from their 6.6 branch to 6.8 for Noble. https://github.com/Xilinx/linux-xlnx/tree/xlnx_rebase_v6.6 We cherry-picked every commit from a3ea85714695 "xilinx: Add a github template telling people to not use pull requests there" ^ .. 24eec56fe5bd "arm64: zynqmp: Remove arm,cortex-a53-edac node" Upstream work was done on net: axienet that Xilinx has reverted on 6.6 in order to apply their own changes. Xilinx squashed these reverts into one commit "Revert "net: axienet: Revert following mainline commits to be in sync with downstream implementation." There were additional patches that were added between 6.6 and 6.8 that we also reverted. We removed the squashed revert and individually reverted the patches to make maintenance easier. The following commits were reverted: 67f10a9bef6c Revert "net: axienet: make use of axistream-connected attribute optional" 947a44219b1e Revert "net: axienet: Clean up DMA start/stop and error handling" 2fafbc9b412e Revert "net: axienet: implement NAPI and GRO receive" e5a7818b8d04 Revert "net: axienet: Use NAPI for TX completion path" de765a372712 Revert "net: axienet: Switch to 64-bit RX/TX statistics" 34311bc5920f Revert "net: ethernet: xilinx: Convert to platform remove callback returning void" 1f35754c5be3 Revert "net: axienet: Preparatory changes for dmaengine support" 1e3ba4732475 Revert "net: axienet: Introduce dmaengine support" 6e93b87de0ce Revert "net: axienet: Fix check for partial TX checksum" Upstream also added erase die capability to mtd: spi-nor which had major conflicts with stacked and parallel memory support added by Xilinx. These should be revisited once Xilinx upstreams the stacked and parallel memory support since this will make maintenance difficult. We reverted the following patches in mtd: spi-nor: ac2881fb1d4d Revert "mtd: spi-nor: add erase die (chip) capability" f044dd43a1b4 Revert "mtd: spi-nor: spansion: enable die erase for multi die flashes" c072086fdce3 Revert "mtd: spi-nor: micron-st: enable die erase for multi die flashes" 6be57acc37df Revert "mtd: spi-nor: remove NO_CHIP_ERASE flag" 6bbd61fc0eef Revert "mtd: spi-nor: micron-st: Add support for mt25qu01g" A few patches were skipped because we were just unsure how to apply them. We should go back and revisit these: usb: gadget: uvc_video: unlock before submitting a request to ep usb: gadget: webcam: Add support for Full HD and 4K UHD Raw Video v4l: xilinx: xcsi2rxss: Fix warnings for NULL_RETURNS In total of the 860 patches we tried to apply 121 were skipped because they had been upstreamed between v6.6 and v6.8. The kernel will use the Ubuntu configs with Xilinx' configs applied on top. To do this we imported the .config built on Xilinx tree for xilinx_zynqmp_defconfig. ** Affects: linux-xilinx-zynqmp (Ubuntu) Importance: Medium Assignee: Portia Stephens (portias) Status: In Progress ** Description changed: Xilinx vendor tree patches need to be forward ported from their 6.6 branch to 6.8 for Noble. https://github.com/Xilinx/linux-xlnx/tree/xlnx_rebase_v6.6 - We cherry-picked every commit from + We cherry-picked every commit from a3ea85714695 "xilinx: Add a github template telling people to not use pull requests there" ^ .. 24eec56fe5bd "arm64: zynqmp: Remove arm,cortex-a53-edac node" - - Upstream work was done on net: axienet that Xilinx has reverted on 6.6 in order to apply their own changes. There were additional patches that were added between 6.6 and 6.8 that we also reverted: + Upstream work was done on net: axienet that Xilinx has reverted on 6.6 + in order to apply their own changes. Xilinx squashed these reverts into + one commit "Revert "net: axienet: Revert following mainline commits to + be in sync with downstream implementation." There were additional + patches that were added between 6.6 and 6.8 that we also reverted. We + removed the squashed revert and individually reverted the patches to + make maintenance easier. The following commits were reverted: 67f10a9bef6c Revert "net: axienet: make use of axistream-connected attribute optional" 947a44219b1e Revert "net: axienet: Clean up DMA start/stop and error handling" 2fafbc9b412e Revert "net: axienet: implement NAPI and GRO receive" e5a7818b8d04 Revert "net: axienet: Use NAPI for TX completion path" de765a372712 Revert "net: axienet: Switch to 64-bit RX/TX statistics" 34311bc5920f Revert "net: ethernet: xilinx: Convert to platform remove callback returning void" 1f35754c5be3 Revert "net: axienet: Preparatory changes for dmaengine support" 1e3ba4732475 Revert "net: axienet: Introduce dmaengine suppo
[Kernel-packages] [Bug 2041782] Re: spi: spi-cadence-quadspi: Fix ospi resume failures conflicts
** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-xilinx-zynqmp (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2041782 Title: spi: spi-cadence-quadspi: Fix ospi resume failures conflicts Status in linux-xilinx-zynqmp package in Ubuntu: Invalid Status in linux-xilinx-zynqmp source package in Jammy: Invalid Bug description: jammy:xilinx-zynqmp is carrying a patch subject "spi: spi-cadence- quadspi: Fix ospi resume failure" from the Xilinx tree , branch xlnx_rebase_v5.15_LTS_2022.1_update . This commit hasn't been upstreamed and completely rewrites the function cqspi_resume(). A change has landed in the v5.15.111 upstream stable release which conflicts with this Xilinx patch in such a way that we don't know how to resolve the conflicts and keep the functionality intact. We have found where Xlinx resolved the merge on the XIlinx 6.1 branch but it doesn't seem correct. In the original commit: (https://github.com/Xilinx/linux- xlnx/commit/6edac18033db445439ca57c23b8cee29a6bbdf0f) in the function cqspi_resume() , the call to cqspi_controller_enable() is removed and ZynqMP specific controls are added. Upstream fixed an issue with suspend-resume (https://github.com/torvalds/linux/commit/2087e85bb66ee3652dafe732bb9b9b896229eafc). The upstream fix replaces the cqspi_controller_enable() with some clock initializations and a call to cqspi_controller_init() which does some register writes before calling cqspi_controller_enable(). Xilinx resolve the conflict by concatenating the two commit's changes to cqspi_resume() (https://github.com/Xilinx/linux-xlnx/blob/xlnx_rebase_v6.1_LTS_2023.1_update/drivers/spi/spi-cadence-quadspi.c#L2271), the end result is that cqspi_resume() consists of ZynqMP specific controls followed by a (nested) call to cqspi_controller_enable(), the exact function call that was removed in XIlinx's original commit. This bug is to track how this merge conflict is resolved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2041782/+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 1995465] Re: linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security.
** Changed in: linux-xilinx-zynqmp (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/1995465 Title: linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security. Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Focal: Fix Released Bug description: [SRU Justification] [Impact] The linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security regression test due to kernel config options. The kernel configs were changed to match the Xilinx provided kernel configs which resulted in these configs being disabled. [Fix] Enable all configs checked in ubuntu_qrt_kernel_security. [Testcase] ubuntu_qrt_kernel caught this isuse and will continue to test whether these configs are enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/1995465/+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 2040354] Re: Add K24 device tree
** Changed in: linux-xilinx-zynqmp (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2040354 Title: Add K24 device tree Status in linux-xilinx-zynqmp package in Ubuntu: Fix Released Status in linux-xilinx-zynqmp source package in Jammy: Fix Released Bug description: [ Impact ] * This ports the K24 device trees from the Xilinx 6.1 kernel (xlnx_rebase_v6.1_LTS_2023.1_update) * This will allow the same image.its file and thus flash-kernel package to be used for the K24 development images and the stable release. [ Test Plan ] * The k24 platform does not need to be tested since it is not a certified platform. The normal regression testing on K26 and ZCU platforms is sufficient. [ Where problems could occur ] * A bug in the device tree could cause a build error in the kernel. The device tree is not used by any certified images. [ Other Info ] The change squashes together the following changes from Xilinx xlnx_rebase_v6.1_LTS_2023.1_update branch. Patches that modified device tree other than: arch/arm64/boot/dts/xilinx/zynqmp-sck-kd-g-revA.dts arch/arm64/boot/dts/xilinx/zynqmp-sm-k24-revA.dts arch/arm64/boot/dts/xilinx/zynqmp-smk-k24-revA.dts were modified to remove the other changes. a89bdb9e6f1f arm64: zynqmp: Add/Update/Sync DTs for xilinx platforms f1fe53d988d8 arm64: zynqmp: Update ADI PHY properties for KD240 f660fc7bba89 arm64: zynqmp: Use MIO 77 for ADI PHY reset on KD240 41a6b53e0691 arm64: zynqmp: Fill model name for SOM CCs 958f20d8445e arm64: zynqmp: Fix memory size on k24 c3cc27055c19 arm64: zynqmp: Wire can0 on kd240-revA 9da2d3e73b17 arm64: zynqmp: Configure gem1 rx pins on kd240 board 646a2dfaaaf8 arm64: zynqmp: Cover K24/KD240 revB/1 boards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2040354/+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 2044554] Re: Turn off non-zynqmp arch support
** Also affects: linux-xilinx-zynqmp (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux-xilinx-zynqmp (Ubuntu Noble) Assignee: (unassigned) => Portia Stephens (portias) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2044554 Title: Turn off non-zynqmp arch support Status in linux-xilinx-zynqmp package in Ubuntu: Fix Committed Status in linux-xilinx-zynqmp source package in Jammy: Fix Released Status in linux-xilinx-zynqmp source package in Noble: New Bug description: [ Impact ] * This is an optimized kernel for zynqmp range of devices. * Currently about 14% of kernel build is targeting non-zynqmp devices, which is dead code unused in production * This reduces kernel build time, kernel image & modules size, amount of required firmware, and makes initrd smaller. * This reduces peak memory usage on boot as well * This will loose ability to execute this exact same kernel build on non-zynqmp device, for benchmarking purposes generic kernel should be used instead. [ Test Plan ] * Ensure newly produced kernel installs and boots on Ubuntu Server and Ubuntu Core target devices without any loss of peripherals and stock devices. [ Where problems could occur ] * This changes may limit ability to smoke-test this kernel on non-zynqmp devices, if needed support for individual CPUs can be turned back on. Or ideally any such testing should move to zynqmp devices. (examples of potentially interesting things to turn back on upon request are QCOM APPLE suppport for running this kernel on Arm Laptops for developer convenience) * It is expected for KVM and QEMU to continue to work as both host and guest [ Other Info ] * Anything else you think is useful to include * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board * and address these questions in advance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2044554/+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 2049442] Re: Enable symbols for all Xilinx device trees
** Changed in: linux-xilinx-zynqmp (Ubuntu Noble) Assignee: (unassigned) => Portia Stephens (portias) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2049442 Title: Enable symbols for all Xilinx device trees Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Jammy: Fix Released Status in linux-xilinx-zynqmp source package in Noble: New Bug description: [ Impact ] * This enables symbols for all device trees built for Xilinx products. * Currently only device trees which have overlays applied have symbols enabled. * Most Xilinx device trees are currently overlayed (thus have the symbols already included) so this should have minimal size impact. [ Test Plan ] * Xilinx will verify they can load the dtbo's for the FPGA during runtime [ Where problems could occur ] * There could be an unexpected impact on other FPGA runtime overlays that are already working. [ Other Info ] * Xilinx platforms apply dtbo's during runtime when loading FPGA firmware. * Xilinx Yocto distribution handle's this in the yocto recipes which is why this change is not upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2049442/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2063290] [NEW] Jammy update: v5.15.153 upstream stable release
evice: support direct IO f2fs: invalidate META_MAPPING before IPU/DIO write f2fs: replace congestion_wait() calls with io_schedule_timeout() f2fs: fix to invalidate META_MAPPING before DIO write f2fs: invalidate meta pages only for post_read required inode f2fs: reduce stack memory cost by using bitfield in struct f2fs_io_info f2fs: compress: fix to cover normal cluster write with cp_rwsem f2fs: compress: fix to check unreleased compressed cluster scsi: csiostor: Avoid function pointer casts RDMA/device: Fix a race between mad_client and cm_client init RDMA/rtrs-clt: Check strnlen return len in sysfs mpath_policy_store() scsi: bfa: Fix function pointer type mismatch for hcb_qe->cbfn net: sunrpc: Fix an off by one in rpc_sockaddr2uaddr() NFSv4.2: fix nfs4_listxattr kernel BUG at mm/usercopy.c:102 NFSv4.2: fix listxattr maximum XDR buffer size watchdog: stm32_iwdg: initialize default timeout NFS: Fix an off by one in root_nfs_cat() f2fs: compress: fix reserve_cblocks counting error when out of space afs: Revert "afs: Hide silly-rename files from userspace" comedi: comedi_test: Prevent timers rescheduling during deletion remoteproc: stm32: use correct format strings on 64-bit remoteproc: stm32: Fix incorrect type in assignment for va remoteproc: stm32: Fix incorrect type assignment returned by stm32_rproc_get_loaded_rsc_tablef tty: vt: fix 20 vs 0x20 typo in EScsiignore serial: max310x: fix syntax error in IRQ error message tty: serial: samsung: fix tx_empty() to return TIOCSER_TEMT arm64: dts: broadcom: bcmbca: bcm4908: drop invalid switch cells kconfig: fix infinite loop when expanding a macro at the end of file rtc: mt6397: select IRQ_DOMAIN instead of depending on it serial: 8250_exar: Don't remove GPIO device on suspend staging: greybus: fix get_channel_from_mode() failure path usb: gadget: net2272: Use irqflags in the call to net2272_probe_fin io_uring: don't save/restore iowait state nouveau: reset the bo resource bus info after an eviction octeontx2-af: Use matching wake_up API variant in CGX command interface s390/vtime: fix average steal time calculation soc: fsl: dpio: fix kcalloc() argument order hsr: Fix uninit-value access in hsr_get_node() net: mtk_eth_soc: move MAC_MCR setting to mac_finish() net: mediatek: mtk_eth_soc: clear MAC_MCR_FORCE_LINK only when MAC is up net: ethernet: mtk_eth_soc: fix PPE hanging issue packet: annotate data-races around ignore_outgoing net: veth: do not manipulate GRO when using XDP net: dsa: mt7530: prevent possible incorrect XTAL frequency selection vdpa/mlx5: Allow CVQ size changes wireguard: receive: annotate data-race around receiving_counter.counter rds: introduce acquire/release ordering in acquire/release_in_xmit() hsr: Handle failures in module init net: phy: fix phy_read_poll_timeout argument type in genphy_loopback net/bnx2x: Prevent access to a freed page in page_pool octeontx2-af: Use separate handlers for interrupts netfilter: nft_set_pipapo: release elements in clone only from destroy path netfilter: nf_tables: do not compare internal table flags on updates rcu: add a helper to report consolidated flavor QS net: report RCU QS on threaded NAPI repolling bpf: report RCU QS in cpumap kthread net: dsa: mt7530: fix handling of LLDP frames net: dsa: mt7530: fix handling of 802.1X PAE frames net: dsa: mt7530: fix link-local frames that ingress vlan filtering ports net: dsa: mt7530: fix handling of all link-local frames spi: spi-mt65xx: Fix NULL pointer access in interrupt handler regmap: Add missing map->bus check remoteproc: stm32: fix incorrect optional pointers UBUNTU: Upstream stable to v5.15.153 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Portia Stephens (portias) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Portia Stephens (portias) ** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.153 upstream stable release from git://git.kernel.org/ - - Linux 5.15.1
[Kernel-packages] [Bug 2061814] [NEW] Mantic update: upstream stable patchset 2024-04-16
s: Delete superfluous, unused "stage" variable in AMX test KVM: selftests: Avoid infinite loop in hyperv_features when invtsc is missing drm/msm/gem: Fix double resv lock aquire ASoC: SOF: ipc3-topology: Fix pipeline tear down logic net/handshake: Fix handshake_req_destroy_test1 bonding: do not report NETDEV_XDP_ACT_XSK_ZEROCOPY devlink: Fix command annotation documentation of: property: Improve finding the consumer of a remote-endpoint property perf: CXL: fix mismatched cpmu event opcode selftests: forwarding: Fix layer 2 miss test flakiness selftests: forwarding: Fix bridge MDB test flakiness selftests: bridge_mdb: Use MDB get instead of dump selftests: forwarding: Suppress grep warnings ptrace: Introduce exception_ip arch hook mm/memory: Use exception ip to search exception tables userfaultfd: fix mmap_changing checking in mfill_atomic_hugetlb selftests/mm: switch to bash from sh selftests: mm: fix map_hugetlb failure on 64K page size systems nouveau: offload fence uevents work to workqueue HID: bpf: remove double fdget() HID: bpf: actually free hdev memory after attaching a HID-BPF program usb: chipidea: core: handle power lost in workqueue usb: core: Prevent null pointer dereference in update_port_device_state interconnect: qcom: sm8550: Enable sync_state powerpc/pseries/iommu: Fix iommu initialisation during DLPAR add powerpc/6xx: set High BAT Enable flag on G2_LE cores iio: adc: ad4130: zero-initialize clock init data iio: adc: ad4130: only set GPIO_CTRL if pin is unused irqchip/gic-v3-its: Handle non-coherent GICv4 redistributors kallsyms: ignore ARMv4 thunks along with others selftests: mptcp: add mptcp_lib_kill_wait mptcp: fix rcv space initialization mptcp: really cope with fastopen race Revert "powerpc/pseries/iommu: Fix iommu initialisation during DLPAR add" drm/amd: Don't init MEC2 firmware when it fails to load usb: typec: tpcm: Fix issues with power being removed during reset ALSA: hda/realtek - Add speaker pin verbtable for Dell dual speaker platform tracing/timerlat: Move hrtimer_init to timerlat_fd open() tracing/synthetic: Fix trace_string() return value tracing/probes: Fix to show a parse error for bad type for $comm tracing/probes: Fix to set arg size and fmt after setting type from BTF Revert "workqueue: Override implicit ordered attribute in workqueue_apply_unbound_cpumask()" iio: pressure: bmp280: Add missing bmp085 to SPI id table pmdomain: mediatek: fix race conditions with genpd drm/amd/display: Add align done check drm/amdgpu/soc21: update VCN 4 max HEVC encoding resolution drm/amd/display: Fix MST Null Ptr for RV net: dsa: mv88e6xxx: Fix failed probe due to unsupported C45 reads nfp: flower: add hardware offload check for post ct entry ftrace: Fix DIRECT_CALLS to use SAVE_REGS by default serial: core: introduce uart_port_tx_flags() serial: mxs-auart: fix tx KVM: x86: make KVM_REQ_NMI request iff NMI pending for vcpu ALSA: hda/realtek: add IDs for Dell dual spk platform crypto: algif_hash - Remove bogus SGL free on zero-length error path nfp: enable NETDEV_XDP_ACT_REDIRECT feature flag wifi: iwlwifi: fix double-free bug wifi: iwlwifi: mvm: fix a crash when we run out of stations thunderbolt: Fix setting the CNS bit in ROUTER_CS_5 smb: client: set correct id, uid and cruid for multiuser automounts KVM: arm64: Fix circular locking dependency arm64/signal: Don't assume that TIF_SVE means we saved SVE state ASoC: SOF: IPC3: fix message bounds on ipc ops tools/rv: Fix curr_reactor uninitialized variable tools/rv: Fix Makefile compiler options for clang tools/rtla: Fix clang warning about mount_point var size pmdomain: renesas: r8a77980-sysc: CR7 must be always on blk-wbt: Fix detection of dirty-throttled tasks docs: kernel_feat.py: fix build error for missing files tracing: Fix HAVE_DYNAMIC_FTRACE_WITH_REGS ifdef netfilter: ipset: fix performance regression in swap operation tracefs: Check for dentry->d_inode exists in set_gid() x86/efi: Drop EFI stub .bss from .data section x86/efi: Drop alignment flags from PE section headers x86/boot: Remove the 'bugger off' message x86/boot: Omit compression buffer from PE/COFF image memory footprint x86/boot: Drop redundant code setting the root device x86/boot: Drop references to startup_64 x86/boot: Grab kernel_info offset from zoffset header directly x86/boot: Set EFI handover offset directly in header asm x86/boot: Define setup size in linker script x86/boot: Derive file size from _edata symbol x86/boot: Construct PE/COFF .text section from assembler x86/boot: Drop PE/COFF .reloc section x86/boot: Split off PE/COFF .data section x86/boot: Increase section and file alignment to 4k/512 x86/efistub: Use 1:1 file:memory mapping for PE/COFF .compat section x86/barrier: Do not serialize MSR accesses on AMD Documentation/arch/ia64/features.rst: fix kernel-feat directive UBUNTU: Upstream stable to v6.1.79, v6.6.18 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Aff
[Kernel-packages] [Bug 2058321] Re: Unsupported platform 'ZynqMP KV260 revB
** Also affects: linux-xilinx-zynqmp (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy) Assignee: (unassigned) => Portia Stephens (portias) ** Changed in: linux-xilinx-zynqmp (Ubuntu) Status: Fix Committed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2058321 Title: Unsupported platform 'ZynqMP KV260 revB Status in linux-xilinx-zynqmp package in Ubuntu: Invalid Status in linux-xilinx-zynqmp source package in Jammy: Fix Committed Bug description: [ Impact ] * flash-kernel uses the model string in the kernel's device tree to determine what platform is running. Thus there is a dependency between the two packages * A change in the model string for KR platforms was made to support rev B (LP #2046280) which breaks older versions of flash-kernel. [ Test Plan ] * Kernel regression testing uses flash-kernel and will test this change * certification testing uses flash-kernel and will test this change [ Where problems could occur ] * This will cause flash-kernel to be updated automatically when the kernel is updated . This may introduce other issues caused by previous flash-kernel changes that users were not running [ Other info ] * flash-kernel SRU https://bugs.launchpad.net/ubuntu/+source/flash- kernel/+bug/2054556 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2058321/+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 2058707] Re: Backport AXI 1-wire host driver
** Also affects: linux-xilinx-zynqmp (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-xilinx-zynqmp (Ubuntu Noble) Importance: High Assignee: Portia Stephens (portias) Status: Fix Committed ** Changed in: linux-xilinx-zynqmp (Ubuntu Noble) Status: Fix Committed => New ** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-xilinx-zynqmp (Ubuntu Noble) Importance: High => Medium ** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy) Assignee: (unassigned) => Portia Stephens (portias) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2058707 Title: Backport AXI 1-wire host driver Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Jammy: Fix Committed Status in linux-xilinx-zynqmp source package in Noble: New Bug description: [ Impact ] * Backport AXI 1-wire host driver. * The driver is used to interface with FPGA IP logic. * The driver is only loaded when device tree overlay is applied on platforms that require the driver. [ Test Plan ] * Xilinx will test the functionality on a KD240 with an FPGA bitstream that has the required IP logic. [ Where problems could occur ] * We are unable to run certification testing with the driver loaded which creates a risk of breaking the driver in the future. [ Other info ] * Private LP bug: https://bugs.launchpad.net/limerick/+bug/2052477 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2058707/+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 2058707] Re: Backport AXI 1-wire host driver
** Changed in: linux-xilinx-zynqmp (Ubuntu) Status: New => In Progress ** Changed in: linux-xilinx-zynqmp (Ubuntu) Importance: Undecided => High ** Changed in: linux-xilinx-zynqmp (Ubuntu) Assignee: (unassigned) => Portia Stephens (portias) ** Changed in: linux-xilinx-zynqmp (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2058707 Title: Backport AXI 1-wire host driver Status in linux-xilinx-zynqmp package in Ubuntu: Fix Committed Bug description: [ Impact ] * Backport AXI 1-wire host driver. * The driver is used to interface with FPGA IP logic. * The driver is only loaded when device tree overlay is applied on platforms that require the driver. [ Test Plan ] * Xilinx will test the functionality on a KD240 with an FPGA bitstream that has the required IP logic. [ Where problems could occur ] * We are unable to run certification testing with the driver loaded which creates a risk of breaking the driver in the future. [ Other info ] * Private LP bug: https://bugs.launchpad.net/limerick/+bug/2052477 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2058707/+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 2058321] Re: Unsupported platform 'ZynqMP KV260 revB
** Changed in: linux-xilinx-zynqmp (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2058321 Title: Unsupported platform 'ZynqMP KV260 revB Status in linux-xilinx-zynqmp package in Ubuntu: Fix Committed Bug description: [ Impact ] * flash-kernel uses the model string in the kernel's device tree to determine what platform is running. Thus there is a dependency between the two packages * A change in the model string for KR platforms was made to support rev B (LP #2046280) which breaks older versions of flash-kernel. [ Test Plan ] * Kernel regression testing uses flash-kernel and will test this change * certification testing uses flash-kernel and will test this change [ Where problems could occur ] * This will cause flash-kernel to be updated automatically when the kernel is updated . This may introduce other issues caused by previous flash-kernel changes that users were not running [ Other info ] * flash-kernel SRU https://bugs.launchpad.net/ubuntu/+source/flash- kernel/+bug/2054556 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2058321/+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 2059991] Re: Mantic update: upstream stable patchset 2024-04-02
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => Portia Stephens (portias) ** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2024-04-02 + + Ported from the following upstream stable releases: + v6.1.78, v6.6.17 + from git://git.kernel.org/ + + ext4: regenerate buddy after block freeing failed if under fc replay + dmaengine: fsl-dpaa2-qdma: Fix the size of dma pools + dmaengine: ti: k3-udma: Report short packet errors + dmaengine: fsl-qdma: Fix a memory leak related to the status queue DMA + dmaengine: fsl-qdma: Fix a memory leak related to the queue command DMA + phy: renesas: rcar-gen3-usb2: Fix returning wrong error code + dmaengine: fix is_slave_direction() return false when DMA_DEV_TO_DEV + phy: ti: phy-omap-usb2: Fix NULL pointer dereference for SRP + cifs: failure to add channel on iface should bump up weight + drm/msms/dp: fixed link clock divider bits be over written in BPC unknown case + drm/msm/dp: return correct Colorimetry for DP_TEST_DYNAMIC_RANGE_CEA case + drm/msm/dpu: check for valid hw_pp in dpu_encoder_helper_phys_cleanup + net: stmmac: xgmac: fix handling of DPP safety error for DMA channels + wifi: mac80211: fix waiting for beacons logic + netdevsim: avoid potential loop in nsim_dev_trap_report_work() + net: atlantic: Fix DMA mapping for PTP hwts ring + selftests: net: cut more slack for gro fwd tests. + selftests: net: avoid just another constant wait + tunnels: fix out of bounds access when building IPv6 PMTU error + atm: idt77252: fix a memleak in open_card_ubr0 + octeontx2-pf: Fix a memleak otx2_sq_init + hwmon: (aspeed-pwm-tacho) mutex for tach reading + hwmon: (coretemp) Fix out-of-bounds memory access + hwmon: (coretemp) Fix bogus core_id to attr name mapping + inet: read sk->sk_family once in inet_recv_error() + drm/i915/gvt: Fix uninitialized variable in handle_mmio() + rxrpc: Fix response to PING RESPONSE ACKs to a dead call + tipc: Check the bearer type before calling tipc_udp_nl_bearer_add() + af_unix: Call kfree_skb() for dead unix_(sk)->oob_skb in GC. + ppp_async: limit MRU to 64K + selftests: cmsg_ipv6: repeat the exact packet + netfilter: nft_compat: narrow down revision to unsigned 8-bits + netfilter: nft_compat: reject unused compat flag + netfilter: nft_compat: restrict match/target protocol to u16 + drm/amd/display: Implement bounds check for stream encoder creation in DCN301 + netfilter: nft_ct: reject direction for ct id + netfilter: nft_set_pipapo: store index in scratch maps + netfilter: nft_set_pipapo: add helper to release pcpu scratch area + netfilter: nft_set_pipapo: remove scratch_aligned pointer + fs/ntfs3: Fix an NULL dereference bug + scsi: core: Move scsi_host_busy() out of host lock if it is for per-command + blk-iocost: Fix an UBSAN shift-out-of-bounds warning + ALSA: usb-audio: Add delay quirk for MOTU M Series 2nd revision + ALSA: usb-audio: Add a quirk for Yamaha YIT-W12TX transmitter + ALSA: usb-audio: add quirk for RODE NT-USB+ + USB: serial: qcserial: add new usb-id for Dell Wireless DW5826e + USB: serial: option: add Fibocom FM101-GL variant + USB: serial: cp210x: add ID for IMST iM871A-USB + usb: dwc3: host: Set XHCI_SG_TRB_CACHE_SIZE_QUIRK + usb: host: xhci-plat: Add support for XHCI_SG_TRB_CACHE_SIZE_QUIRK + hrtimer: Report offline hrtimer enqueue + Input: i8042 - fix strange behavior of touchpad on Clevo NS70PU + Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping ATKBD_CMD_GETID + io_uring/net: fix sr->len for IORING_OP_RECV with MSG_WAITALL and buffers + net: stmmac: xgmac: use #define for string constants + ALSA: usb-audio: Sort quirk table entries + net: stmmac: xgmac: fix a typo of register name in DPP safety handling + perf evlist: Fix evlist__new_default() for > 1 core PMU + cifs: avoid redundant calls to disable multichannel + rust: arc: add explicit `drop()` around `Box::from_raw()` + rust: task: remove redundant explicit link + rust: print: use explicit link in documentation + MAINTAINERS: add Catherine as xfs maintainer for 6.6.y + xfs: bump max fsgeom struct version + xfs: hoist freeing of rt data fork extent mappings + xfs: prevent rt growfs when quota is enabled + xfs: rt stubs should return negative errnos when rt disabled + xfs: fi
[Kernel-packages] [Bug 2059385] Re: Mantic update: upstream stable patchset 2024-03-28
** Changed in: linux (Ubuntu Mantic) Status: In Progress => 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/2059385 Title: Mantic update: upstream stable patchset 2024-03-28 Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Invalid Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2024-03-28 Ported from the following upstream stable releases: v6.1.78, v6.6.17 from git://git.kernel.org/ ext4: regenerate buddy after block freeing failed if under fc replay dmaengine: fsl-dpaa2-qdma: Fix the size of dma pools dmaengine: ti: k3-udma: Report short packet errors dmaengine: fsl-qdma: Fix a memory leak related to the status queue DMA dmaengine: fsl-qdma: Fix a memory leak related to the queue command DMA phy: renesas: rcar-gen3-usb2: Fix returning wrong error code dmaengine: fix is_slave_direction() return false when DMA_DEV_TO_DEV phy: ti: phy-omap-usb2: Fix NULL pointer dereference for SRP cifs: failure to add channel on iface should bump up weight drm/msms/dp: fixed link clock divider bits be over written in BPC unknown case drm/msm/dp: return correct Colorimetry for DP_TEST_DYNAMIC_RANGE_CEA case drm/msm/dpu: check for valid hw_pp in dpu_encoder_helper_phys_cleanup net: stmmac: xgmac: fix handling of DPP safety error for DMA channels wifi: mac80211: fix waiting for beacons logic netdevsim: avoid potential loop in nsim_dev_trap_report_work() net: atlantic: Fix DMA mapping for PTP hwts ring selftests: net: cut more slack for gro fwd tests. selftests: net: avoid just another constant wait tunnels: fix out of bounds access when building IPv6 PMTU error atm: idt77252: fix a memleak in open_card_ubr0 octeontx2-pf: Fix a memleak otx2_sq_init hwmon: (aspeed-pwm-tacho) mutex for tach reading hwmon: (coretemp) Fix out-of-bounds memory access hwmon: (coretemp) Fix bogus core_id to attr name mapping inet: read sk->sk_family once in inet_recv_error() drm/i915/gvt: Fix uninitialized variable in handle_mmio() rxrpc: Fix response to PING RESPONSE ACKs to a dead call tipc: Check the bearer type before calling tipc_udp_nl_bearer_add() af_unix: Call kfree_skb() for dead unix_(sk)->oob_skb in GC. ppp_async: limit MRU to 64K selftests: cmsg_ipv6: repeat the exact packet netfilter: nft_compat: narrow down revision to unsigned 8-bits netfilter: nft_compat: reject unused compat flag netfilter: nft_compat: restrict match/target protocol to u16 drm/amd/display: Implement bounds check for stream encoder creation in DCN301 netfilter: nft_ct: reject direction for ct id netfilter: nft_set_pipapo: store index in scratch maps netfilter: nft_set_pipapo: add helper to release pcpu scratch area netfilter: nft_set_pipapo: remove scratch_aligned pointer fs/ntfs3: Fix an NULL dereference bug scsi: core: Move scsi_host_busy() out of host lock if it is for per-command blk-iocost: Fix an UBSAN shift-out-of-bounds warning ALSA: usb-audio: Add delay quirk for MOTU M Series 2nd revision ALSA: usb-audio: Add a quirk for Yamaha YIT-W12TX transmitter ALSA: usb-audio: add quirk for RODE NT-USB+ USB: serial: qcserial: add new usb-id for Dell Wireless DW5826e USB: serial: option: add Fibocom FM101-GL variant USB: serial: cp210x: add ID for IMST iM871A-USB usb: dwc3: host: Set XHCI_SG_TRB_CACHE_SIZE_QUIRK usb: host: xhci-plat: Add support for XHCI_SG_TRB_CACHE_SIZE_QUIRK hrtimer: Report offline hrtimer enqueue Input: i8042 - fix strange behavior of touchpad on Clevo NS70PU Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping ATKBD_CMD_GETID io_uring/net: fix sr->len for IORING_OP_RECV with MSG_WAITALL and buffers net: stmmac: xgmac: use #define for string constants ALSA: usb-audio: Sort quirk table entries net: stmmac: xgmac: fix a typo of register name in DPP safety handling rust: upgrade to Rust 1.71.1 UBUNTU: [Config] updateconfigs for Rust 1.71.1 rust: upgrade to Rust 1.72.1 perf evlist: Fix evlist__new_default() for > 1 core PMU cifs: avoid redundant calls to disable multichannel rust: arc: add explicit `drop()` around `Box::from_raw()` rust: task: remove redundant explicit link rust: print: use explicit link in documentation rust: upgrade to Rust 1.73.0 MAINTAINERS: add Catherine as xfs maintainer for 6.6.y xfs: bump max fsgeom struct
[Kernel-packages] [Bug 2059991] [NEW] Mantic update: upstream stable patchset 2024-04-02
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: upstream stable patchset 2024-04-02 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** 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: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2059991 Title: Mantic update: upstream stable patchset 2024-04-02 Status in linux package in Ubuntu: Confirmed Status in linux source package in Mantic: 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: upstream stable patchset 2024-04-02 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059991/+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 2058707] Re: Backport AXI 1-wire host driver
** Description changed: [ Impact ] + * Backport AXI 1-wire host driver Edit. + * The driver is used to interface with FPGA IP logic. + * The driver is only loaded when device tree overlay is applied on platforms that require the driver. [ Test Plan ] + * Xilinx will test the functionality on a KD240 with an FPGA bitstream + that has the required IP logic. + [ Where problems could occur ] + * We are unable to run certification testing with the driver loaded + which creates a risk of breaking the driver in the future. + [ Other info ] + + Private LP bug: https://bugs.launchpad.net/limerick/+bug/2052477 ** Description changed: [ Impact ] - * Backport AXI 1-wire host driver Edit. + * Backport AXI 1-wire host driver. * The driver is used to interface with FPGA IP logic. * The driver is only loaded when device tree overlay is applied on platforms that require the driver. [ Test Plan ] * Xilinx will test the functionality on a KD240 with an FPGA bitstream that has the required IP logic. [ Where problems could occur ] * We are unable to run certification testing with the driver loaded which creates a risk of breaking the driver in the future. [ Other info ] Private LP bug: https://bugs.launchpad.net/limerick/+bug/2052477 ** Description changed: [ Impact ] * Backport AXI 1-wire host driver. * The driver is used to interface with FPGA IP logic. * The driver is only loaded when device tree overlay is applied on platforms that require the driver. [ Test Plan ] * Xilinx will test the functionality on a KD240 with an FPGA bitstream that has the required IP logic. [ Where problems could occur ] * We are unable to run certification testing with the driver loaded which creates a risk of breaking the driver in the future. [ Other info ] - Private LP bug: https://bugs.launchpad.net/limerick/+bug/2052477 + * Private LP bug: https://bugs.launchpad.net/limerick/+bug/2052477 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2058707 Title: Backport AXI 1-wire host driver Status in linux-xilinx-zynqmp package in Ubuntu: New Bug description: [ Impact ] * Backport AXI 1-wire host driver. * The driver is used to interface with FPGA IP logic. * The driver is only loaded when device tree overlay is applied on platforms that require the driver. [ Test Plan ] * Xilinx will test the functionality on a KD240 with an FPGA bitstream that has the required IP logic. [ Where problems could occur ] * We are unable to run certification testing with the driver loaded which creates a risk of breaking the driver in the future. [ Other info ] * Private LP bug: https://bugs.launchpad.net/limerick/+bug/2052477 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2058707/+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 2059385] [NEW] Mantic update: upstream stable patchset 2024-03-28
: only remap the written blocks in xfs_reflink_end_cow_extent
xfs: up(ic_sema) if flushing data device fails
xfs: fix internal error from AGFL exhaustion
xfs: inode recovery does not validate the recovered inode
xfs: clean up dqblk extraction
xfs: dquot recovery does not validate the recovered dquot
xfs: clean up FS_XFLAG_REALTIME handling in xfs_ioctl_setattr_xflags
xfs: respect the stable writes flag on the RT device
wifi: mac80211: fix RCU use in TDLS fast-xmit
wifi: iwlwifi: exit eSR only after the FW does
wifi: brcmfmac: Adjust n_channels usage for __counted_by
selftests/net: convert unicast_extensions.sh to run it in unique namespace
selftests/net: convert pmtu.sh to run it in unique namespace
selftests/net: change shebang to bash to support "source"
selftests: net: fix tcp listener handling in pmtu.sh
tsnep: Fix mapping for zero copy XDP_TX action
rxrpc: Fix generation of serial numbers to skip zero
rxrpc: Fix delayed ACKs to not set the reference serial number
rxrpc: Fix counting of new acks and nacks
selftests: net: let big_tcp test cope with slow env
drm/amd/display: Fix 'panel_cntl' could be null in 'dcn21_set_backlight_level()'
drm/amd/display: Add NULL test for 'timing generator' in 'dcn21_set_pipe()'
riscv: Improve tlb_flush()
riscv: Make __flush_tlb_range() loop over pte instead of flushing the whole tlb
riscv: Improve flush_tlb_kernel_range()
mm: Introduce flush_cache_vmap_early()
riscv: mm: execute local TLB flush after populating vmemmap
riscv: Fix set_huge_pte_at() for NAPOT mapping
riscv: Fix hugetlb_mask_last_page() when NAPOT is enabled
riscv: Flush the tlb when a page directory is freed
libceph: rename read_sparse_msg_*() to read_partial_sparse_msg_*()
libceph: just wait for more data to be available on the socket
riscv: Fix arch_hugetlb_migration_supported() for NAPOT
riscv: declare overflow_stack as exported from traps.c
Revert "usb: typec: tcpm: fix cc role at port reset"
x86/lib: Revert to _ASM_EXTABLE_UA() for {get,put}_user() fixups
xhci: process isoc TD properly when there was a transaction error mid TD.
xhci: handle isoc Babble and Buffer Overrun events properly
usb: dwc3: pci: add support for the Intel Arrow Lake-H
media: solo6x10: replace max(a, min(b, c)) by clamp(b, a, c)
io_uring/poll: move poll execution helpers higher up
io_uring/net: un-indent mshot retry path in io_recv_finish()
io_uring/poll: add requeue return code from poll multishot handling
io_uring/net: limit inline multishot retries
UBUNTU: Upstream stable to v6.1.78, v6.6.17
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Mantic)
Importance: Medium
Assignee: Portia Stephens (portias)
Status: In Progress
** 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: New
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Mantic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Mantic)
Status: New => In Progress
** Changed in: linux (Ubuntu Mantic)
Assignee: (unassigned) => Portia Stephens (portias)
** Description changed:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2024-03-28
+
+ Ported from the following upstream stable releases:
+ v6.1.78, v6.6.17
+
from git://git.kernel.org/
+
+ ext4: regenerate buddy after block freeing failed if under fc replay
+ dmaengine: fsl-dpaa2-qdma: Fix the size of dma pools
+ dmaengine: ti: k3-udma: Report short packet errors
+ dmaengine: fsl-qdma: Fix a memory leak related to the status queue DMA
+ dmaengine: fsl-qdma: Fix a memory leak related to the queue command DMA
+ phy: renesas: rcar-gen3-usb2: Fix returning wrong error code
+ dmaengine: fix is_slave_direction() return false when DMA_DEV_TO_DEV
+ phy: ti: phy-omap-usb2: Fix NULL pointer dereference for SRP
+ cifs: failure to add channel on iface should bump up weight
+ drm/msms/dp: fixed link clock divider bits be over written in BPC unknown case
+ drm/msm/dp: return correct Colorimetry for DP_TEST_DYNAMIC_RANGE_CEA case
+ drm/msm/dpu: check for valid hw_pp in dpu_encoder_helper_phys_cleanup
+ net: stmmac: xgmac: fix handling of DPP safety error for DMA channels
+ wifi: mac80211: fix waiting for beacons logic
+ netdevsim: avoid potential loop in nsim_dev_trap_report_work()
+ n
[Kernel-packages] [Bug 2055241] Re: Update on-chip oscillator clock nodes for Kria
** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2055241 Title: Update on-chip oscillator clock nodes for Kria Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Jammy: Fix Committed Bug description: [ Impact ] * This models on-chip oscillator clock nodes in KV/KR/KD board device trees built for Xilinx products to be in sync with the corresponding board schematic * Currently a few clocks were not modelled which are planned to be included now. * Most clocks in board device trees are currently included so this should have minimal size impact. * The correct and cleanest approach is to model clock sources in Xilinx's application dtsi's in order to reference these clock nodes from the board device tree rather than having duplicated nodes in application overlay dtbo's [ Test Plan ] * Normal certification will test that the device tree changes did not introduce a regression on any certified platform. * Xilinx will verify they can load the dtbo's for the FPGA during runtime [ Where problems could occur ] * There could be an unexpected impact since there are discrepancies between some revA vs revB board device trees, all clock nodes not being modelled to be in sync with board schematics [ Other Info ] * Changes are pulled from Xilinx' 6.6 tree https://github.com/Xilinx/linux-xlnx/commit/bd1a7261325afa7526ed12fbaeb8f2e939bd02f8 https://github.com/Xilinx/linux-xlnx/commit/d9d492b32494611dbcc422d9f365a59df20c69b1 https://github.com/Xilinx/linux-xlnx/commit/a0fe3083d290f8507922a68daa60cb92d76d56b2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2055241/+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 2059068] [NEW] Mantic update: upstream stable patchset 2024-03-26
t/sched: flower: Fix chain template offload net/mlx5e: Fix operation precedence bug in port timestamping napi_poll context net/mlx5e: Fix peer flow lists handling net/mlx5: Bridge, Enable mcast in smfs steering mode net/mlx5: Bridge, fix multicast packets sent to uplink net/mlx5e: Ignore IPsec replay window values on sender side selftests: net: fix rps_default_mask with >32 CPUs bpf: Propagate modified uaddrlen from cgroup sockaddr programs bpf: Add bpf_sock_addr_set_sun_path() to allow writing unix sockaddr from bpf ice: work on pre-XDP prog frag count i40e: handle multi-buffer packets that are shrunk by xdp prog ice: remove redundant xdp_rxq_info registration ice: update xdp_rxq_info::frag_size for ZC enabled Rx queue i40e: set xdp_rxq_info::frag_size selftests: bonding: do not test arp/ns target with mode balance-alb/tlb tsnep: Remove FCS for XDP data path tsnep: Fix XDP_RING_NEED_WAKEUP for empty fill ring btrfs: scrub: avoid use-after-free when chunk length is not 64K aligned nfsd: fix RELEASE_LOCKOWNER Revert "drivers/firmware: Move sysfb_init() from device_initcall to subsys_initcall_sync" drm/amdgpu: Fix the null pointer when load rlc firmware drm: Fix TODO list mentioning non-KMS drivers drm: Disable the cursor plane on atomic contexts with virtualized drivers drm/virtio: Disable damage clipping if FB changed since last page-flip drm: Allow drivers to indicate the damage helpers to ignore damage clips drm/amd/display: fix bandwidth validation failure on DCN 2.1 drm/amdgpu: correct the cu count for gfx v11 drm/amd/display: Align the returned error code with legacy DP drm/amd/display: Fix late derefrence 'dsc' check in 'link_set_dsc_pps_packet()' drm/amd/display: Fix uninitialized variable usage in core_link_ 'read_dpcd() & write_dpcd()' functions net/bpf: Avoid unused "sin_addr_len" warning when CONFIG_CGROUP_BPF is not set thermal: core: Store trip pointer in struct thermal_instance thermal: gov_power_allocator: avoid inability to reset a cdev mm: migrate: record the mlocked page status to remove unnecessary lru drain mm: migrate: fix getting incorrect page mapping during page migration drm/i915/lnl: Remove watchdog timers for PSR drm/i915/psr: Only allow PSR in LPSP mode on HSW non-ULT drm/panel-edp: Add AUO B116XTN02, BOE NT116WHM-N21,836X2, NV116WHM-N49 V8.0 drm/panel-edp: drm/panel-edp: Fix AUO B116XTN02 name drm/amdgpu/gfx10: set UNORD_DISPATCH in compute MQDs drm/amdgpu/gfx11: set UNORD_DISPATCH in compute MQDs drm/panel: samsung-s6d7aa0: drop DRM_BUS_FLAG_DE_HIGH for lsl080al02 memblock: fix crash when reserved memory is not added to memory firmware: arm_scmi: Use xa_insert() when saving raw queues spi: intel-pci: Remove Meteor Lake-S SoC PCI ID from the list cpufreq/amd-pstate: Fix setting scaling max/min freq values spi: spi-cadence: Reverse the order of interleaved write and read operations cifs: fix stray unlock in cifs_chan_skip_or_disable drm: bridge: samsung-dsim: Don't use FORCE_STOP_STATE genirq: Initialize resend_node hlist for all interrupt descriptors clocksource: Skip watchdog check for large watchdog intervals thermal: trip: Drop lockdep assertion from thermal_zone_trip_id() platform/x86: intel-uncore-freq: Fix types in sysfs callbacks UBUNTU: Upstream stable to v6.1.76, v6.6.15 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Mantic) Importance: Medium Assignee: Portia Stephens (portias) Status: In Progress ** 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: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => Portia Stephens (portias) ** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2024-03-26 + + Ported from the following upstream stable releases: + v6.1.76, v6.6.15 + from git://git.kernel.org/ + + iio: adc: ad7091r: Set alert bit in config register + iio: adc: ad7091r: Allow users to configure device events + ext4: allow for the last group to be marked as trimmed + arm64: properly install vmlinuz.efi + OPP: Pass rounded rate to _se
[Kernel-packages] [Bug 2058707] [NEW] Backport AXI 1-wire host driver
Public bug reported: [ Impact ] [ Test Plan ] [ Where problems could occur ] [ Other info ] ** Affects: linux-xilinx-zynqmp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2058707 Title: Backport AXI 1-wire host driver Status in linux-xilinx-zynqmp package in Ubuntu: New Bug description: [ Impact ] [ Test Plan ] [ Where problems could occur ] [ Other info ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2058707/+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 2054366] Re: Fix backported kria device tree changes
** Changed in: linux-xilinx-zynqmp (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2054366 Title: Fix backported kria device tree changes Status in linux-xilinx-zynqmp package in Ubuntu: Fix Released Status in linux-xilinx-zynqmp source package in Jammy: Fix Released Bug description: [ Impact ] * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. * Since all Xilinx device tree's are so interdependent all Kria and ZCU device trees were updated including certified platforms. [ Test Plan ] * QA will run certification testing on the KD240 platform * Normal certification testing will be run on all other certified platforms [ Where problems could occur ] * This impacts the device tree for certified Xilinx platforms which could break any of the device touched by the change. [ Fixes ] * 6.1 compatible string and interrupt-name for gpu: gpu@fd4b incorrectly backported * 6.1 compatible string for ethernet@ff0b incorrectly backported * dwc3_[01] quirks incorrectly updated for 6.1 * xilinx_ams field incorrectly updated. [ Other info ] * Private launchpad bugs that contain detail on the KD240 regressions: https://bugs.launchpad.net/limerick/+bug/2051228 https://bugs.launchpad.net/limerick/+bug/2051224 https://bugs.launchpad.net/limerick/+bug/2051201 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2054366/+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 2058321] Re: Unsupported platform 'ZynqMP KV260 revB
** Description changed: [ Impact ] + + * flash-kernel uses the model string in the kernel's device tree to determine what platform is running. Thus there is a dependency between the two packages + * A change in the model string for KR platforms was made to support rev B (LP #2046280) which breaks flash-kernel older versions of flash-kernel. [ Test Plan ] + * Kernel regression testing uses flash-kernel and will test this change + * certification testing uses flash-kernel and will test this change + [ Where problems could occur ] + * This will cause flash-kernel to be updated automatically when the + kernel is updated . This may introduce other issues caused by previous + flash-kernel changes that users were not running + [ Other info ] + + * flash-kernel SRU https://bugs.launchpad.net/ubuntu/+source/flash- + kernel/+bug/2054556 ** Changed in: linux-xilinx-zynqmp (Ubuntu) Assignee: (unassigned) => Portia Stephens (portias) ** Changed in: linux-xilinx-zynqmp (Ubuntu) Status: New => In Progress ** Changed in: linux-xilinx-zynqmp (Ubuntu) Importance: Undecided => High ** Description changed: [ Impact ] * flash-kernel uses the model string in the kernel's device tree to determine what platform is running. Thus there is a dependency between the two packages - * A change in the model string for KR platforms was made to support rev B (LP #2046280) which breaks flash-kernel older versions of flash-kernel. + * A change in the model string for KR platforms was made to support rev B (LP #2046280) which breaks older versions of flash-kernel. [ Test Plan ] * Kernel regression testing uses flash-kernel and will test this change * certification testing uses flash-kernel and will test this change [ Where problems could occur ] * This will cause flash-kernel to be updated automatically when the kernel is updated . This may introduce other issues caused by previous flash-kernel changes that users were not running [ Other info ] * flash-kernel SRU https://bugs.launchpad.net/ubuntu/+source/flash- kernel/+bug/2054556 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2058321 Title: Unsupported platform 'ZynqMP KV260 revB Status in linux-xilinx-zynqmp package in Ubuntu: In Progress Bug description: [ Impact ] * flash-kernel uses the model string in the kernel's device tree to determine what platform is running. Thus there is a dependency between the two packages * A change in the model string for KR platforms was made to support rev B (LP #2046280) which breaks older versions of flash-kernel. [ Test Plan ] * Kernel regression testing uses flash-kernel and will test this change * certification testing uses flash-kernel and will test this change [ Where problems could occur ] * This will cause flash-kernel to be updated automatically when the kernel is updated . This may introduce other issues caused by previous flash-kernel changes that users were not running [ Other info ] * flash-kernel SRU https://bugs.launchpad.net/ubuntu/+source/flash- kernel/+bug/2054556 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2058321/+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 2058321] [NEW] Unsupported platform 'ZynqMP KV260 revB
Public bug reported: [ Impact ] [ Test Plan ] [ Where problems could occur ] [ Other info ] ** Affects: linux-xilinx-zynqmp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2058321 Title: Unsupported platform 'ZynqMP KV260 revB Status in linux-xilinx-zynqmp package in Ubuntu: New Bug description: [ Impact ] [ Test Plan ] [ Where problems could occur ] [ Other info ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2058321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056403] Re: Mantic update: upstream stable patchset 2024-03-07
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => Portia Stephens (portias) ** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2024-03-07 + + Ported from the following upstream stable releases: + v6.1.75, v6.6.14 + from git://git.kernel.org/ + + x86/lib: Fix overflow when counting digits + x86/mce/inject: Clear test status value + EDAC/thunderx: Fix possible out-of-bounds string access + powerpc: add crtsavres.o to always-y instead of extra-y + powerpc/44x: select I2C for CURRITUCK + powerpc/pseries/memhp: Fix access beyond end of drmem array + selftests/powerpc: Fix error handling in FPU/VMX preemption tests + powerpc/powernv: Add a null pointer check to scom_debug_init_one() + powerpc/powernv: Add a null pointer check in opal_event_init() + powerpc/powernv: Add a null pointer check in opal_powercap_init() + powerpc/imc-pmu: Add a null pointer check in update_events_in_group() + spi: spi-zynqmp-gqspi: fix driver kconfig dependencies + mtd: rawnand: Increment IFC_TIMEOUT_MSECS for nand controller response + ACPI: video: check for error while searching for backlight device parent + ACPI: LPIT: Avoid u32 multiplication overflow + platform/x86/intel/vsec: Fix xa_alloc memory leak + cpufreq: scmi: process the result of devm_of_clk_add_hw_provider() + calipso: fix memory leak in netlbl_calipso_add_pass() + efivarfs: force RO when remounting if SetVariable is not supported + spi: sh-msiof: Enforce fixed DTDL for R-Car H3 + ACPI: LPSS: Fix the fractional clock divider flags + ACPI: extlog: Clear Extended Error Log status when RAS_CEC handled the error + kunit: debugfs: Fix unchecked dereference in debugfs_print_results() + mtd: Fix gluebi NULL pointer dereference caused by ftl notifier + selinux: Fix error priority for bind with AF_UNSPEC on PF_INET6 socket + crypto: virtio - Handle dataq logic with tasklet + crypto: sa2ul - Return crypto_aead_setkey to transfer the error + crypto: ccp - fix memleak in ccp_init_dm_workarea + crypto: af_alg - Disallow multiple in-flight AIO requests + crypto: safexcel - Add error handling for dma_map_sg() calls + crypto: sahara - remove FLAGS_NEW_KEY logic + crypto: sahara - fix cbc selftest failure + crypto: sahara - fix ahash selftest failure + crypto: sahara - fix processing requests with cryptlen < sg->length + crypto: sahara - fix error handling in sahara_hw_descriptor_create() + crypto: hisilicon/qm - save capability registers in qm init process + crypto: hisilicon/zip - add zip comp high perf mode configuration + crypto: hisilicon/qm - add a function to set qm algs + crypto: hisilicon/hpre - save capability registers in probe process + crypto: hisilicon/sec2 - save capability registers in probe process + crypto: hisilicon/zip - save capability registers in probe process + pstore: ram_core: fix possible overflow in persistent_ram_init_ecc() + erofs: fix memory leak on short-lived bounced pages + fs: indicate request originates from old mount API + gfs2: Fix kernel NULL pointer dereference in gfs2_rgrp_dump + crypto: virtio - Wait for tasklet to complete on device remove + crypto: sahara - avoid skcipher fallback code duplication + crypto: sahara - handle zero-length aes requests + crypto: sahara - fix ahash reqsize + crypto: sahara - fix wait_for_completion_timeout() error handling + crypto: sahara - improve error handling in sahara_sha_process() + crypto: sahara - fix processing hash requests with req->nbytes < sg->length + crypto: sahara - do not resize req->src when doing hash operations + crypto: scomp - fix req->dst buffer overflow + csky: fix arch_jump_label_transform_static override + blocklayoutdriver: Fix reference leak of pnfs_device_node + NFSv4.1/pnfs: Ensure we handle the error NFS4ERR_RETURNCONFLICT + SUNRPC: fix _xprt_switch_find_current_entry logic + pNFS: Fix the pnfs block driver's calculation of layoutget size + wifi: plfxlc: check for allocation failure in plfxlc_usb_wreq_async() + wifi: rtw88: fix RX filter in FIF_ALLMULTI flag + bpf, lpm: Fix check prefixlen before walking trie + bpf: Add crosstask check to __bpf_get_stack + wifi: ath11k: Defer on rproc_get failure + wifi: libertas: stop selecting wext + ARM: dts: qcom: apq8064: correct XOADC register address + net/ncsi
[Kernel-packages] [Bug 2056403] [NEW] Mantic update: upstream stable patchset 2024-03-07
related to availability of mem event in a PMU perf stat: Exit perf stat if parse groups fails iio: adc: ad9467: add mutex to struct ad9467_state perf unwind-libdw: Handle JIT-generated DSOs properly perf unwind-libunwind: Fix base address for .eh_frame bus: mhi: ep: Do not allocate event ring element on stack bus: mhi: ep: Use slab allocator where applicable usb: gadget: webcam: Make g_webcam loadable again iommu: Don't reserve 0-length IOVA region power: supply: Fix null pointer dereference in smb2_probe apparmor: Fix ref count leak in task_kill perf stat: Fix hard coded LL miss units apparmor: fix possible memory leak in unpack_trans_table serial: apbuart: fix console prompt on qemu perf db-export: Fix missing reference count get in call_path_from_sample() cxl/port: Fix missing target list lock spi: coldfire-qspi: Remove an erroneous clk_disable_unprepare() from the remove function hisi_acc_vfio_pci: Update migration data pointer correctly on saving/resume rxrpc: Fix use of Don't Fragment flag octeontx2-af: CN10KB: Fix FIFO length calculation for RPM2 net: micrel: Fix PTP frame parsing for lan8841 ALSA: hda: Properly setup HDMI stream net: add more sanity check in virtio_net_hdr_to_skb() net: netdev_queue: netdev_txq_completed_mb(): fix wake condition bpf: iter_udp: Retry with a larger batch size without going back to the previous bucket bpf: Avoid iter->offset making backward progress in bpf_iter_udp net: tls, fix WARNIING in __sk_msg_free gpio: mlxbf3: add an error code check in mlxbf3_gpio_probe ASoC: SOF: ipc4-loader: remove the CPC check warnings selftests: bonding: Change script interpreter io_uring: adjust defer tw counting arm64/ptrace: Don't flush ZA/ZT storage when writing ZA via ptrace mlxsw: spectrum_acl_tcam: Fix NULL pointer dereference in error path mlxsw: spectrum_acl_tcam: Fix stack corruption mlxsw: spectrum_router: Register netdevice notifier before nexthop UBUNTU: Upstream stable to v6.1.75, v6.6.14 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Mantic) Importance: Medium Assignee: Portia Stephens (portias) Status: In Progress ** 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: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056403 Title: Mantic update: upstream stable patchset 2024-03-07 Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2024-03-07 Ported from the following upstream stable releases: v6.1.75, v6.6.14 from git://git.kernel.org/ x86/lib: Fix overflow when counting digits x86/mce/inject: Clear test status value EDAC/thunderx: Fix possible out-of-bounds string access powerpc: add crtsavres.o to always-y instead of extra-y powerpc/44x: select I2C for CURRITUCK powerpc/pseries/memhp: Fix access beyond end of drmem array selftests/powerpc: Fix error handling in FPU/VMX preemption tests powerpc/powernv: Add a null pointer check to scom_debug_init_one() powerpc/powernv: Add a null pointer check in opal_event_init() powerpc/powernv: Add a null pointer check in opal_powercap_init() powerpc/imc-pmu: Add a null pointer check in update_events_in_group() spi: spi-zynqmp-gqspi: fix driver kconfig dependencies mtd: rawnand: Increment IFC_TIMEOUT_MSECS for nand controller response ACPI: video: check for error while searching for backlight device parent ACPI: LPIT: Avoid u32 multiplication overflow platform/x86/intel/vsec: Fix xa_alloc memory leak cpufreq: scmi: process the result of devm_of_clk_add_hw_provider() calipso: fix memory leak in netlbl_calipso_add_pass() efivarfs: force RO when remounting if SetVariable is not supported spi: sh-msiof: Enforce fixed DTDL for R-Car H3 ACPI: LPSS: Fix the fractional clock divider flags ACPI: extlog: Clear Extended Error Log status when RAS_CEC handled the error kunit: debugfs: Fix unchecked dereference in debugfs_print_results() mtd: Fix gluebi NULL pointer dereference caused by ftl notifier selinux: Fix error priority for bind with AF_UNSPEC on PF_INET6 socket crypto: virtio - Handle dataq logic with task
[Kernel-packages] [Bug 2055237] Re: Backport ps uart RS485 driver
** Also affects: linux-xilinx-zynqmp (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-xilinx-zynqmp (Ubuntu Noble) Importance: Undecided Assignee: Portia Stephens (portias) Status: In Progress ** Changed in: linux-xilinx-zynqmp (Ubuntu Noble) Status: In Progress => New ** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy) Assignee: (unassigned) => Portia Stephens (portias) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2055237 Title: Backport ps uart RS485 driver Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Jammy: In Progress Status in linux-xilinx-zynqmp source package in Noble: New Bug description: [ Impact ] * Backports support for rs485 to the uartps driver from the tty staging tree [ Test Plan ] * Testing is needed to ensure this doesn't break the serial console on current platforms. QA will develop a new automated test to be integrated into cert testing * Testing of the RS485 port will be integrated into the cert testing for the KD240 [ Where problems could occur ] * The patches have not landed in mainline and are being pulled from the maintainers tree. There is a risk they will be rejected from mainline. [ Other info ] * The following 3 patches are required from the tty-dev tree. All other patches were pulled in to support the backport. 1. https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-next=32152467ffac3b79eae7313959c310946b0e6072 2. https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-next=74231ab6cc2d02303ddf1fabd878756c52f788a5 3. https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-next=fccc9d9233f918ee50cf2955ae7134a7f3418351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2055237/+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 2055241] [NEW] Update on-chip oscillator clock nodes for Kria
Public bug reported: [ Impact ] * This models on-chip oscillator clock nodes in KV/KR/KD board device trees built for Xilinx products to be in sync with the corresponding board schematic * Currently a few clocks were not modelled which are planned to be included now. * Most clocks in board device trees are currently included so this should have minimal size impact. * The correct and cleanest approach is to model clock sources in Xilinx's application dtsi's in order to reference these clock nodes from the board device tree rather than having duplicated nodes in application overlay dtbo's [ Test Plan ] * Normal certification will test that the device tree changes did not introduce a regression on any certified platform. * Xilinx will verify they can load the dtbo's for the FPGA during runtime [ Where problems could occur ] * There could be an unexpected impact since there are discrepancies between some revA vs revB board device trees, all clock nodes not being modelled to be in sync with board schematics [ Other Info ] * Changes are pulled from Xilinx' 6.6 tree https://github.com/Xilinx/linux-xlnx/commit/bd1a7261325afa7526ed12fbaeb8f2e939bd02f8 https://github.com/Xilinx/linux-xlnx/commit/d9d492b32494611dbcc422d9f365a59df20c69b1 https://github.com/Xilinx/linux-xlnx/commit/a0fe3083d290f8507922a68daa60cb92d76d56b2 ** Affects: linux-xilinx-zynqmp (Ubuntu) Importance: Undecided Status: New ** Affects: linux-xilinx-zynqmp (Ubuntu Jammy) Importance: High Assignee: Portia Stephens (portias) Status: In Progress ** Also affects: linux-xilinx-zynqmp (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy) Assignee: (unassigned) => Portia Stephens (portias) ** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy) Importance: Undecided => High ** Description changed: [ Impact ] * This models on-chip oscillator clock nodes in KV/KR/KD board device trees built for Xilinx products to be in sync with the corresponding board schematic * Currently a few clocks were not modelled which are planned to be included now. * Most clocks in board device trees are currently included so this should have minimal size impact. * The correct and cleanest approach is to model clock sources in Xilinx's application dtsi's in order to reference these clock nodes from the board device tree rather than having duplicated nodes in application overlay dtbo's [ Test Plan ] - * Xilinx will verify they can load the dtbo's for the FPGA during - runtime + * Normal certification will test that the device tree changes did not introduce a regression on any certified platform. + * Xilinx will verify they can load the dtbo's for the FPGA during runtime [ Where problems could occur ] * There could be an unexpected impact since there are discrepancies between some revA vs revB board device trees, all clock nodes not being modelled to be in sync with board schematics [ Other Info ] https://github.com/Xilinx/linux-xlnx/commit/bd1a7261325afa7526ed12fbaeb8f2e939bd02f8 https://github.com/Xilinx/linux-xlnx/commit/d9d492b32494611dbcc422d9f365a59df20c69b1 https://github.com/Xilinx/linux-xlnx/commit/a0fe3083d290f8507922a68daa60cb92d76d56b2 ** Description changed: [ Impact ] * This models on-chip oscillator clock nodes in KV/KR/KD board device trees built for Xilinx products to be in sync with the corresponding board schematic * Currently a few clocks were not modelled which are planned to be included now. * Most clocks in board device trees are currently included so this should have minimal size impact. * The correct and cleanest approach is to model clock sources in Xilinx's application dtsi's in order to reference these clock nodes from the board device tree rather than having duplicated nodes in application overlay dtbo's [ Test Plan ] - * Normal certification will test that the device tree changes did not introduce a regression on any certified platform. + * Normal certification will test that the device tree changes did not introduce a regression on any certified platform. * Xilinx will verify they can load the dtbo's for the FPGA during runtime [ Where problems could occur ] * There could be an unexpected impact since there are discrepancies between some revA vs revB board device trees, all clock nodes not being modelled to be in sync with board schematics [ Other Info ] + * Changes are pulled from Xilinx' 6.6 tree https://github.com/Xilinx/linux-xlnx/commit/bd1a7261325afa7526ed12fbaeb8f2e939bd02f8 https://github.com/Xilinx/linux-xlnx/commit/d9d492b32494611dbcc422d9f365a59df20c69b1 https://github.com/Xilinx/linux-xlnx/commit/a0fe3083d290f8507922a68daa60cb92d76d56b2 -- You received this bug notification because you are a member of Kernel Packag
[Kernel-packages] [Bug 2055237] [NEW] Backport ps uart RS485 driver
Public bug reported: [ Impact ] * Backports support for rs485 to the uartps driver from the tty staging tree [ Test Plan ] * Testing is needed to ensure this doesn't break the serial console on current platforms. QA will develop a new automated test to be integrated into cert testing * Testing of the RS485 port will be integrated into the cert testing for the KD240 [ Where problems could occur ] * The patches have not landed in mainline and are being pulled from the maintainers tree. There is a risk they will be rejected from mainline. [ Other info ] * The following 3 patches are required from the tty-dev tree. All other patches were pulled in to support the backport. 1. https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-next=32152467ffac3b79eae7313959c310946b0e6072 2. https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-next=74231ab6cc2d02303ddf1fabd878756c52f788a5 3. https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-next=fccc9d9233f918ee50cf2955ae7134a7f3418351 ** Affects: linux-xilinx-zynqmp (Ubuntu) Importance: Undecided Assignee: Portia Stephens (portias) Status: In Progress ** Changed in: linux-xilinx-zynqmp (Ubuntu) Assignee: (unassigned) => Portia Stephens (portias) ** Description changed: [ Impact ] * Backports support for rs485 to the uartps driver from the tty staging tree - [ Test Plan ] * Testing is needed to ensure this doesn't break the serial console on current platforms. QA will develop a new automated test to be integrated into cert testing * Testing of the RS485 port will be integrated into the cert testing for the KD240 [ Where problems could occur ] * The patches have not landed in mainline and are being pulled from the maintainers tree. There is a risk they will be rejected from mainline. - [ Other info ] + * The following 3 patches are required from the tty-dev tree. All other patches were pulled in to support the backport. + 1. https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-next=32152467ffac3b79eae7313959c310946b0e6072 + 2. https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-next=74231ab6cc2d02303ddf1fabd878756c52f788a5 + 3. https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-next=fccc9d9233f918ee50cf2955ae7134a7f3418351 ** Changed in: linux-xilinx-zynqmp (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2055237 Title: Backport ps uart RS485 driver Status in linux-xilinx-zynqmp package in Ubuntu: In Progress Bug description: [ Impact ] * Backports support for rs485 to the uartps driver from the tty staging tree [ Test Plan ] * Testing is needed to ensure this doesn't break the serial console on current platforms. QA will develop a new automated test to be integrated into cert testing * Testing of the RS485 port will be integrated into the cert testing for the KD240 [ Where problems could occur ] * The patches have not landed in mainline and are being pulled from the maintainers tree. There is a risk they will be rejected from mainline. [ Other info ] * The following 3 patches are required from the tty-dev tree. All other patches were pulled in to support the backport. 1. https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-next=32152467ffac3b79eae7313959c310946b0e6072 2. https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-next=74231ab6cc2d02303ddf1fabd878756c52f788a5 3. https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-next=fccc9d9233f918ee50cf2955ae7134a7f3418351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2055237/+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 2054779] Re: Mantic update: upstream stable patchset 2024-02-26
** Summary changed: - Mantic update: upstream stable patchset 2024-02-23 + Mantic update: upstream stable patchset 2024-02-26 ** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: - upstream stable patchset 2024-02-23 + upstream stable patchset 2024-02-26 Ported from the following upstream stable releases: v6.1.72, v6.6.11 from git://git.kernel.org/ keys, dns: Fix missing size check of V1 server-list header ALSA: hda/realtek: enable SND_PCI_QUIRK for hp pavilion 14-ec1xxx series ALSA: hda/realtek: fix mute/micmute LEDs for a HP ZBook ALSA: hda/realtek: Fix mute and mic-mute LEDs for HP ProBook 440 G6 mptcp: prevent tcp diag from closing listener subflows Revert "PCI/ASPM: Remove pcie_aspm_pm_state_change()" drm/mgag200: Fix gamma lut not initialized for G200ER, G200EV, G200SE cifs: cifs_chan_is_iface_active should be called with chan_lock held cifs: do not depend on release_iface for maintaining iface_list KVM: x86/pmu: fix masking logic for MSR_CORE_PERF_GLOBAL_CTRL wifi: iwlwifi: pcie: don't synchronize IRQs from IRQ drm/bridge: ti-sn65dsi86: Never store more than msg->size bytes in AUX xfer netfilter: nf_tables: set transport offset from mac header for netdev/egress nfc: llcp_core: Hold a ref to llcp_local->dev when holding a ref to llcp_local octeontx2-af: Fix marking couple of structure as __packed drm/i915/dp: Fix passing the correct DPCD_REV for drm_dp_set_phy_test_pattern ice: Fix link_down_on_close message ice: Shut down VSI with "link-down-on-close" enabled i40e: Fix filter input checks to prevent config with invalid values igc: Report VLAN EtherType matching back to user igc: Check VLAN TCI mask igc: Check VLAN EtherType mask ASoC: fsl_rpmsg: Fix error handler with pm_runtime_enable ASoC: mediatek: mt8186: fix AUD_PAD_TOP register and offset mlxbf_gige: fix receive packet race condition net: sched: em_text: fix possible memory leak in em_text_destroy() r8169: Fix PCI error on system resume net: Implement missing getsockopt(SO_TIMESTAMPING_NEW) selftests: bonding: do not set port down when adding to bond ARM: sun9i: smp: Fix array-index-out-of-bounds read in sunxi_mc_smp_init sfc: fix a double-free bug in efx_probe_filters net: bcmgenet: Fix FCS generation for fragmented skbuffs netfilter: nft_immediate: drop chain reference counter on error net: Save and restore msg_namelen in sock_sendmsg i40e: fix use-after-free in i40e_aqc_add_filters() ASoC: meson: g12a-toacodec: Validate written enum values ASoC: meson: g12a-tohdmitx: Validate written enum values ASoC: meson: g12a-toacodec: Fix event generation ASoC: meson: g12a-tohdmitx: Fix event generation for S/PDIF mux i40e: Restore VF MSI-X state during PCI reset igc: Fix hicredit calculation net/qla3xxx: fix potential memleak in ql_alloc_buffer_queues net/smc: fix invalid link access in dumping SMC-R connections octeontx2-af: Always configure NIX TX link credits based on max frame size octeontx2-af: Re-enable MAC TX in otx2_stop processing asix: Add check for usbnet_get_endpoints net: ravb: Wait for operating mode to be applied bnxt_en: Remove mis-applied code from bnxt_cfg_ntp_filters() net: Implement missing SO_TIMESTAMPING_NEW cmsg support bpf: Support new 32bit offset jmp instruction mm: merge folio_has_private()/filemap_release_folio() call pairs mm, netfs, fscache: stop read optimisation when folio removed from pagecache smb: client: fix missing mode bits for SMB symlinks ALSA: hda/realtek: Add quirk for Lenovo Yoga Pro 7 firewire: ohci: suppress unexpected system reboot in AMD Ryzen machines and ASM108x/VT630x PCIe cards x86/kprobes: fix incorrect return address calculation in kprobe_emulate_call_indirect i2c: core: Fix atomic xfer check for non-preempt config mm: fix unmap_mapping_range high bits shift bug drm/amdgpu: skip gpu_info fw loading on navi12 drm/amd/display: add nv12 bounding box mmc: meson-mx-sdhc: Fix initialization frozen issue mmc: rpmb: fixes pause retune on all RPMB partitions. mmc: core: Cancel delayed work before releasing host mmc: sdhci-sprd: Fix eMMC init failure after hw reset bpf: Fix a verifier bug due to incorrect branch offset comparison with cpu=v4 media: qcom: camss: Comment CSID dt_id field Revert "interconnect: qcom: sm8250: Enable sync_state" drm/amd/display: pbn_div need be updated for hotplug event accel/qaic: Fix GEM import path code accel/qaic: Implement quirk
[Kernel-packages] [Bug 2055002] Re: Mantic update: upstream stable patchset 2024-02-27
** Summary changed: - Mantic update: upstream stable patchset 2024-02-26 + Mantic update: upstream stable patchset 2024-02-27 ** Description changed: + SRU Justification - 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: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + upstream stable patchset 2024-02-27 -upstream stable patchset 2024-02-26 + Ported from the following upstream stable releases: + v6.1.73, v6.6.12 - Ported from the following upstream stable releases: - v6.1.73, v6.6.12 - -from git://git.kernel.org/ + from git://git.kernel.org/ Revert "nfsd: call nfsd_last_thread() before final nfsd_put()" cifs: fix flushing folio regression for 6.1 backport UBUNTU: Upstream stable to v6.1.73, v6.6.12 -- 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/2055002 Title: Mantic update: upstream stable patchset 2024-02-27 Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2024-02-27 Ported from the following upstream stable releases: v6.1.73, v6.6.12 from git://git.kernel.org/ Revert "nfsd: call nfsd_last_thread() before final nfsd_put()" cifs: fix flushing folio regression for 6.1 backport UBUNTU: Upstream stable to v6.1.73, v6.6.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055002/+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 2055002] [NEW] Mantic update: upstream stable patchset 2024-02-26
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: upstream stable patchset 2024-02-26 Ported from the following upstream stable releases: v6.1.73, v6.6.12 from git://git.kernel.org/ Revert "nfsd: call nfsd_last_thread() before final nfsd_put()" cifs: fix flushing folio regression for 6.1 backport UBUNTU: Upstream stable to v6.1.73, v6.6.12 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Mantic) Importance: Medium Assignee: Portia Stephens (portias) Status: In Progress ** 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: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => Portia Stephens (portias) ** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2024-02-26 + + Ported from the following upstream stable releases: + v6.1.73, v6.6.12 + from git://git.kernel.org/ + + Revert "nfsd: call nfsd_last_thread() before final nfsd_put()" + cifs: fix flushing folio regression for 6.1 backport + UBUNTU: Upstream stable to v6.1.73, v6.6.12 -- 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/2055002 Title: Mantic update: upstream stable patchset 2024-02-26 Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2024-02-26 Ported from the following upstream stable releases: v6.1.73, v6.6.12 from git://git.kernel.org/ Revert "nfsd: call nfsd_last_thread() before final nfsd_put()" cifs: fix flushing folio regression for 6.1 backport UBUNTU: Upstream stable to v6.1.73, v6.6.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055002/+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 2054779] Re: Mantic update: upstream stable patchset 2024-02-23
** Description changed: + SRU Justification - 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: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + upstream stable patchset 2024-02-23 -upstream stable patchset 2024-02-23 + Ported from the following upstream stable releases: + v6.1.72, v6.6.11 - Ported from the following upstream stable releases: - v6.1.72, v6.6.11 + from git://git.kernel.org/ -from git://git.kernel.org/ - - HID: i2c-hid: Remove I2C_HID_QUIRK_SET_PWR_WAKEUP_DEV quirk - HID: i2c-hid: Renumber I2C_HID_QUIRK_ defines - HID: i2c-hid: Skip SET_POWER SLEEP for Cirque touchpad on system suspend - ALSA: hda/realtek: Enable headset mic on Lenovo M70 Gen5 - Bluetooth: Enforce validation on max value of connection interval - netfilter: nf_tables: reject QUEUE/DROP verdict parameters - xen-netback: don't produce zero-size SKB frags - apparmor: Fix move_mount mediation by detecting if source is detached keys, dns: Fix missing size check of V1 server-list header ALSA: hda/realtek: enable SND_PCI_QUIRK for hp pavilion 14-ec1xxx series ALSA: hda/realtek: fix mute/micmute LEDs for a HP ZBook ALSA: hda/realtek: Fix mute and mic-mute LEDs for HP ProBook 440 G6 mptcp: prevent tcp diag from closing listener subflows Revert "PCI/ASPM: Remove pcie_aspm_pm_state_change()" drm/mgag200: Fix gamma lut not initialized for G200ER, G200EV, G200SE cifs: cifs_chan_is_iface_active should be called with chan_lock held cifs: do not depend on release_iface for maintaining iface_list KVM: x86/pmu: fix masking logic for MSR_CORE_PERF_GLOBAL_CTRL wifi: iwlwifi: pcie: don't synchronize IRQs from IRQ drm/bridge: ti-sn65dsi86: Never store more than msg->size bytes in AUX xfer netfilter: nf_tables: set transport offset from mac header for netdev/egress nfc: llcp_core: Hold a ref to llcp_local->dev when holding a ref to llcp_local octeontx2-af: Fix marking couple of structure as __packed drm/i915/dp: Fix passing the correct DPCD_REV for drm_dp_set_phy_test_pattern ice: Fix link_down_on_close message ice: Shut down VSI with "link-down-on-close" enabled i40e: Fix filter input checks to prevent config with invalid values igc: Report VLAN EtherType matching back to user igc: Check VLAN TCI mask igc: Check VLAN EtherType mask ASoC: fsl_rpmsg: Fix error handler with pm_runtime_enable ASoC: mediatek: mt8186: fix AUD_PAD_TOP register and offset mlxbf_gige: fix receive packet race condition net: sched: em_text: fix possible memory leak in em_text_destroy() r8169: Fix PCI error on system resume net: Implement missing getsockopt(SO_TIMESTAMPING_NEW) selftests: bonding: do not set port down when adding to bond ARM: sun9i: smp: Fix array-index-out-of-bounds read in sunxi_mc_smp_init sfc: fix a double-free bug in efx_probe_filters net: bcmgenet: Fix FCS generation for fragmented skbuffs netfilter: nft_immediate: drop chain reference counter on error net: Save and restore msg_namelen in sock_sendmsg i40e: fix use-after-free in i40e_aqc_add_filters() ASoC: meson: g12a-toacodec: Validate written enum values ASoC: meson: g12a-tohdmitx: Validate written enum values ASoC: meson: g12a-toacodec: Fix event generation ASoC: meson: g12a-tohdmitx: Fix event generation for S/PDIF mux i40e: Restore VF MSI-X state during PCI reset igc: Fix hicredit calculation net/qla3xxx: fix potential memleak in ql_alloc_buffer_queues net/smc: fix invalid link access in dumping SMC-R connections octeontx2-af: Always configure NIX TX link credits based on max frame size octeontx2-af: Re-enable MAC TX in otx2_stop processing asix: Add check for usbnet_get_endpoints net: ravb: Wait for operating mode to be applied bnxt_en: Remove mis-applied code from bnxt_cfg_ntp_filters() net: Implement missing SO_TIMESTAMPING_NEW cmsg support bpf: Support new 32bit offset jmp instruction mm: merge folio_has_private()/filemap_release_folio() call pairs mm, netfs, fscache: stop read optimisation when folio removed from pagecache smb: client: fix missing mode bits for SMB
[Kernel-packages] [Bug 2054366] Re: Fix backported kria device tree changes
I have tested this on KD240 and verified all 3 regressions listed the bug are fixed. ** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy) Assignee: (unassigned) => Portia Stephens (portias) ** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy) Importance: Undecided => High ** Tags removed: verification-needed-jammy-linux-xilinx-zynqmp ** Tags added: verification-done-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2054366 Title: Fix backported kria device tree changes Status in linux-xilinx-zynqmp package in Ubuntu: In Progress Status in linux-xilinx-zynqmp source package in Jammy: Fix Committed Bug description: [ Impact ] * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. * Since all Xilinx device tree's are so interdependent all Kria and ZCU device trees were updated including certified platforms. [ Test Plan ] * QA will run certification testing on the KD240 platform * Normal certification testing will be run on all other certified platforms [ Where problems could occur ] * This impacts the device tree for certified Xilinx platforms which could break any of the device touched by the change. [ Fixes ] * 6.1 compatible string and interrupt-name for gpu: gpu@fd4b incorrectly backported * 6.1 compatible string for ethernet@ff0b incorrectly backported * dwc3_[01] quirks incorrectly updated for 6.1 * xilinx_ams field incorrectly updated. [ Other info ] * Private launchpad bugs that contain detail on the KD240 regressions: https://bugs.launchpad.net/limerick/+bug/2051228 https://bugs.launchpad.net/limerick/+bug/2051224 https://bugs.launchpad.net/limerick/+bug/2051201 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2054366/+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 2054779] Re: Mantic update: upstream stable patchset 2024-02-23
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => Portia Stephens (portias) ** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2024-02-23 + + Ported from the following upstream stable releases: + v6.1.72, v6.6.11 + from git://git.kernel.org/ + + HID: i2c-hid: Remove I2C_HID_QUIRK_SET_PWR_WAKEUP_DEV quirk + HID: i2c-hid: Renumber I2C_HID_QUIRK_ defines + HID: i2c-hid: Skip SET_POWER SLEEP for Cirque touchpad on system suspend + ALSA: hda/realtek: Enable headset mic on Lenovo M70 Gen5 + Bluetooth: Enforce validation on max value of connection interval + netfilter: nf_tables: reject QUEUE/DROP verdict parameters + xen-netback: don't produce zero-size SKB frags + apparmor: Fix move_mount mediation by detecting if source is detached + keys, dns: Fix missing size check of V1 server-list header + ALSA: hda/realtek: enable SND_PCI_QUIRK for hp pavilion 14-ec1xxx series + ALSA: hda/realtek: fix mute/micmute LEDs for a HP ZBook + ALSA: hda/realtek: Fix mute and mic-mute LEDs for HP ProBook 440 G6 + mptcp: prevent tcp diag from closing listener subflows + Revert "PCI/ASPM: Remove pcie_aspm_pm_state_change()" + drm/mgag200: Fix gamma lut not initialized for G200ER, G200EV, G200SE + cifs: cifs_chan_is_iface_active should be called with chan_lock held + cifs: do not depend on release_iface for maintaining iface_list + KVM: x86/pmu: fix masking logic for MSR_CORE_PERF_GLOBAL_CTRL + wifi: iwlwifi: pcie: don't synchronize IRQs from IRQ + drm/bridge: ti-sn65dsi86: Never store more than msg->size bytes in AUX xfer + netfilter: nf_tables: set transport offset from mac header for netdev/egress + nfc: llcp_core: Hold a ref to llcp_local->dev when holding a ref to llcp_local + octeontx2-af: Fix marking couple of structure as __packed + drm/i915/dp: Fix passing the correct DPCD_REV for drm_dp_set_phy_test_pattern + ice: Fix link_down_on_close message + ice: Shut down VSI with "link-down-on-close" enabled + i40e: Fix filter input checks to prevent config with invalid values + igc: Report VLAN EtherType matching back to user + igc: Check VLAN TCI mask + igc: Check VLAN EtherType mask + ASoC: fsl_rpmsg: Fix error handler with pm_runtime_enable + ASoC: mediatek: mt8186: fix AUD_PAD_TOP register and offset + mlxbf_gige: fix receive packet race condition + net: sched: em_text: fix possible memory leak in em_text_destroy() + r8169: Fix PCI error on system resume + net: Implement missing getsockopt(SO_TIMESTAMPING_NEW) + selftests: bonding: do not set port down when adding to bond + ARM: sun9i: smp: Fix array-index-out-of-bounds read in sunxi_mc_smp_init + sfc: fix a double-free bug in efx_probe_filters + net: bcmgenet: Fix FCS generation for fragmented skbuffs + netfilter: nft_immediate: drop chain reference counter on error + net: Save and restore msg_namelen in sock_sendmsg + i40e: fix use-after-free in i40e_aqc_add_filters() + ASoC: meson: g12a-toacodec: Validate written enum values + ASoC: meson: g12a-tohdmitx: Validate written enum values + ASoC: meson: g12a-toacodec: Fix event generation + ASoC: meson: g12a-tohdmitx: Fix event generation for S/PDIF mux + i40e: Restore VF MSI-X state during PCI reset + igc: Fix hicredit calculation + net/qla3xxx: fix potential memleak in ql_alloc_buffer_queues + net/smc: fix invalid link access in dumping SMC-R connections + octeontx2-af: Always configure NIX TX link credits based on max frame size + octeontx2-af: Re-enable MAC TX in otx2_stop processing + asix: Add check for usbnet_get_endpoints + net: ravb: Wait for operating mode to be applied + bnxt_en: Remove mis-applied code from bnxt_cfg_ntp_filters() + net: Implement missing SO_TIMESTAMPING_NEW cmsg support + bpf: Support new 32bit offset jmp instruction + mm: merge folio_has_private()/filemap_release_folio() call pairs + mm, netfs, fscache: stop read optimisation when folio removed from pagecache + smb: client: fix missing mode bits for SMB symlinks + ALSA: hda/realtek: Add quirk for Lenovo Yoga Pro 7 + firewire: ohci: suppress unexpected system reboot in AMD Ryzen machines and ASM108x/VT630x PCIe cards + x86/kprobes: fix incorrect return address calculation in kprobe_emulate_call_indirect + i2c: core: Fix atomic xfer check for non-preempt config +
[Kernel-packages] [Bug 2054779] [NEW] Mantic update: upstream stable patchset 2024-02-23
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: upstream stable patchset 2024-02-23 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** 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: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2054779 Title: Mantic update: upstream stable patchset 2024-02-23 Status in linux package in Ubuntu: Confirmed Status in linux source package in Mantic: 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: upstream stable patchset 2024-02-23 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054779/+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 2054366] Re: Fix backported kria device tree changes
** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2054366 Title: Fix backported kria device tree changes Status in linux-xilinx-zynqmp package in Ubuntu: In Progress Status in linux-xilinx-zynqmp source package in Jammy: Fix Committed Bug description: [ Impact ] * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. * Since all Xilinx device tree's are so interdependent all Kria and ZCU device trees were updated including certified platforms. [ Test Plan ] * QA will run certification testing on the KD240 platform * Normal certification testing will be run on all other certified platforms [ Where problems could occur ] * This impacts the device tree for certified Xilinx platforms which could break any of the device touched by the change. [ Fixes ] * 6.1 compatible string and interrupt-name for gpu: gpu@fd4b incorrectly backported * 6.1 compatible string for ethernet@ff0b incorrectly backported * dwc3_[01] quirks incorrectly updated for 6.1 * xilinx_ams field incorrectly updated. [ Other info ] * Private launchpad bugs that contain detail on the KD240 regressions: https://bugs.launchpad.net/limerick/+bug/2051228 https://bugs.launchpad.net/limerick/+bug/2051224 https://bugs.launchpad.net/limerick/+bug/2051201 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2054366/+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 2054366] Re: Fix backported kria device tree changes
** Description changed: [ Impact ] * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. * Since all Xilinx device tree's are so interdependent all Kria and ZCU device trees were updated including certified platforms. [ Test Plan ] * QA will run certification testing on the KD240 platform * Normal certification testing will be run on all other certified platforms [ Where problems could occur ] * This impacts the device tree for certified Xilinx platforms which could break any of the device touched by the change. - [ Other Info ] + [ Fixes ] + * 6.1 compatible string and interrupt-name for gpu: gpu@fd4b incorrectly backported + * 6.1 compatible string for ethernet@ff0b incorrectly backported + * dwc3_[01] quirks incorrectly updated for 6.1 + * xilinx_ams field incorrectly updated. + [ Other info ] * Private launchpad bugs that contain detail on the KD240 regressions: https://bugs.launchpad.net/limerick/+bug/2051228 https://bugs.launchpad.net/limerick/+bug/2051224 https://bugs.launchpad.net/limerick/+bug/2051201 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2054366 Title: Fix backported kria device tree changes Status in linux-xilinx-zynqmp package in Ubuntu: In Progress Status in linux-xilinx-zynqmp source package in Jammy: New Bug description: [ Impact ] * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. * Since all Xilinx device tree's are so interdependent all Kria and ZCU device trees were updated including certified platforms. [ Test Plan ] * QA will run certification testing on the KD240 platform * Normal certification testing will be run on all other certified platforms [ Where problems could occur ] * This impacts the device tree for certified Xilinx platforms which could break any of the device touched by the change. [ Fixes ] * 6.1 compatible string and interrupt-name for gpu: gpu@fd4b incorrectly backported * 6.1 compatible string for ethernet@ff0b incorrectly backported * dwc3_[01] quirks incorrectly updated for 6.1 * xilinx_ams field incorrectly updated. [ Other info ] * Private launchpad bugs that contain detail on the KD240 regressions: https://bugs.launchpad.net/limerick/+bug/2051228 https://bugs.launchpad.net/limerick/+bug/2051224 https://bugs.launchpad.net/limerick/+bug/2051201 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2054366/+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 2054366] Re: Fix backported kria device tree changes
** Also affects: linux-xilinx-zynqmp (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2054366 Title: Fix backported kria device tree changes Status in linux-xilinx-zynqmp package in Ubuntu: In Progress Status in linux-xilinx-zynqmp source package in Jammy: New Bug description: [ Impact ] * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. * Since all Xilinx device tree's are so interdependent all Kria and ZCU device trees were updated including certified platforms. [ Test Plan ] * QA will run certification testing on the KD240 platform * Normal certification testing will be run on all other certified platforms [ Where problems could occur ] * This impacts the device tree for certified Xilinx platforms which could break any of the device touched by the change. [ Other Info ] * Private launchpad bugs that contain detail on the KD240 regressions: https://bugs.launchpad.net/limerick/+bug/2051228 https://bugs.launchpad.net/limerick/+bug/2051224 https://bugs.launchpad.net/limerick/+bug/2051201 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2054366/+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 2054366] Re: Fix backported kria device tree changes
** Description changed: [ Impact ] - * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. + * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. * Since all Xilinx device tree's are so interdependent all Kria and ZCU device trees were updated including certified platforms. [ Test Plan ] - * QA will run certification testing on the KD240 platform - * Normal certification testing will be run on all other certified platforms + * QA will run certification testing on the KD240 platform + * Normal certification testing will be run on all other certified platforms [ Where problems could occur ] * This impacts the device tree for certified Xilinx platforms which could break any of the device touched by the change. [ Other Info ] - * Private launchpad bugs that contain the regressions: + * Private launchpad bugs that contain detail on the KD240 regressions: https://bugs.launchpad.net/limerick/+bug/2051228 https://bugs.launchpad.net/limerick/+bug/2051224 https://bugs.launchpad.net/limerick/+bug/2051201 ** Changed in: linux-xilinx-zynqmp (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2054366 Title: Fix backported kria device tree changes Status in linux-xilinx-zynqmp package in Ubuntu: In Progress Bug description: [ Impact ] * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. * Since all Xilinx device tree's are so interdependent all Kria and ZCU device trees were updated including certified platforms. [ Test Plan ] * QA will run certification testing on the KD240 platform * Normal certification testing will be run on all other certified platforms [ Where problems could occur ] * This impacts the device tree for certified Xilinx platforms which could break any of the device touched by the change. [ Other Info ] * Private launchpad bugs that contain detail on the KD240 regressions: https://bugs.launchpad.net/limerick/+bug/2051228 https://bugs.launchpad.net/limerick/+bug/2051224 https://bugs.launchpad.net/limerick/+bug/2051201 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2054366/+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 2054366] [NEW] Fix backported kria device tree changes
Public bug reported: [ Impact ] * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. * Since all Xilinx device tree's are so interdependent all Kria and ZCU device trees were updated including certified platforms. [ Test Plan ] * QA will run certification testing on the KD240 platform * Normal certification testing will be run on all other certified platforms [ Where problems could occur ] * This impacts the device tree for certified Xilinx platforms which could break any of the device touched by the change. [ Other Info ] * Private launchpad bugs that contain the regressions: https://bugs.launchpad.net/limerick/+bug/2051228 https://bugs.launchpad.net/limerick/+bug/2051224 https://bugs.launchpad.net/limerick/+bug/2051201 ** Affects: linux-xilinx-zynqmp (Ubuntu) Importance: High Assignee: Portia Stephens (portias) Status: New ** Changed in: linux-xilinx-zynqmp (Ubuntu) Assignee: (unassigned) => Portia Stephens (portias) ** Changed in: linux-xilinx-zynqmp (Ubuntu) Importance: Undecided => Critical ** Changed in: linux-xilinx-zynqmp (Ubuntu) Importance: Critical => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2054366 Title: Fix backported kria device tree changes Status in linux-xilinx-zynqmp package in Ubuntu: New Bug description: [ Impact ] * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. * Since all Xilinx device tree's are so interdependent all Kria and ZCU device trees were updated including certified platforms. [ Test Plan ] * QA will run certification testing on the KD240 platform * Normal certification testing will be run on all other certified platforms [ Where problems could occur ] * This impacts the device tree for certified Xilinx platforms which could break any of the device touched by the change. [ Other Info ] * Private launchpad bugs that contain the regressions: https://bugs.launchpad.net/limerick/+bug/2051228 https://bugs.launchpad.net/limerick/+bug/2051224 https://bugs.launchpad.net/limerick/+bug/2051201 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2054366/+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 2053212] [NEW] Jammy update: v5.15.146 upstream stable release
st qualifier to device_get_match_data() parameter
spi: Introduce spi_get_device_match_data() helper
iio: imu: adis16475: add spi_device_id table
smb: client: fix OOB in SMB2_query_info_init()
mm/filemap: avoid buffered read/write race to read inconsistent data
ring-buffer: Fix wake ups when buffer_percent is set to 100
tracing: Fix blocked reader of snapshot buffer
ring-buffer: Remove useless update to write_stamp in rb_try_to_discard()
ring-buffer: Fix slowpath of interrupted event
dm-integrity: don't modify bio's immutable bio_vec in integrity_metadata()
device property: Allow const parameter to dev_fwnode()
bpf: Fix prog_array_map_poke_run map poke update
Linux 5.15.146
UBUNTU: Upstream stable to v5.15.146
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Jammy)
Importance: Medium
Assignee: Portia Stephens (portias)
Status: In Progress
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Portia Stephens (portias)
** Description changed:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.15.146 upstream stable release
from git://git.kernel.org/
-
+ ARM: dts: dra7: Fix DRA7 L3 NoC node register size
+ ARM: OMAP2+: Fix null pointer dereference and memory leak in
omap_soc_device_init
+ reset: Fix crash when freeing non-existent optional resets
+ s390/vx: fix save/restore of fpu kernel context
+ wifi: iwlwifi: pcie: add another missing bh-disable for rxq->lock
+ wifi: mac80211: mesh_plink: fix matches_local logic
+ net/mlx5e: Fix slab-out-of-bounds in mlx5_query_nic_vport_mac_list()
+ net/mlx5e: fix a potential double-free in fs_udp_create_groups
+ net/mlx5: Fix fw tracer first block check
+ net/mlx5e: Correct snprintf truncation handling for fw_version buffer used by
representors
+ net: sched: ife: fix potential use-after-free
+ ethernet: atheros: fix a memleak in atl1e_setup_ring_resources
+ net/rose: fix races in rose_kill_by_device()
+ net: mana: select PAGE_POOL
+ net: check vlan filter feature in vlan_vids_add_by_dev() and
vlan_vids_del_by_dev()
+ afs: Fix the dynamic root's d_delete to always delete unused dentries
+ afs: Fix dynamic root lookup DNS check
+ net: check dev->gso_max_size in gso_features_check()
+ keys, dns: Allow key types (eg. DNS) to be reclaimed immediately on expiry
+ keys, dns: Fix missing size check of V1 server-list header
+ keys, dns: Fix size check of V1 server-list header
+ afs: Fix overwriting of result of DNS query
+ afs: Use refcount_t rather than atomic_t
+ afs: Fix use-after-free due to get/remove race in volume tree
+ ASoC: hdmi-codec: fix missing report for jack initial status
+ i2c: aspeed: Handle the coalesced stop conditions with the start conditions.
+ pinctrl: at91-pio4: use dedicated lock class for IRQ
+ gpiolib: cdev: add gpio_device locking wrapper around gpio_ioctl()
+ ksmbd: fix wrong name of SMB2_CREATE_ALLOCATION_SIZE
+ drm/i915/mtl: limit second scaler vertical scaling in ver >= 14
+ drm/i915: Relocate intel_atomic_setup_scalers()
+ drm/i915: Fix intel_atomic_setup_scalers() plane_state handling
+ smb: client: fix NULL deref in asn1_ber_decoder()
+ smb: client: fix OOB in smb2_query_reparse_point()
+ interconnect: Treat xlate() returning NULL node as an error
+ iio: imu: inv_mpu6050: fix an error code problem in inv_mpu6050_read_raw
+ Input: ipaq-micro-keys - add error handling for devm_kmemdup
+ scsi: bnx2fc: Fix skb double free in bnx2fc_rcv()
+ iio: common: ms_sensors: ms_sensors_i2c: fix humidity conversion time table
+ iio: adc: ti_am335x_adc: Fix return value check of tiadc_request_dma()
+ iio: triggered-buffer: prevent possible freeing of wrong buffer
+ ALSA: usb-audio: Increase delay in MOTU M quirk
+ wifi: cfg80211: Add my certificate
+ wifi: cfg80211: fix certs build to not depend on file order
+ USB: serial: ftdi_sio: update Actisense PIDs constant names
+ USB: serial: option: add Quectel EG912Y module support
+ USB: serial: option: add Foxconn T99W265 with new baseline
+ USB: serial: option: add Quectel RM500Q R13 firmware support
+ Bluetooth: hci_event: Fi
[Kernel-packages] [Bug 2052406] [NEW] Jammy update: v5.15.145 upstream stable release
rent and ->d_name ksmbd: destroy expired sessions ksmbd: block asynchronous requests when making a delay on session setup ksmbd: fix racy issue from smb2 close and logoff with multichannel ksmbd: fix racy issue under cocurrent smb2 tree disconnect ksmbd: fix uninitialized pointer read in ksmbd_vfs_rename() ksmbd: fix uninitialized pointer read in smb2_create_link() ksmbd: fix multiple out-of-bounds read during context decoding ksmbd: fix UAF issue from opinfo->conn ksmbd: call putname after using the last component ksmbd: fix out-of-bound read in deassemble_neg_contexts() ksmbd: fix out-of-bound read in parse_lease_state() ksmbd: fix posix_acls and acls dereferencing possible ERR_PTR() ksmbd: check the validation of pdu_size in ksmbd_conn_handler_loop ksmbd: validate smb request protocol id ksmbd: add mnt_want_write to ksmbd vfs functions ksmbd: remove unused ksmbd_tree_conn_share function ksmbd: use kzalloc() instead of __GFP_ZERO ksmbd: return a literal instead of 'err' in ksmbd_vfs_kern_path_locked() ksmbd: Change the return value of ksmbd_vfs_query_maximal_access to void ksmbd: use kvzalloc instead of kvmalloc ksmbd: Replace the ternary conditional operator with min() ksmbd: fix out of bounds read in smb2_sess_setup ksmbd: add missing compound request handing in some commands ksmbd: Use struct_size() helper in ksmbd_negotiate_smb_dialect() ksmbd: Replace one-element array with flexible-array member ksmbd: Fix unsigned expression compared with zero ksmbd: check if a mount point is crossed during path lookup ksmbd: validate session id and tree id in compound request ksmbd: fix out of bounds in init_smb2_rsp_hdr() ksmbd: switch to use kmemdup_nul() helper ksmbd: add support for read compound ksmbd: fix wrong interim response on compound ksmbd: fix `force create mode' and `force directory mode' ksmbd: reduce descriptor size if remaining bytes is less than request size ksmbd: Fix one kernel-doc comment ksmbd: fix slub overflow in ksmbd_decode_ntlmssp_auth_blob() ksmbd: add missing calling smb2_set_err_rsp() on error ksmbd: remove experimental warning ksmbd: remove unneeded mark_inode_dirty in set_info_sec() ksmbd: fix passing freed memory 'aux_payload_buf' ksmbd: return invalid parameter error response if smb2 request is invalid ksmbd: check iov vector index in ksmbd_conn_write() ksmbd: fix race condition between session lookup and expire ksmbd: fix race condition with fp ksmbd: fix race condition from parallel smb2 logoff requests ksmbd: fix race condition from parallel smb2 lock requests ksmbd: fix race condition between tree conn lookup and disconnect ksmbd: fix wrong error response status by using set_smb2_rsp_status() ksmbd: fix Null pointer dereferences in ksmbd_update_fstate() ksmbd: fix potential double free on smb2_read_pipe() error path ksmbd: Remove unused field in ksmbd_user struct ksmbd: reorganize ksmbd_iov_pin_rsp() ksmbd: fix kernel-doc comment of ksmbd_vfs_setxattr() ksmbd: fix recursive locking in vfs helpers ksmbd: fix missing RDMA-capable flag for IPoIB device in ksmbd_rdma_capable_netdev() ksmbd: add support for surrogate pair conversion ksmbd: no need to wait for binded connection termination at logoff ksmbd: fix kernel-doc comment of ksmbd_vfs_kern_path_locked() ksmbd: handle malformed smb1 message ksmbd: prevent memory leak on error return ksmbd: fix possible deadlock in smb2_open ksmbd: separately allocate ci per dentry ksmbd: move oplock handling after unlock parent dir ksmbd: release interim response after sending status pending response ksmbd: move setting SMB2_FLAGS_ASYNC_COMMAND and AsyncId ksmbd: don't update ->op_state as OPLOCK_STATE_NONE on error tracing/kprobes: Return EADDRNOTAVAIL when func matches several symbols kasan: disable kasan_non_canonical_hook() for HW tags Linux 5.15.145 UBUNTU: Upstream stable to v5.15.145 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Portia Stephens (portias) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Portia Stephens (portias) ** Description changed: 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 follo
[Kernel-packages] [Bug 2052404] [NEW] Jammy update: v5.15.144 upstream stable release
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.15.144 upstream stable release from git://git.kernel.org/ r8152: add vendor/device ID pair for D-Link DUB-E250 r8152: add vendor/device ID pair for ASUS USB-C2500 netfilter: nf_tables: fix 'exist' matching on bigendian arches mm/memory_hotplug: handle memblock_add_node() failures in add_memory_resource() memblock: allow to specify flags with memblock_add_node() MIPS: Loongson64: Handle more memory types passed from firmware ksmbd: fix memory leak in smb2_lock() afs: Fix refcount underflow from error handling race HID: lenovo: Restrict detection of patched firmware only to USB cptkbd net: ipv6: support reporting otherwise unknown prefix flags in RTM_NEWPREFIX qca_debug: Prevent crash on TX ring changes qca_debug: Fix ethtool -G iface tx behavior qca_spi: Fix reset behavior atm: solos-pci: Fix potential deadlock on _queue_lock atm: solos-pci: Fix potential deadlock on _queue_lock net: vlan: introduce skb_vlan_eth_hdr() net: fec: correct queue selection octeontx2-af: fix a use-after-free in rvu_nix_register_reporters octeontx2-pf: Fix promisc mcam entry action octeontx2-af: Update RSS algorithm index qed: Fix a potential use-after-free in qed_cxt_tables_alloc net: Remove acked SYN flag from packet in the transmit queue correctly net: ena: Destroy correct number of xdp queues upon failure net: ena: Fix xdp drops handling due to multibuf packets net: ena: Fix XDP redirection error stmmac: dwmac-loongson: Make sure MDIO is initialized before use sign-file: Fix incorrect return values check vsock/virtio: Fix unsigned integer wrap around in virtio_transport_has_space() dpaa2-switch: fix size of the dma_unmap net: stmmac: use dev_err_probe() for reporting mdio bus registration failure net: stmmac: Handle disabled MDIO busses from devicetree net: atlantic: fix double free in ring reinit logic cred: switch to using atomic_long_t fuse: dax: set fc->dax to NULL in fuse_dax_conn_free() ALSA: hda/hdmi: add force-connect quirk for NUC5CPYB ALSA: hda/hdmi: add force-connect quirks for ASUSTeK Z170 variants ALSA: hda/realtek: Apply mute LED quirk for HP15-db PCI: loongson: Limit MRRS to 256 drm/mediatek: Add spinlock for setting vblank event in atomic_begin usb: aqc111: check packet for fixup for true limit stmmac: dwmac-loongson: Add architecture dependency UBUNTU: [Config] updateconfigs for CONFIG_DWMAC_LOONGSON blk-throttle: fix lockdep warning of "cgroup_mutex or RCU read lock required!" blk-cgroup: bypass blkcg_deactivate_policy after destroying bcache: avoid oversize memory allocation by small stripe_size bcache: remove redundant assignment to variable cur_idx bcache: add code comments for bch_btree_node_get() and __bch_btree_node_alloc() bcache: avoid NULL checking to c->root in run_cache_set() platform/x86: intel_telemetry: Fix kernel doc descriptions HID: glorious: fix Glorious Model I HID report HID: add ALWAYS_POLL quirk for Apple kb HID: hid-asus: reset the backlight brightness level on resume HID: multitouch: Add quirk for HONOR GLO-GXXX touchpad asm-generic: qspinlock: fix queued_spin_value_unlocked() implementation net: usb: qmi_wwan: claim interface 4 for ZTE MF290 HID: hid-asus: add const to read-only outgoing usb buffer btrfs: do not allow non subvolume root targets for snapshot soundwire: stream: fix NULL pointer dereference for multi_link ext4: prevent the normalized size from exceeding EXT_MAX_BLOCKS arm64: mm: Always make sw-dirty PTEs hw-dirty in pte_modify team: Fix use-after-free when an option instance allocation fails drm/amdgpu/sdma5.2: add begin/end_use ring callbacks ring-buffer: Fix memory leak of free page tracing: Update snapshot buffer on resize if it is allocated ring-buffer: Do not update before stamp when switching sub-buffers ring-buffer: Have saved event hold the entire event ring-buffer: Fix writing to the buffer with max_data_size ring-buffer: Fix a race in rb_time_cmpxchg() for 32 bit archs ring-buffer: Do not try to put back write_stamp USB: gadget: core: adjust uevent timing on gadget unbind powerpc/ftrace: Create a dummy stackframe to fix stack unwind powerpc/ftrace: Fix stack teardown in ftrace_no_trace r8152: avoid to change cfg for all devices r8152: remove rtl_vendor_mode function r8152: fix the autosuspend doesn't work Linux 5.15.144 UBUNTU: Upstream stable to v5.15.144 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Portia Stephens (portias) Status: In Progress
[Kernel-packages] [Bug 2050858] Re: Jammy update: v5.15.143 upstream stable release
** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.143 upstream stable release from git://git.kernel.org/ - vdpa/mlx5: preserve CVQ vringh index hrtimers: Push pending hrtimers away from outgoing CPU earlier i2c: designware: Fix corrupted memory seen in the ISR netfilter: ipset: fix race condition between swap/destroy and kernel side add/del/test tg3: Move the [rt]x_dropped counters to tg3_napi tg3: Increment tx_dropped in tg3_tso_bug() kconfig: fix memory leak from range properties drm/amdgpu: correct chunk_ptr to a pointer to chunk. platform/x86: asus-wmi: Adjust tablet/lidflip handling to use enum platform/x86: asus-wmi: Add support for ROG X13 tablet mode platform/x86: asus-wmi: Simplify tablet-mode-switch probing platform/x86: asus-wmi: Simplify tablet-mode-switch handling platform/x86: asus-wmi: Move i8042 filter install to shared asus-wmi code of: dynamic: Fix of_reconfig_get_state_change() return value documentation platform/x86: wmi: Allow duplicate GUIDs for drivers that use struct wmi_driver platform/x86: wmi: Skip blocks with zero instances ipv6: fix potential NULL deref in fib6_add() octeontx2-pf: Add missing mutex lock in otx2_get_pauseparam octeontx2-af: Check return value of nix_get_nixlf before using nixlf hv_netvsc: rndis_filter needs to select NLS r8152: Rename RTL8152_UNPLUG to RTL8152_INACCESSIBLE r8152: Add RTL8152_INACCESSIBLE checks to more loops r8152: Add RTL8152_INACCESSIBLE to r8156b_wait_loading_flash() r8152: Add RTL8152_INACCESSIBLE to r8153_pre_firmware_1() r8152: Add RTL8152_INACCESSIBLE to r8153_aldps_en() mlxbf-bootctl: correctly identify secure boot with development keys platform/mellanox: Add null pointer checks for devm_kasprintf() platform/mellanox: Check devm_hwmon_device_register_with_groups() return value arcnet: restoring support for multiple Sohard Arcnet cards net: stmmac: fix FPE events losing octeontx2-af: fix a use-after-free in rvu_npa_register_reporters i40e: Fix unexpected MFS warning message net: bnxt: fix a potential use-after-free in bnxt_init_tc ionic: fix snprintf format length warning ionic: Fix dim work handling in split interrupt mode ipv4: ip_gre: Avoid skb_pull() failure in ipgre_xmit() net: hns: fix fake link up on xge port octeontx2-af: Update Tx link register range netfilter: nf_tables: validate family when identifying table via handle netfilter: xt_owner: Fix for unsafe access of sk->sk_socket tcp: do not accept ACK of bytes we never sent bpf: sockmap, updating the sg structure should also update curr psample: Require 'CAP_NET_ADMIN' when joining "packets" group net: add missing kdoc for struct genl_multicast_group::flags drop_monitor: Require 'CAP_SYS_ADMIN' when joining "events" group tee: optee: Fix supplicant based device enumeration RDMA/hns: Fix unnecessary err return when using invalid congest control algorithm RDMA/irdma: Do not modify to SQD on error RDMA/irdma: Add wait for suspend on SQD arm64: dts: rockchip: Expand reg size of vdec node for RK3399 RDMA/rtrs-srv: Do not unconditionally enable irq RDMA/rtrs-clt: Start hb after path_up RDMA/rtrs-srv: Check return values while processing info request RDMA/rtrs-srv: Free srv_mr iu only when always_invalidate is true RDMA/rtrs-srv: Destroy path files after making sure no IOs in-flight RDMA/rtrs-clt: Fix the max_send_wr setting RDMA/rtrs-clt: Remove the warnings for req in_use check RDMA/bnxt_re: Correct module description string hwmon: (acpi_power_meter) Fix 4.29 MW bug hwmon: (nzxt-kraken2) Fix error handling path in kraken2_probe() ASoC: wm_adsp: fix memleak in wm_adsp_buffer_populate RDMA/core: Fix umem iterator when PAGE_SIZE is greater then HCA pgsz RDMA/irdma: Avoid free the non-cqp_request scratch arm64: dts: imx8mq: drop usb3-resume-missing-cas from usb arm64: dts: imx8mp: imx8mq: Add parkmode-disable-ss-quirk on DWC3 ARM: dts: imx6ul-pico: Describe the Ethernet PHY clock tracing: Fix a warning when allocating buffered events fails scsi: be2iscsi: Fix a memleak in beiscsi_init_wrb_handle() ARM: imx: Check return value of devm_kasprintf in imx_mmdc_perf_init ARM: dts: imx7: Declare timers compatible with fsl,imx6dl-gpt ARM: dts: imx28-xea: Pass the 'model' property riscv: fix misaligned access handling of C.SWSP and C.SDSP md: introduce md_ro_state md: don't leave 'MD_RECOVERY_FROZEN' in error path of md_set_readonly() kprobes: consistent rcu api usage for kretprobe
[Kernel-packages] [Bug 2051176] Re: Update Ubuntu.md
** Summary changed: - Ubuntu.md in Mantic is out of date + Update Ubuntu.md ** Description changed: [ Impact ] - * The Ubuntu.md has incorrect Ubuntu release and kernel version + * The Ubuntu.md has incorrect Ubuntu release and kernel version information which may impact any tools that use this information to determine the Ubuntu release. [ Test Plan ] - * cat Ubuntu.md and check to make sure it is correct + * cat Ubuntu.md and check to make sure it is correct [ Where problems could occur ] - * There is no functional impact on the kernel.. we could introduce a + * There is no functional impact on the kernel.. we could introduce a typo in Ubuntu.md + + [ Other Info ] + + * I used the current kernel version of 6.5.10 since it didn't seem to + make sense to use the old version we released with. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2051176 Title: Update Ubuntu.md Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: In Progress Bug description: [ Impact ] * The Ubuntu.md has incorrect Ubuntu release and kernel version information which may impact any tools that use this information to determine the Ubuntu release. [ Test Plan ] * cat Ubuntu.md and check to make sure it is correct [ Where problems could occur ] * There is no functional impact on the kernel.. we could introduce a typo in Ubuntu.md [ Other Info ] * I used the current kernel version of 6.5.10 since it didn't seem to make sense to use the old version we released with. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051176/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051176] [NEW] Ubuntu.md in Mantic is out of date
Public bug reported: [ Impact ] * The Ubuntu.md has incorrect Ubuntu release and kernel version information which may impact any tools that use this information to determine the Ubuntu release. [ Test Plan ] * cat Ubuntu.md and check to make sure it is correct [ Where problems could occur ] * There is no functional impact on the kernel.. we could introduce a typo in Ubuntu.md ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Mantic) Importance: Medium Assignee: Portia Stephens (portias) Status: In Progress ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => Portia Stephens (portias) ** Changed in: linux (Ubuntu) Status: New => Invalid ** Description changed: - Ubuntu.md in mantic:linux still references the Lunar release. + [ Impact ] + + * The Ubuntu.md has incorrect Ubuntu release and kernel version + information which may impact any tools that use this information to + determine the Ubuntu release. + + [ Test Plan ] + + * cat Ubuntu.md and check to make sure it is correct + + [ Where problems could occur ] + + * There is no functional impact on the kernel.. we could introduce a + typo in Ubuntu.md -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2051176 Title: Ubuntu.md in Mantic is out of date Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: In Progress Bug description: [ Impact ] * The Ubuntu.md has incorrect Ubuntu release and kernel version information which may impact any tools that use this information to determine the Ubuntu release. [ Test Plan ] * cat Ubuntu.md and check to make sure it is correct [ Where problems could occur ] * There is no functional impact on the kernel.. we could introduce a typo in Ubuntu.md To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051176/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2050858] Re: Jammy update: v5.15.143 upstream stable release
** Description changed: + SRU Justification - 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: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.15.143 upstream stable release + from git://git.kernel.org/ -v5.15.143 upstream stable release -from git://git.kernel.org/ - - + vdpa/mlx5: preserve CVQ vringh index + hrtimers: Push pending hrtimers away from outgoing CPU earlier + i2c: designware: Fix corrupted memory seen in the ISR + netfilter: ipset: fix race condition between swap/destroy and kernel side add/del/test + tg3: Move the [rt]x_dropped counters to tg3_napi + tg3: Increment tx_dropped in tg3_tso_bug() + kconfig: fix memory leak from range properties + drm/amdgpu: correct chunk_ptr to a pointer to chunk. + platform/x86: asus-wmi: Adjust tablet/lidflip handling to use enum + platform/x86: asus-wmi: Add support for ROG X13 tablet mode + platform/x86: asus-wmi: Simplify tablet-mode-switch probing + platform/x86: asus-wmi: Simplify tablet-mode-switch handling + platform/x86: asus-wmi: Move i8042 filter install to shared asus-wmi code + of: dynamic: Fix of_reconfig_get_state_change() return value documentation + platform/x86: wmi: Allow duplicate GUIDs for drivers that use struct wmi_driver + platform/x86: wmi: Skip blocks with zero instances + ipv6: fix potential NULL deref in fib6_add() + octeontx2-pf: Add missing mutex lock in otx2_get_pauseparam + octeontx2-af: Check return value of nix_get_nixlf before using nixlf + hv_netvsc: rndis_filter needs to select NLS + r8152: Rename RTL8152_UNPLUG to RTL8152_INACCESSIBLE + r8152: Add RTL8152_INACCESSIBLE checks to more loops + r8152: Add RTL8152_INACCESSIBLE to r8156b_wait_loading_flash() + r8152: Add RTL8152_INACCESSIBLE to r8153_pre_firmware_1() + r8152: Add RTL8152_INACCESSIBLE to r8153_aldps_en() + mlxbf-bootctl: correctly identify secure boot with development keys + platform/mellanox: Add null pointer checks for devm_kasprintf() + platform/mellanox: Check devm_hwmon_device_register_with_groups() return value + arcnet: restoring support for multiple Sohard Arcnet cards + net: stmmac: fix FPE events losing + octeontx2-af: fix a use-after-free in rvu_npa_register_reporters + i40e: Fix unexpected MFS warning message + net: bnxt: fix a potential use-after-free in bnxt_init_tc + ionic: fix snprintf format length warning + ionic: Fix dim work handling in split interrupt mode + ipv4: ip_gre: Avoid skb_pull() failure in ipgre_xmit() + net: hns: fix fake link up on xge port + octeontx2-af: Update Tx link register range + netfilter: nf_tables: validate family when identifying table via handle + netfilter: xt_owner: Fix for unsafe access of sk->sk_socket + tcp: do not accept ACK of bytes we never sent + bpf: sockmap, updating the sg structure should also update curr + psample: Require 'CAP_NET_ADMIN' when joining "packets" group + net: add missing kdoc for struct genl_multicast_group::flags + drop_monitor: Require 'CAP_SYS_ADMIN' when joining "events" group + tee: optee: Fix supplicant based device enumeration + RDMA/hns: Fix unnecessary err return when using invalid congest control algorithm + RDMA/irdma: Do not modify to SQD on error + RDMA/irdma: Add wait for suspend on SQD + arm64: dts: rockchip: Expand reg size of vdec node for RK3399 + RDMA/rtrs-srv: Do not unconditionally enable irq + RDMA/rtrs-clt: Start hb after path_up + RDMA/rtrs-srv: Check return values while processing info request + RDMA/rtrs-srv: Free srv_mr iu only when always_invalidate is true + RDMA/rtrs-srv: Destroy path files after making sure no IOs in-flight + RDMA/rtrs-clt: Fix the max_send_wr setting + RDMA/rtrs-clt: Remove the warnings for req in_use check + RDMA/bnxt_re: Correct module description string + hwmon: (acpi_power_meter) Fix 4.29 MW bug + hwmon: (nzxt-kraken2) Fix error handling path in kraken2_probe() + ASoC: wm_adsp: fix memleak in wm_adsp_buffer_populate + RDMA/core: Fix umem iterator when PAGE_SIZE is greater then HCA pgsz + RDMA/irdma: Avoid free the non-cqp_request scratch + arm64: dts: imx8mq: drop usb3-resume-missing-cas from usb + arm64: dts: imx8mp: imx8mq: Add parkmode-disable-ss-quirk on DWC3 + ARM: dts:
[Kernel-packages] [Bug 2050858] Re: Jammy update: v5.15.143 upstream stable release
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Portia Stephens (portias)
--
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/2050858
Title:
Jammy update: v5.15.143 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
In Progress
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.15.143 upstream stable release
from git://git.kernel.org/
Linux 5.15.143
devcoredump: Send uevent once devcd is ready
devcoredump : Serialize devcd_del work
smb: client: fix potential NULL deref in parse_dfs_referrals()
cifs: Fix non-availability of dedup breaking generic/304
Revert "btrfs: add dmesg output for first mount and last unmount of a
filesystem"
MIPS: Loongson64: Enable DMA noncoherent support
MIPS: Loongson64: Reserve vgabios memory on boot
KVM: SVM: Update EFER software model on CR0 trap for SEV-ES
KVM: s390/mm: Properly reset no-dat
x86/CPU/AMD: Check vendor in the AMD microcode callback
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
Revert "xhci: Loosen RPM as default policy to cover for AMD xHC 1.1"
parport: Add support for Brainboxes IX/UC/PX parallel cards
usb: gadget: f_hid: fix report descriptor allocation
drm/amdgpu: correct the amdgpu runtime dereference usage count
drm/amd/amdgpu: Fix warnings in amdgpu/amdgpu_display.c
gpiolib: sysfs: Fix error handling on failed export
perf: Fix perf_event_validate_size()
perf/core: Add a new read format to get a number of lost samples
arm64: dts: mt8183: kukui: Fix underscores in node names
arm64: dts: mediatek: add missing space before {
arm64: dts: mediatek: mt8183: Move thermal-zones to the root node
arm64: dts: mediatek: align thermal zone node names with dtschema
tools headers UAPI: Sync linux/perf_event.h with the kernel sources
docs/process/howto: Replace C89 with C11
platform/x86: asus-wmi: Fix kbd_dock_devid tablet-switch reporting
netfilter: nft_set_pipapo: skip inactive elements during set walk
io_uring/af_unix: disable sending io_uring over sockets
mm: fix oops when filemap_map_pmd() without prealloc_pte
r8169: fix rtl8125b PAUSE frames blasting when suspended
tracing: Stop current tracer when resizing buffer
tracing: Set actual size after ring buffer resize
ring-buffer: Force absolute timestamp on discard of event
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: etm4x: Remove bogous __exit annotation for some functions
coresight: etm4x: Make etm4_remove_dev() return void
kallsyms: Make kallsyms_on_each_symbol generally available
binder: fix memory leaks of spam and pending work
arm64: dts: mediatek: mt8183: Fix unit address for scp reserved memory
arm64: dts: mediatek: mt8173-evb: Fix regulator-fixed node names
arm64: dts: mediatek: mt8183-kukui-jacuzzi: fix dsi unnecessary cells
properties
arm64: dts: mediatek: mt7622: fix memory node warning check
platform/surface: aggregator: fix recv_buf() return value
regmap: fix bogus error on regcache_sync success
packet: Move reference count in packet_sock to atomic_long_t
tracing: Fix a possible race when disabling buffered events
tracing: Fix incomplete locking when disabling buffered events
tracing: Disable snapshot buffer when stopping instance tracers
tracing: Always update snapshot buffer size
checkstack: fix printed address
nilfs2: prevent WARNING in nilfs_sufile_set_segment_usage()
nilfs2: fix missing error check for sb_set_blocksize call
ALSA: hda/realtek: Enable headset on Lenovo M90 Gen5
ALSA: pcm: fix out-of-bounds in snd_pcm_state_names
ALSA: usb-audio: Add Pioneer DJM-450 mixer controls
io_uring: fix mutex_unlock with unreferenced ctx
nvme-pci: Add sleep quirk for Kingston drives
kprobes: consistent rcu api
[Kernel-packages] [Bug 2050858] [NEW] Jammy update: v5.15.143 upstream stable release
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.15.143 upstream stable release
from git://git.kernel.org/
Linux 5.15.143
devcoredump: Send uevent once devcd is ready
devcoredump : Serialize devcd_del work
smb: client: fix potential NULL deref in parse_dfs_referrals()
cifs: Fix non-availability of dedup breaking generic/304
Revert "btrfs: add dmesg output for first mount and last unmount of a
filesystem"
MIPS: Loongson64: Enable DMA noncoherent support
MIPS: Loongson64: Reserve vgabios memory on boot
KVM: SVM: Update EFER software model on CR0 trap for SEV-ES
KVM: s390/mm: Properly reset no-dat
x86/CPU/AMD: Check vendor in the AMD microcode callback
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
Revert "xhci: Loosen RPM as default policy to cover for AMD xHC 1.1"
parport: Add support for Brainboxes IX/UC/PX parallel cards
usb: gadget: f_hid: fix report descriptor allocation
drm/amdgpu: correct the amdgpu runtime dereference usage count
drm/amd/amdgpu: Fix warnings in amdgpu/amdgpu_display.c
gpiolib: sysfs: Fix error handling on failed export
perf: Fix perf_event_validate_size()
perf/core: Add a new read format to get a number of lost samples
arm64: dts: mt8183: kukui: Fix underscores in node names
arm64: dts: mediatek: add missing space before {
arm64: dts: mediatek: mt8183: Move thermal-zones to the root node
arm64: dts: mediatek: align thermal zone node names with dtschema
tools headers UAPI: Sync linux/perf_event.h with the kernel sources
docs/process/howto: Replace C89 with C11
platform/x86: asus-wmi: Fix kbd_dock_devid tablet-switch reporting
netfilter: nft_set_pipapo: skip inactive elements during set walk
io_uring/af_unix: disable sending io_uring over sockets
mm: fix oops when filemap_map_pmd() without prealloc_pte
r8169: fix rtl8125b PAUSE frames blasting when suspended
tracing: Stop current tracer when resizing buffer
tracing: Set actual size after ring buffer resize
ring-buffer: Force absolute timestamp on discard of event
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: etm4x: Remove bogous __exit annotation for some functions
coresight: etm4x: Make etm4_remove_dev() return void
kallsyms: Make kallsyms_on_each_symbol generally available
binder: fix memory leaks of spam and pending work
arm64: dts: mediatek: mt8183: Fix unit address for scp reserved memory
arm64: dts: mediatek: mt8173-evb: Fix regulator-fixed node names
arm64: dts: mediatek: mt8183-kukui-jacuzzi: fix dsi unnecessary cells properties
arm64: dts: mediatek: mt7622: fix memory node warning check
platform/surface: aggregator: fix recv_buf() return value
regmap: fix bogus error on regcache_sync success
packet: Move reference count in packet_sock to atomic_long_t
tracing: Fix a possible race when disabling buffered events
tracing: Fix incomplete locking when disabling buffered events
tracing: Disable snapshot buffer when stopping instance tracers
tracing: Always update snapshot buffer size
checkstack: fix printed address
nilfs2: prevent WARNING in nilfs_sufile_set_segment_usage()
nilfs2: fix missing error check for sb_set_blocksize call
ALSA: hda/realtek: Enable headset on Lenovo M90 Gen5
ALSA: pcm: fix out-of-bounds in snd_pcm_state_names
ALSA: usb-audio: Add Pioneer DJM-450 mixer controls
io_uring: fix mutex_unlock with unreferenced ctx
nvme-pci: Add sleep quirk for Kingston drives
kprobes: consistent rcu api usage for kretprobe holder
md: don't leave 'MD_RECOVERY_FROZEN' in error path of md_set_readonly()
md: introduce md_ro_state
riscv: fix misaligned access handling of C.SWSP and C.SDSP
ARM: dts: imx28-xea: Pass the 'model' property
ARM: dts: imx7: Declare timers compatible with fsl,imx6dl-gpt
ARM: imx: Check return value of devm_kasprintf in imx_mmdc_perf_init
scsi: be2iscsi: Fix a memleak in beiscsi_init_wrb_handle()
tracing: Fix a warning when allocating buffered events fails
ARM: dts: imx6ul-pico: Describe the Ethernet PHY clock
arm64: dts: imx8mp: imx8mq: Add parkmode-disable-ss-quirk on DWC3
arm64: dts: imx8mq: drop usb3-resume-missing-cas from usb
RDMA/irdma: Avoid free the non-cqp_request scratch
RDMA/core: Fix umem iterator when PAGE_SIZE is greater then HCA pgsz
ASoC: wm_adsp: fix memleak in
[Kernel-packages] [Bug 2050849] Re: Jammy update: v5.15.142 upstream stable release
** Description changed: + SRU Justification - 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: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.15.142 upstream stable release + from git://git.kernel.org/ -v5.15.142 upstream stable release -from git://git.kernel.org/ - - + locking/ww_mutex/test: Fix potential workqueue corruption + perf/core: Bail out early if the request AUX area is out of bound + clocksource/drivers/timer-imx-gpt: Fix potential memory leak + clocksource/drivers/timer-atmel-tcb: Fix initialization on SAM9 hardware + workqueue: Provide one lock class key per work_on_cpu() callsite + x86/mm: Drop the 4 MB restriction on minimal NUMA node memory size + wifi: mac80211_hwsim: fix clang-specific fortify warning + wifi: mac80211: don't return unset power in ieee80211_get_tx_power() + atl1c: Work around the DMA RX overflow issue + bpf: Detect IP == ksym.end as part of BPF program + wifi: ath9k: fix clang-specific fortify warnings + wifi: ath10k: fix clang-specific fortify warning + net: annotate data-races around sk->sk_tx_queue_mapping + net: annotate data-races around sk->sk_dst_pending_confirm + wifi: ath10k: Don't touch the CE interrupt registers after power up + Bluetooth: btusb: Add date->evt_skb is NULL check + Bluetooth: Fix double free in hci_conn_cleanup + platform/x86: thinkpad_acpi: Add battery quirk for Thinkpad X120e + drm/komeda: drop all currently held locks if deadlock happens + drm/amdkfd: Fix a race condition of vram buffer unref in svm code + drm/amd/display: use full update for clip size increase of large plane source + string.h: add array-wrappers for (v)memdup_user() + kernel: kexec: copy user-array safely + kernel: watch_queue: copy user-array safely + drm: vmwgfx_surface.c: copy user-array safely + drm/msm/dp: skip validity check for DP CTS EDID checksum + drm/amd: Fix UBSAN array-index-out-of-bounds for SMU7 + drm/amd: Fix UBSAN array-index-out-of-bounds for Polaris and Tonga + drm/amdgpu: Fix potential null pointer derefernce + drm/panel: fix a possible null pointer dereference + drm/panel/panel-tpo-tpg110: fix a possible null pointer dereference + drm/amdgpu/vkms: fix a possible null pointer dereference + drm/panel: st7703: Pick different reset sequence + drm/amdkfd: Fix shift out-of-bounds issue + drm/amdgpu: Fix a null pointer access when the smc_rreg pointer is NULL + arm64: dts: ls208xa: use a pseudo-bus to constrain usb dma size + selftests/efivarfs: create-read: fix a resource leak + ASoC: soc-card: Add storage for PCI SSID + crypto: pcrypt - Fix hungtask for PADATA_RESET + RDMA/hfi1: Use FIELD_GET() to extract Link Width + scsi: hisi_sas: Set debugfs_dir pointer to NULL after removing debugfs + scsi: ibmvfc: Remove BUG_ON in the case of an empty event pool + fs/jfs: Add check for negative db_l2nbperpage + fs/jfs: Add validity check for db_maxag and db_agpref + jfs: fix array-index-out-of-bounds in dbFindLeaf + jfs: fix array-index-out-of-bounds in diAlloc + HID: lenovo: Detect quirk-free fw on cptkbd and stop applying workaround + ARM: 9320/1: fix stack depot IRQ stack filter + ALSA: hda: Fix possible null-ptr-deref when assigning a stream + PCI: tegra194: Use FIELD_GET()/FIELD_PREP() with Link Width fields + atm: iphase: Do PCI error checks on own line + scsi: libfc: Fix potential NULL pointer dereference in fc_lport_ptp_setup() + PCI: Use FIELD_GET() to extract Link Width + PCI: Extract ATS disabling to a helper function + PCI: Disable ATS for specific Intel IPU E2000 devices + misc: pci_endpoint_test: Add Device ID for R-Car S4-8 PCIe controller + PCI: Use FIELD_GET() in Sapphire RX 5600 XT Pulse quirk + HID: Add quirk for Dell Pro Wireless Keyboard and Mouse KM5221W + exfat: support handle zero-size directory + tty: vcc: Add check for kstrdup() in vcc_probe() + usb: gadget: f_ncm: Always set current gadget in ncm_bind() + 9p/trans_fd: Annotate data-racy writes to file::f_flags + 9p: v9fs_listxattr: fix %s null argument warning + i3c: mipi-i3c-hci: Fix out of bounds access in hci_dma_irq_handler + i2c: sun6i-p2wi: Prevent potential division by zero + virtio-blk: fix implicit overflow on virtio_max_dma_size +
[Kernel-packages] [Bug 2050849] [NEW] Jammy update: v5.15.142 upstream stable release
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.15.142 upstream stable release from git://git.kernel.org/ pinctrl: avoid reload of p state in list iteration firewire: core: fix possible memory leak in create_units() mmc: cqhci: Increase recovery halt timeout mmc: cqhci: Warn of halt or task clear failure mmc: cqhci: Fix task clearing in CQE error recovery mmc: block: Retry commands in CQE error recovery mmc: block: Do not lose cache flush during CQE error recovery mmc: block: Be sure to wait while busy in CQE error recovery ALSA: hda: Disable power-save on KONTRON SinglePC ALSA: hda/realtek: Headset Mic VREF to 100% ALSA: hda/realtek: Add supported ALC257 for ChromeOS dm-verity: align struct dm_verity_fec_io properly dm verity: don't perform FEC for failed readahead IO bcache: revert replacing IS_ERR_OR_NULL with IS_ERR iommu/vt-d: Add MTL to quirk list to skip TE disabling powerpc: Don't clobber f0/vs0 during fp|altivec register save parisc: Drop the HP-UX ENOSYM and EREMOTERELEASE error codes btrfs: ref-verify: fix memory leaks in btrfs_ref_tree_mod() btrfs: fix off-by-one when checking chunk map includes logical address btrfs: send: ensure send_fd is writable btrfs: make error messages more clear when getting a chunk map Input: xpad - add HyperX Clutch Gladiate Support vlan: introduce vlan_dev_free_egress_priority vlan: move dev_put into vlan_dev_uninit rcu: Avoid tracing a few functions executed in stop machine hv_netvsc: fix race of netvsc and VF register_netdevice USB: core: Change configuration warnings to notices usb: config: fix iteration issue in 'usb_get_bos_descriptor()' dpaa2-eth: increase the needed headroom to account for alignment uapi: propagate __struct_group() attributes to the container union selftests/net: ipsec: fix constant out of range octeontx2-af: Fix possible buffer overflow net: stmmac: xgmac: Disable FPE MMC interrupts octeontx2-pf: Fix adding mbox work queue entry when num_vfs > 64 Revert "workqueue: remove unused cancel_work()" r8169: prevent potential deadlock in rtl8169_close ravb: Fix races between ravb_tx_timeout_work() and net related ops net: ravb: Check return value of reset_control_deassert() net: ravb: Use pm_runtime_resume_and_get() net: ravb: Start TX queues after HW initialization succeeded net: ravb: Stop DMA in case of failures on ravb_open() perf intel-pt: Fix async branch flags selftests/resctrl: Add missing SPDX license to Makefile selftests/resctrl: Move _GNU_SOURCE define into Makefile smb3: fix touch -h of symlink ASoC: Intel: Move soc_intel_is_foo() helpers to a generic header ASoC: SOF: sof-pci-dev: use community key on all Up boards ASoC: SOF: sof-pci-dev: add parameter to override topology filename ASoC: SOF: sof-pci-dev: don't use the community key on APL Chromebooks ASoC: SOF: sof-pci-dev: Fix community key quirk detection fbdev: stifb: Make the STI next font pointer a 32-bit signed offset fs: add ctime accessors infrastructure smb3: fix caching of ctime on setxattr cpufreq: imx6q: don't warn for disabling a non-existing frequency cpufreq: imx6q: Don't disable 792 Mhz OPP unnecessarily iommu/vt-d: Omit devTLB invalidation requests when TES=0 iommu/vt-d: Make context clearing consistent with context mapping mmc: core: add helpers mmc_regulator_enable/disable_vqmmc mmc: sdhci-sprd: Fix vqmmc not shutting down after the card was pulled r8169: disable ASPM in case of tx timeout r8169: fix deadlock on RTL8125 in jumbo mtu mode iomap: update ki_pos a little later in iomap_dio_complete Linux 5.15.142 UBUNTU: Upstream stable to v5.15.142 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2050849 Title: Jammy update: v5.15.142 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: 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
[Kernel-packages] [Bug 2049442] Re: Enable symbols for all Xilinx device trees
** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2049442 Title: Enable symbols for all Xilinx device trees Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Jammy: Fix Committed Status in linux-xilinx-zynqmp source package in Noble: New Bug description: [ Impact ] * This enables symbols for all device trees built for Xilinx products. * Currently only device trees which have overlays applied have symbols enabled. * Most Xilinx device trees are currently overlayed (thus have the symbols already included) so this should have minimal size impact. [ Test Plan ] * Xilinx will verify they can load the dtbo's for the FPGA during runtime [ Where problems could occur ] * There could be an unexpected impact on other FPGA runtime overlays that are already working. [ Other Info ] * Xilinx platforms apply dtbo's during runtime when loading FPGA firmware. * Xilinx Yocto distribution handle's this in the yocto recipes which is why this change is not upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2049442/+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 2050038] Re: Jammy update: v5.15.140 upstream stable release
** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: - upstream stable patchset 2024-01-22 + v5.15.140 upstream stable release from git://git.kernel.org/ locking/ww_mutex/test: Fix potential workqueue corruption perf/core: Bail out early if the request AUX area is out of bound clocksource/drivers/timer-imx-gpt: Fix potential memory leak clocksource/drivers/timer-atmel-tcb: Fix initialization on SAM9 hardware workqueue: Provide one lock class key per work_on_cpu() callsite x86/mm: Drop the 4 MB restriction on minimal NUMA node memory size wifi: mac80211_hwsim: fix clang-specific fortify warning wifi: mac80211: don't return unset power in ieee80211_get_tx_power() atl1c: Work around the DMA RX overflow issue bpf: Detect IP == ksym.end as part of BPF program wifi: ath9k: fix clang-specific fortify warnings wifi: ath10k: fix clang-specific fortify warning net: annotate data-races around sk->sk_tx_queue_mapping net: annotate data-races around sk->sk_dst_pending_confirm wifi: ath10k: Don't touch the CE interrupt registers after power up Bluetooth: btusb: Add date->evt_skb is NULL check Bluetooth: Fix double free in hci_conn_cleanup platform/x86: thinkpad_acpi: Add battery quirk for Thinkpad X120e drm/komeda: drop all currently held locks if deadlock happens drm/amdkfd: Fix a race condition of vram buffer unref in svm code drm/amd/display: use full update for clip size increase of large plane source string.h: add array-wrappers for (v)memdup_user() kernel: kexec: copy user-array safely kernel: watch_queue: copy user-array safely drm: vmwgfx_surface.c: copy user-array safely drm/msm/dp: skip validity check for DP CTS EDID checksum drm/amd: Fix UBSAN array-index-out-of-bounds for SMU7 drm/amd: Fix UBSAN array-index-out-of-bounds for Polaris and Tonga drm/amdgpu: Fix potential null pointer derefernce drm/panel: fix a possible null pointer dereference drm/panel/panel-tpo-tpg110: fix a possible null pointer dereference drm/amdgpu/vkms: fix a possible null pointer dereference drm/panel: st7703: Pick different reset sequence drm/amdkfd: Fix shift out-of-bounds issue drm/amdgpu: Fix a null pointer access when the smc_rreg pointer is NULL arm64: dts: ls208xa: use a pseudo-bus to constrain usb dma size selftests/efivarfs: create-read: fix a resource leak ASoC: soc-card: Add storage for PCI SSID crypto: pcrypt - Fix hungtask for PADATA_RESET RDMA/hfi1: Use FIELD_GET() to extract Link Width scsi: hisi_sas: Set debugfs_dir pointer to NULL after removing debugfs scsi: ibmvfc: Remove BUG_ON in the case of an empty event pool fs/jfs: Add check for negative db_l2nbperpage fs/jfs: Add validity check for db_maxag and db_agpref jfs: fix array-index-out-of-bounds in dbFindLeaf jfs: fix array-index-out-of-bounds in diAlloc HID: lenovo: Detect quirk-free fw on cptkbd and stop applying workaround ARM: 9320/1: fix stack depot IRQ stack filter ALSA: hda: Fix possible null-ptr-deref when assigning a stream PCI: tegra194: Use FIELD_GET()/FIELD_PREP() with Link Width fields atm: iphase: Do PCI error checks on own line scsi: libfc: Fix potential NULL pointer dereference in fc_lport_ptp_setup() PCI: Use FIELD_GET() to extract Link Width PCI: Extract ATS disabling to a helper function PCI: Disable ATS for specific Intel IPU E2000 devices misc: pci_endpoint_test: Add Device ID for R-Car S4-8 PCIe controller PCI: Use FIELD_GET() in Sapphire RX 5600 XT Pulse quirk HID: Add quirk for Dell Pro Wireless Keyboard and Mouse KM5221W exfat: support handle zero-size directory tty: vcc: Add check for kstrdup() in vcc_probe() usb: gadget: f_ncm: Always set current gadget in ncm_bind() 9p/trans_fd: Annotate data-racy writes to file::f_flags 9p: v9fs_listxattr: fix %s null argument warning i3c: mipi-i3c-hci: Fix out of bounds access in hci_dma_irq_handler i2c: sun6i-p2wi: Prevent potential division by zero virtio-blk: fix implicit overflow on virtio_max_dma_size i3c: master: mipi-i3c-hci: Fix a kernel panic for accessing DAT_data. media: gspca: cpia1: shift-out-of-bounds in set_flicker media: vivid: avoid integer overflow gfs2: ignore negated quota changes gfs2: fix an oops in gfs2_permission media: cobalt: Use FIELD_GET() to extract Link Width media: ccs: Fix driver quirk struct documentation media: imon: fix access to invalid resource for the second interface drm/amd/display: Avoid NULL dereference of timing generator kgdb: Flush console before
[Kernel-packages] [Bug 2050044] [NEW] Jammy update: v5.15.141 upstream stable release
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.15.141 upstream stable release from git://git.kernel.org/ afs: Fix afs_server_list to be cleaned up with RCU afs: Make error on cell lookup failure consistent with OpenAFS drm/panel: boe-tv101wum-nl6: Fine tune the panel power sequence drm/panel: auo,b101uan08.3: Fine tune the panel power sequence drm/panel: simple: Fix Innolux G101ICE-L01 bus flags drm/panel: simple: Fix Innolux G101ICE-L01 timings wireguard: use DEV_STATS_INC() octeontx2-pf: Fix memory leak during interface down ata: pata_isapnp: Add missing error check for devm_ioport_map() drm/rockchip: vop: Fix color for RGB888/BGR888 format on VOP full HID: core: store the unique system identifier in hid_device HID: fix HID device resource race between HID core and debugging support ipv4: Correct/silence an endian warning in __ip_do_redirect net: usb: ax88179_178a: fix failed operations during ax88179_reset net/smc: avoid data corruption caused by decline arm/xen: fix xen_vcpu_info allocation alignment octeontx2-pf: Fix ntuple rule creation to direct packet to VF with higher Rx queue than its PF amd-xgbe: handle corner-case during sfp hotplug amd-xgbe: handle the corner-case during tx completion amd-xgbe: propagate the correct speed and duplex status net: axienet: Fix check for partial TX checksum afs: Return ENOENT if no cell DNS record can be found afs: Fix file locking on R/O volumes to operate in local mode nvmet: nul-terminate the NQNs passed in the connect command USB: dwc3: qcom: fix resource leaks on probe deferral USB: dwc3: qcom: fix ACPI platform device leak lockdep: Fix block chain corruption MIPS: KVM: Fix a build warning about variable set but not used media: camss: Replace hard coded value with parameter media: camss: sm8250: Virtual channels for CSID media: qcom: camss: Fix set CSI2_RX_CFG1_VC_MODE when VC is greater than 3 media: qcom: camss: Fix csid-gen2 for test pattern generator ext4: add a new helper to check if es must be kept ext4: factor out __es_alloc_extent() and __es_free_extent() ext4: use pre-allocated es in __es_insert_extent() ext4: use pre-allocated es in __es_remove_extent() ext4: using nofail preallocation in ext4_es_remove_extent() ext4: using nofail preallocation in ext4_es_insert_delayed_block() ext4: using nofail preallocation in ext4_es_insert_extent() ext4: fix slab-use-after-free in ext4_es_insert_extent() ext4: make sure allocate pending entry not fail proc: sysctl: prevent aliased sysctls from getting passed to init ACPI: resource: Skip IRQ override on ASUS ExpertBook B1402CVA swiotlb-xen: provide the "max_mapping_size" method bcache: replace a mistaken IS_ERR() by IS_ERR_OR_NULL() in btree_gc_coalesce() md: fix bi_status reporting in md_end_clone_io bcache: fixup multi-threaded bch_sectors_dirty_init() wake-up race io_uring/fs: consider link->flags when getting path for LINKAT s390/dasd: protect device queue against concurrent access USB: serial: option: add Luat Air72*U series products hv_netvsc: Fix race of register_netdevice_notifier and VF register hv_netvsc: Mark VF as slave before exposing it to user-mode dm-delay: fix a race between delay_presuspend and delay_bio bcache: check return value from btree_node_alloc_replacement() bcache: prevent potential division by zero error bcache: fixup init dirty data errors bcache: fixup lock c->root error usb: cdnsp: Fix deadlock issue during using NCM gadget USB: serial: option: add Fibocom L7xx modules USB: serial: option: fix FM101R-GL defines USB: serial: option: don't claim interface 4 for ZTE MF290 usb: typec: tcpm: Skip hard reset when in error recovery USB: dwc2: write HCINT with INTMASK applied usb: dwc3: Fix default mode initialization usb: dwc3: set the dma max_seg_size USB: dwc3: qcom: fix software node leak on probe errors USB: dwc3: qcom: fix wakeup after probe deferral io_uring: fix off-by one bvec index Linux 5.15.141 UBUNTU: Upstream stable to v5.15.141 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Portia Stephens (portias) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Summary changed: - Jammy update: upstream stable patchset 2024-01-22 + Jammy update: v5.15.141 upstream stable release ** Description changed: + SRU Justifi
[Kernel-packages] [Bug 2050038] Re: Jammy update: v5.15.140 upstream stable release
** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Portia Stephens (portias) ** Changed in: linux (Ubuntu) Status: Confirmed => 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/2050038 Title: Jammy update: v5.15.140 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2024-01-22 from git://git.kernel.org/ locking/ww_mutex/test: Fix potential workqueue corruption perf/core: Bail out early if the request AUX area is out of bound clocksource/drivers/timer-imx-gpt: Fix potential memory leak clocksource/drivers/timer-atmel-tcb: Fix initialization on SAM9 hardware workqueue: Provide one lock class key per work_on_cpu() callsite x86/mm: Drop the 4 MB restriction on minimal NUMA node memory size wifi: mac80211_hwsim: fix clang-specific fortify warning wifi: mac80211: don't return unset power in ieee80211_get_tx_power() atl1c: Work around the DMA RX overflow issue bpf: Detect IP == ksym.end as part of BPF program wifi: ath9k: fix clang-specific fortify warnings wifi: ath10k: fix clang-specific fortify warning net: annotate data-races around sk->sk_tx_queue_mapping net: annotate data-races around sk->sk_dst_pending_confirm wifi: ath10k: Don't touch the CE interrupt registers after power up Bluetooth: btusb: Add date->evt_skb is NULL check Bluetooth: Fix double free in hci_conn_cleanup platform/x86: thinkpad_acpi: Add battery quirk for Thinkpad X120e drm/komeda: drop all currently held locks if deadlock happens drm/amdkfd: Fix a race condition of vram buffer unref in svm code drm/amd/display: use full update for clip size increase of large plane source string.h: add array-wrappers for (v)memdup_user() kernel: kexec: copy user-array safely kernel: watch_queue: copy user-array safely drm: vmwgfx_surface.c: copy user-array safely drm/msm/dp: skip validity check for DP CTS EDID checksum drm/amd: Fix UBSAN array-index-out-of-bounds for SMU7 drm/amd: Fix UBSAN array-index-out-of-bounds for Polaris and Tonga drm/amdgpu: Fix potential null pointer derefernce drm/panel: fix a possible null pointer dereference drm/panel/panel-tpo-tpg110: fix a possible null pointer dereference drm/amdgpu/vkms: fix a possible null pointer dereference drm/panel: st7703: Pick different reset sequence drm/amdkfd: Fix shift out-of-bounds issue drm/amdgpu: Fix a null pointer access when the smc_rreg pointer is NULL arm64: dts: ls208xa: use a pseudo-bus to constrain usb dma size selftests/efivarfs: create-read: fix a resource leak ASoC: soc-card: Add storage for PCI SSID crypto: pcrypt - Fix hungtask for PADATA_RESET RDMA/hfi1: Use FIELD_GET() to extract Link Width scsi: hisi_sas: Set debugfs_dir pointer to NULL after removing debugfs scsi: ibmvfc: Remove BUG_ON in the case of an empty event pool fs/jfs: Add check for negative db_l2nbperpage fs/jfs: Add validity check for db_maxag and db_agpref jfs: fix array-index-out-of-bounds in dbFindLeaf jfs: fix array-index-out-of-bounds in diAlloc HID: lenovo: Detect quirk-free fw on cptkbd and stop applying workaround ARM: 9320/1: fix stack depot IRQ stack filter ALSA: hda: Fix possible null-ptr-deref when assigning a stream PCI: tegra194: Use FIELD_GET()/FIELD_PREP() with Link Width fields atm: iphase: Do PCI error checks on own line scsi: libfc: Fix potential NULL pointer dereference in fc_lport_ptp_setup() PCI: Use FIELD_GET() to extract Link Width PCI: Extract ATS disabling to a helper function PCI: Disable ATS for specific Intel IPU E2000 devices misc: pci_endpoint_test: Add Device ID for R-Car S4-8 PCIe controller PCI: Use FIELD_GET() in Sapphire RX 5600 XT Pulse quirk HID: Add quirk for Dell Pro Wireless Keyboard and Mouse KM5221W exfat: support handle zero-size directory tty: vcc: Add check for kstrdup() in vcc_probe() usb: gadget: f_ncm: Always set current gadget in ncm_bind() 9p/trans_fd: Annotate data-racy writes to file::f_flags 9p: v9fs_listxattr: fix %s null argument warning i3c: mipi-i3c-hci: Fix out of bounds access in hci_dma_irq_handler i2c: sun6i-p2wi: Prevent potential divi
[Kernel-packages] [Bug 2050038] [NEW] Jammy update: v5.15.140 upstream stable release
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: upstream stable patchset 2024-01-22 from git://git.kernel.org/ locking/ww_mutex/test: Fix potential workqueue corruption perf/core: Bail out early if the request AUX area is out of bound clocksource/drivers/timer-imx-gpt: Fix potential memory leak clocksource/drivers/timer-atmel-tcb: Fix initialization on SAM9 hardware workqueue: Provide one lock class key per work_on_cpu() callsite x86/mm: Drop the 4 MB restriction on minimal NUMA node memory size wifi: mac80211_hwsim: fix clang-specific fortify warning wifi: mac80211: don't return unset power in ieee80211_get_tx_power() atl1c: Work around the DMA RX overflow issue bpf: Detect IP == ksym.end as part of BPF program wifi: ath9k: fix clang-specific fortify warnings wifi: ath10k: fix clang-specific fortify warning net: annotate data-races around sk->sk_tx_queue_mapping net: annotate data-races around sk->sk_dst_pending_confirm wifi: ath10k: Don't touch the CE interrupt registers after power up Bluetooth: btusb: Add date->evt_skb is NULL check Bluetooth: Fix double free in hci_conn_cleanup platform/x86: thinkpad_acpi: Add battery quirk for Thinkpad X120e drm/komeda: drop all currently held locks if deadlock happens drm/amdkfd: Fix a race condition of vram buffer unref in svm code drm/amd/display: use full update for clip size increase of large plane source string.h: add array-wrappers for (v)memdup_user() kernel: kexec: copy user-array safely kernel: watch_queue: copy user-array safely drm: vmwgfx_surface.c: copy user-array safely drm/msm/dp: skip validity check for DP CTS EDID checksum drm/amd: Fix UBSAN array-index-out-of-bounds for SMU7 drm/amd: Fix UBSAN array-index-out-of-bounds for Polaris and Tonga drm/amdgpu: Fix potential null pointer derefernce drm/panel: fix a possible null pointer dereference drm/panel/panel-tpo-tpg110: fix a possible null pointer dereference drm/amdgpu/vkms: fix a possible null pointer dereference drm/panel: st7703: Pick different reset sequence drm/amdkfd: Fix shift out-of-bounds issue drm/amdgpu: Fix a null pointer access when the smc_rreg pointer is NULL arm64: dts: ls208xa: use a pseudo-bus to constrain usb dma size selftests/efivarfs: create-read: fix a resource leak ASoC: soc-card: Add storage for PCI SSID crypto: pcrypt - Fix hungtask for PADATA_RESET RDMA/hfi1: Use FIELD_GET() to extract Link Width scsi: hisi_sas: Set debugfs_dir pointer to NULL after removing debugfs scsi: ibmvfc: Remove BUG_ON in the case of an empty event pool fs/jfs: Add check for negative db_l2nbperpage fs/jfs: Add validity check for db_maxag and db_agpref jfs: fix array-index-out-of-bounds in dbFindLeaf jfs: fix array-index-out-of-bounds in diAlloc HID: lenovo: Detect quirk-free fw on cptkbd and stop applying workaround ARM: 9320/1: fix stack depot IRQ stack filter ALSA: hda: Fix possible null-ptr-deref when assigning a stream PCI: tegra194: Use FIELD_GET()/FIELD_PREP() with Link Width fields atm: iphase: Do PCI error checks on own line scsi: libfc: Fix potential NULL pointer dereference in fc_lport_ptp_setup() PCI: Use FIELD_GET() to extract Link Width PCI: Extract ATS disabling to a helper function PCI: Disable ATS for specific Intel IPU E2000 devices misc: pci_endpoint_test: Add Device ID for R-Car S4-8 PCIe controller PCI: Use FIELD_GET() in Sapphire RX 5600 XT Pulse quirk HID: Add quirk for Dell Pro Wireless Keyboard and Mouse KM5221W exfat: support handle zero-size directory tty: vcc: Add check for kstrdup() in vcc_probe() usb: gadget: f_ncm: Always set current gadget in ncm_bind() 9p/trans_fd: Annotate data-racy writes to file::f_flags 9p: v9fs_listxattr: fix %s null argument warning i3c: mipi-i3c-hci: Fix out of bounds access in hci_dma_irq_handler i2c: sun6i-p2wi: Prevent potential division by zero virtio-blk: fix implicit overflow on virtio_max_dma_size i3c: master: mipi-i3c-hci: Fix a kernel panic for accessing DAT_data. media: gspca: cpia1: shift-out-of-bounds in set_flicker media: vivid: avoid integer overflow gfs2: ignore negated quota changes gfs2: fix an oops in gfs2_permission media: cobalt: Use FIELD_GET() to extract Link Width media: ccs: Fix driver quirk struct documentation media: imon: fix access to invalid resource for the second interface drm/amd/display: Avoid NULL dereference of timing generator kgdb: Flush console before entering kgdb on panic i2c: dev: copy userspace array safely ASoC: ti: omap-mcbsp: Fix runtime PM underflow warnings drm/qxl: prevent memory leak drm/amdgpu: fix software pci_unplug on some chips pwm: Fix double shift bug wifi:
[Kernel-packages] [Bug 2049442] [NEW] Enable symbols for all Xilinx device trees
Public bug reported: [ Impact ] * This enables symbols for all device trees built for Xilinx products. * Currently only device trees which have overlays applied have symbols enabled. * Most Xilinx device trees are currently overlayed (thus have the symbols already included) so this should have minimal size impact. [ Test Plan ] * Xilinx will verify they can load the dtbo's for the FPGA during runtime [ Where problems could occur ] * There could be an unexpected impact on other FPGA runtime overlays that are already working. [ Other Info ] * Xilinx platforms apply dtbo's during runtime when loading FPGA firmware. * Xilinx Yocto distribution handle's this in the yocto recipes which is why this change is not upstream. ** Affects: linux-xilinx-zynqmp (Ubuntu) Importance: Undecided Status: New ** Affects: linux-xilinx-zynqmp (Ubuntu Jammy) Importance: Undecided Assignee: Portia Stephens (portias) Status: New ** Affects: linux-xilinx-zynqmp (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-xilinx-zynqmp (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-xilinx-zynqmp (Ubuntu Noble) Importance: Undecided Status: New ** Description changed: [ Impact ] - * This enables symbols for all device trees built for Xilinx products. + * This enables symbols for all device trees built for Xilinx products. * Currently only device trees which have overlays applied have symbols enabled. - * Most Xilinx device trees are currently overlayed (thus have the symbols already included) so this should have minimal size impact. + * Most Xilinx device trees are currently overlayed (thus have the symbols already included) so this should have minimal size impact. [ Test Plan ] * Xilinx will verify they can load the dtbo's for the FPGA during runtime [ Where problems could occur ] * There could be an unexpected impact on other FPGA runtime overlays that are already working. + [ Other Info ] - [ Other Info ] * Xilinx platforms apply dtbo's during runtime when loading FPGA firmware. + * Xilinx Yocto distribution handle's this in the yocto recipes which is why this change is not upstream. ** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy) Assignee: (unassigned) => Portia Stephens (portias) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2049442 Title: Enable symbols for all Xilinx device trees Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Jammy: New Status in linux-xilinx-zynqmp source package in Noble: New Bug description: [ Impact ] * This enables symbols for all device trees built for Xilinx products. * Currently only device trees which have overlays applied have symbols enabled. * Most Xilinx device trees are currently overlayed (thus have the symbols already included) so this should have minimal size impact. [ Test Plan ] * Xilinx will verify they can load the dtbo's for the FPGA during runtime [ Where problems could occur ] * There could be an unexpected impact on other FPGA runtime overlays that are already working. [ Other Info ] * Xilinx platforms apply dtbo's during runtime when loading FPGA firmware. * Xilinx Yocto distribution handle's this in the yocto recipes which is why this change is not upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2049442/+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 2044554] Re: Turn off non-zynqmp arch support
** Also affects: linux-xilinx-zynqmp (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2044554 Title: Turn off non-zynqmp arch support Status in linux-xilinx-zynqmp package in Ubuntu: Fix Committed Status in linux-xilinx-zynqmp source package in Jammy: New Bug description: [ Impact ] * This is an optimized kernel for zynqmp range of devices. * Currently about 14% of kernel build is targeting non-zynqmp devices, which is dead code unused in production * This reduces kernel build time, kernel image & modules size, amount of required firmware, and makes initrd smaller. * This reduces peak memory usage on boot as well * This will loose ability to execute this exact same kernel build on non-zynqmp device, for benchmarking purposes generic kernel should be used instead. [ Test Plan ] * Ensure newly produced kernel installs and boots on Ubuntu Server and Ubuntu Core target devices without any loss of peripherals and stock devices. [ Where problems could occur ] * This changes may limit ability to smoke-test this kernel on non-zynqmp devices, if needed support for individual CPUs can be turned back on. Or ideally any such testing should move to zynqmp devices. (examples of potentially interesting things to turn back on upon request are QCOM APPLE suppport for running this kernel on Arm Laptops for developer convenience) * It is expected for KVM and QEMU to continue to work as both host and guest [ Other Info ] * Anything else you think is useful to include * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board * and address these questions in advance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2044554/+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 2044554] Re: Turn off non-zynqmp arch support
** Changed in: linux-xilinx-zynqmp (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2044554 Title: Turn off non-zynqmp arch support Status in linux-xilinx-zynqmp package in Ubuntu: Fix Committed Status in linux-xilinx-zynqmp source package in Jammy: New Bug description: [ Impact ] * This is an optimized kernel for zynqmp range of devices. * Currently about 14% of kernel build is targeting non-zynqmp devices, which is dead code unused in production * This reduces kernel build time, kernel image & modules size, amount of required firmware, and makes initrd smaller. * This reduces peak memory usage on boot as well * This will loose ability to execute this exact same kernel build on non-zynqmp device, for benchmarking purposes generic kernel should be used instead. [ Test Plan ] * Ensure newly produced kernel installs and boots on Ubuntu Server and Ubuntu Core target devices without any loss of peripherals and stock devices. [ Where problems could occur ] * This changes may limit ability to smoke-test this kernel on non-zynqmp devices, if needed support for individual CPUs can be turned back on. Or ideally any such testing should move to zynqmp devices. (examples of potentially interesting things to turn back on upon request are QCOM APPLE suppport for running this kernel on Arm Laptops for developer convenience) * It is expected for KVM and QEMU to continue to work as both host and guest [ Other Info ] * Anything else you think is useful to include * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board * and address these questions in advance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2044554/+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 2046280] Re: Add support for KD240 platform
** Changed in: linux-xilinx-zynqmp (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2046280 Title: Add support for KD240 platform Status in linux-xilinx-zynqmp package in Ubuntu: Fix Committed Bug description: [ Impact ] * This change adds support for the KD240 Kria platform. * It is the same SoC as other Kria/ZCU platforms * This change will enable us to certify the KD240 platform with the linux-xilinx-zynqmp kernel [ Test Plan ] * Normal regression testing and certification testing will be run on currently certified platform * A release candidate KD240 image will be generated from -proposed and QA will run certification testing on it [ Where problems could occur ] * The device tree changes include changes to dtsi's used by other certified Xilinx platforms. [ Other Info ] * KD240 changes are backported from Xilinx 6.1 tree. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280/+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 2049350] [NEW] Jammy update: v5.15.137 upstream stable release
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:
upstream stable patchset 2024-01-15
from git://git.kernel.org/
lib/Kconfig.debug: do not enable DEBUG_PREEMPT by default
Documentation: sysctl: align cells in second content column
xfs: don't expose internal symlink metadata buffers to the vfs
Bluetooth: hci_event: Ignore NULL link key
Bluetooth: Reject connection with the device which has same BD_ADDR
Bluetooth: Fix a refcnt underflow problem for hci_conn
Bluetooth: vhci: Fix race when opening vhci device
Bluetooth: hci_event: Fix coding style
Bluetooth: avoid memcmp() out of bounds warning
ice: fix over-shifted variable
ice: reset first in crash dump kernels
nfc: nci: fix possible NULL pointer dereference in send_acknowledge()
regmap: fix NULL deref on lookup
KVM: x86: Mask LVTPC when handling a PMI
tcp: check mptcp-level constraints for backlog coalescing
fs/ntfs3: Fix possible null-pointer dereference in hdr_find_e()
fs/ntfs3: fix panic about slab-out-of-bounds caused by ntfs_list_ea()
fs/ntfs3: fix deadlock in mark_as_free_ex
netfilter: nft_payload: fix wrong mac header matching
drm/i915: Retry gtt fault when out of fence registers
ASoC: codecs: wcd938x-sdw: fix use after free on driver unbind
ASoC: codecs: wcd938x-sdw: fix runtime PM imbalance on probe errors
ASoC: codecs: wcd938x: drop bogus bind error handling
ASoC: codecs: wcd938x: fix unbind tear down order
qed: fix LL2 RX buffer allocation
xfrm: fix a data-race in xfrm_gen_index()
xfrm: interface: use DEV_STATS_INC()
net: ipv4: fix return value check in esp_remove_trailer
net: ipv6: fix return value check in esp_remove_trailer
net: rfkill: gpio: prevent value glitch during probe
tcp: fix excessive TLP and RACK timeouts from HZ rounding
tcp: tsq: relax tcp_small_queue_check() when rtx queue contains a single skb
tun: prevent negative ifindex
ipv4: fib: annotate races around nh->nh_saddr_genid and nh->nh_saddr
net: usb: smsc95xx: Fix an error code in smsc95xx_reset()
i40e: prevent crash on probe if hw registers have invalid values
net: dsa: bcm_sf2: Fix possible memory leak in bcm_sf2_mdio_register()
bonding: Return pointer to data after pull on skb
net/sched: sch_hfsc: upgrade 'rt' to 'sc' when it becomes a inner curve
neighbor: tracing: Move pin6 inside CONFIG_IPV6=y section
netfilter: nft_set_rbtree: .deactivate fails if element has expired
netfilter: nf_tables: do not remove elements if set backend implements .abort
netfilter: nf_tables: revert do not remove elements if set backend implements
.abort
net: pktgen: Fix interface flags printing
selftests/mm: fix awk usage in charge_reserved_hugetlb.sh and
hugetlb_reparenting_test.sh that may cause error
serial: 8250: omap: Fix imprecise external abort for omap_8250_pm()
serial: 8250_omap: Fix errors with no_console_suspend
iio: Un-inline iio_buffer_enabled()
iio: core: Hide read accesses to iio_dev->currentmode
iio: core: introduce iio_device_{claim|release}_buffer_mode() APIs
iio: cros_ec: fix an use-after-free in cros_ec_sensors_push_data()
iio: adc: ad7192: Correct reference voltage
perf: Add irq and exception return branch types
perf/x86: Move branch classifier
perf/x86/lbr: Filter vsyscall addresses
drm/atomic-helper: relax unregistered connector check
powerpc/32s: Remove capability to disable KUEP at boottime
powerpc/32s: Do kuep_lock() and kuep_unlock() in assembly
powerpc/47x: Fix 47x syscall return crash
mctp: Allow local delivery to the null EID
mctp: perform route lookups under a RCU read-side lock
nfp: flower: avoid rmmod nfp crash issues
ksmbd: not allow to open file if delelete on close bit is set
ARM: dts: ti: omap: Fix noisy serial with overrun-throttle-ms for mapphone
fs-writeback: do not requeue a clean inode having skipped pages
btrfs: return -EUCLEAN for delayed tree ref with a ref count not equals to 1
btrfs: initialize start_slot in btrfs_log_prealloc_extents
i2c: mux: Avoid potential false error message in i2c_mux_add_adapter
overlayfs: set ctime when setting mtime and atime
gpio: timberdale: Fix potential deadlock on >lock
ata: libata-core: Fix compilation warning in ata_dev_config_ncq()
ata: libata-eh: Fix compilation warning in ata_eh_link_report()
tracing: relax trace_event_eval_update() execution with cond_resched()
wifi: mwifiex: Sanity check tlv_len and tlv_bitmap_len
wifi: iwlwifi: Ensure ack flag is properly cleared.
HID: holtek: fix slab-out-of-bounds Write in holtek_kbd_input_event
Bluetooth: btusb: add shutdown function for QCA6174
Bluetooth: Avoid redundant authentication
Bluetooth: hci_core: Fix build warnings
wifi: cfg80211: Fix
[Kernel-packages] [Bug 2048737] Re: Lunar update: upstream stable patchset 2024-01-09
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Lunar) 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/2048737 Title: Lunar update: upstream stable patchset 2024-01-09 Status in linux package in Ubuntu: Invalid Status in linux source package in Lunar: Invalid Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2024-01-09 Ported from the following upstream stable releases: v6.1.58 v6.1.59, v6.5.8 from git://git.kernel.org/ Revert "NFS: More fixes for nfs_direct_write_reschedule_io()" lib/test_meminit: fix off-by-one error in test_pages() drm/i915: Don't set PIPE_CONTROL_FLUSH_L3 for aux inval RDMA/cxgb4: Check skb value for failure to allocate perf/arm-cmn: Fix the unhandled overflow status of counter 4 to 7 platform/x86: think-lmi: Fix reference leak platform/x86: hp-wmi:: Mark driver struct with __refdata to prevent section mismatch warning scsi: Do not rescan devices with a suspended queue HID: logitech-hidpp: Fix kernel crash on receiver USB disconnect quota: Fix slow quotaoff ASoC: amd: yc: Fix non-functional mic on Lenovo 82YM ata: libata-scsi: Disable scsi device manage_system_start_stop net: prevent address rewrite in kernel_bind() arm64: dts: qcom: sm8150: extend the size of the PDC resource dt-bindings: interrupt-controller: renesas,rzg2l-irqc: Update description for '#interrupt-cells' property irqchip: renesas-rzg2l: Fix logic to clear TINT interrupt source KEYS: trusted: Remove redundant static calls usage ALSA: usb-audio: Fix microphone sound on Opencomm2 Headset ALSA: usb-audio: Fix microphone sound on Nexigo webcam. ASoC: SOF: amd: fix for firmware reload failure after playback ASoC: simple-card-utils: fixup simple_util_startup() error handling ASoC: Intel: soc-acpi: Add entry for HDMI_In capture support in MTL match table ASoC: Intel: sof_sdw: add support for SKU 0B14 ASoC: Intel: soc-acpi: Add entry for sof_es8336 in MTL match table. ASoC: Use of_property_read_bool() for boolean properties ASoC: fsl_sai: MCLK bind with TX/RX enable bit ASoC: fsl_sai: Don't disable bitclock for i.MX8MP ALSA: hda/realtek: Add quirk for HP Victus 16-d1xxx to enable mute LED ALSA: hda/realtek: Add quirk for mute LEDs on HP ENVY x360 15-eu0xxx ALSA: hda/realtek - ALC287 merge RTK codec with CS CS35L41 AMP pinctrl: nuvoton: wpcm450: fix out of bounds write drm/msm/dp: do not reinitialize phy unless retry during link training drm/msm/dsi: skip the wait for video mode done if not applicable drm/msm/dsi: fix irq_of_parse_and_map() error checking drm/msm/dpu: change _dpu_plane_calc_bw() to use u64 to avoid overflow drm/msm/dp: Add newlines to debug printks phy: lynx-28g: cancel the CDR check work item on the remove path phy: lynx-28g: lock PHY while performing CDR lock workaround phy: lynx-28g: serialize concurrent phy_set_mode_ext() calls to shared registers net: dsa: qca8k: fix potential MDIO bus conflict when accessing internal PHYs via management frames can: isotp: isotp_sendmsg(): fix TX state detection and wait behavior can: sun4i_can: Only show Kconfig if ARCH_SUNXI is set UBUNTU: [Config]: remove CAN_SUN4I arm64: dts: mediatek: mt8195: Set DSU PMU status to fail ravb: Fix up dma_free_coherent() call in ravb_remove() ravb: Fix use-after-free issue in ravb_tx_timeout_work() ieee802154: ca8210: Fix a potential UAF in ca8210_probe mlxsw: fix mlxsw_sp2_nve_vxlan_learning_set() return type xen-netback: use default TX queue size for vifs riscv, bpf: Factor out emit_call for kernel and bpf context riscv, bpf: Sign-extend return values drm/vmwgfx: fix typo of sizeof argument bpf: Fix verifier log for async callback return values net: refine debug info in skb_checksum_help() net: macsec: indicate next pn update when offloading net: phy: mscc: macsec: reject PN update requests net/mlx5e: macsec: use update_pn flag instead of PN comparation ixgbe: fix crash with empty VF macvlan list net/mlx5e: Again mutually exclude RX-FCS and RX-port-timestamp net: nfc: fix races in nfc_llcp_sock_get() and nfc_llcp_sock_get_sn() pinctrl: renesas: rzn1: Enable missing PINMUX nfc: nci: assert requested protocol is valid workqueue: Override implicit ordered attribute in
[Kernel-packages] [Bug 2048737] [NEW] Lunar update: upstream stable patchset 2024-01-09
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: upstream stable patchset 2024-01-09 Ported from the following upstream stable releases: v6.1.58 v6.1.59, v6.5.8 from git://git.kernel.org/ Revert "NFS: More fixes for nfs_direct_write_reschedule_io()" lib/test_meminit: fix off-by-one error in test_pages() drm/i915: Don't set PIPE_CONTROL_FLUSH_L3 for aux inval RDMA/cxgb4: Check skb value for failure to allocate perf/arm-cmn: Fix the unhandled overflow status of counter 4 to 7 platform/x86: think-lmi: Fix reference leak platform/x86: hp-wmi:: Mark driver struct with __refdata to prevent section mismatch warning scsi: Do not rescan devices with a suspended queue HID: logitech-hidpp: Fix kernel crash on receiver USB disconnect quota: Fix slow quotaoff ASoC: amd: yc: Fix non-functional mic on Lenovo 82YM ata: libata-scsi: Disable scsi device manage_system_start_stop net: prevent address rewrite in kernel_bind() arm64: dts: qcom: sm8150: extend the size of the PDC resource dt-bindings: interrupt-controller: renesas,rzg2l-irqc: Update description for '#interrupt-cells' property irqchip: renesas-rzg2l: Fix logic to clear TINT interrupt source KEYS: trusted: Remove redundant static calls usage ALSA: usb-audio: Fix microphone sound on Opencomm2 Headset ALSA: usb-audio: Fix microphone sound on Nexigo webcam. ASoC: SOF: amd: fix for firmware reload failure after playback ASoC: simple-card-utils: fixup simple_util_startup() error handling ASoC: Intel: soc-acpi: Add entry for HDMI_In capture support in MTL match table ASoC: Intel: sof_sdw: add support for SKU 0B14 ASoC: Intel: soc-acpi: Add entry for sof_es8336 in MTL match table. ASoC: Use of_property_read_bool() for boolean properties ASoC: fsl_sai: MCLK bind with TX/RX enable bit ASoC: fsl_sai: Don't disable bitclock for i.MX8MP ALSA: hda/realtek: Add quirk for HP Victus 16-d1xxx to enable mute LED ALSA: hda/realtek: Add quirk for mute LEDs on HP ENVY x360 15-eu0xxx ALSA: hda/realtek - ALC287 merge RTK codec with CS CS35L41 AMP pinctrl: nuvoton: wpcm450: fix out of bounds write drm/msm/dp: do not reinitialize phy unless retry during link training drm/msm/dsi: skip the wait for video mode done if not applicable drm/msm/dsi: fix irq_of_parse_and_map() error checking drm/msm/dpu: change _dpu_plane_calc_bw() to use u64 to avoid overflow drm/msm/dp: Add newlines to debug printks phy: lynx-28g: cancel the CDR check work item on the remove path phy: lynx-28g: lock PHY while performing CDR lock workaround phy: lynx-28g: serialize concurrent phy_set_mode_ext() calls to shared registers net: dsa: qca8k: fix potential MDIO bus conflict when accessing internal PHYs via management frames can: isotp: isotp_sendmsg(): fix TX state detection and wait behavior can: sun4i_can: Only show Kconfig if ARCH_SUNXI is set UBUNTU: [Config]: remove CAN_SUN4I arm64: dts: mediatek: mt8195: Set DSU PMU status to fail ravb: Fix up dma_free_coherent() call in ravb_remove() ravb: Fix use-after-free issue in ravb_tx_timeout_work() ieee802154: ca8210: Fix a potential UAF in ca8210_probe mlxsw: fix mlxsw_sp2_nve_vxlan_learning_set() return type xen-netback: use default TX queue size for vifs riscv, bpf: Factor out emit_call for kernel and bpf context riscv, bpf: Sign-extend return values drm/vmwgfx: fix typo of sizeof argument bpf: Fix verifier log for async callback return values net: refine debug info in skb_checksum_help() net: macsec: indicate next pn update when offloading net: phy: mscc: macsec: reject PN update requests net/mlx5e: macsec: use update_pn flag instead of PN comparation ixgbe: fix crash with empty VF macvlan list net/mlx5e: Again mutually exclude RX-FCS and RX-port-timestamp net: nfc: fix races in nfc_llcp_sock_get() and nfc_llcp_sock_get_sn() pinctrl: renesas: rzn1: Enable missing PINMUX nfc: nci: assert requested protocol is valid workqueue: Override implicit ordered attribute in workqueue_apply_unbound_cpumask() tcp: enforce receive buffer memory limits by allowing the tcp window to shrink dmaengine: stm32-mdma: abort resume if no ongoing transfer dmaengine: stm32-dma: fix stm32_dma_prep_slave_sg in case of MDMA chaining dmaengine: stm32-dma: fix residue in case of MDMA chaining dmaengine: stm32-mdma: use Link Address Register to compute residue dmaengine: stm32-mdma: set in_flight_bytes in case CRQA flag is set usb: xhci: xhci-ring: Use sysdev for mapping bounce buffer net: usb: dm9601: fix uninitialized variable use in dm9601_mdio_read usb: dwc3: Soft reset phy on probe for host
[Kernel-packages] [Bug 2048736] [NEW] Lunar update: upstream stable patchset 2024-01-09
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: upstream stable patchset 2024-01-09 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug -- 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/2048736 Title: Lunar update: upstream stable patchset 2024-01-09 Status in linux package in Ubuntu: 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: upstream stable patchset 2024-01-09 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2048736/+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 2044554] Re: Turn off non-zynqmp arch support
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2044554 Title: Turn off non-zynqmp arch support Status in linux-xilinx-zynqmp package in Ubuntu: In Progress Bug description: [ Impact ] * This is an optimized kernel for zynqmp range of devices. * Currently about 14% of kernel build is targeting non-zynqmp devices, which is dead code unused in production * This reduces kernel build time, kernel image & modules size, amount of required firmware, and makes initrd smaller. * This reduces peak memory usage on boot as well * This will loose ability to execute this exact same kernel build on non-zynqmp device, for benchmarking purposes generic kernel should be used instead. [ Test Plan ] * Ensure newly produced kernel installs and boots on Ubuntu Server and Ubuntu Core target devices without any loss of peripherals and stock devices. [ Where problems could occur ] * This changes may limit ability to smoke-test this kernel on non-zynqmp devices, if needed support for individual CPUs can be turned back on. Or ideally any such testing should move to zynqmp devices. (examples of potentially interesting things to turn back on upon request are QCOM APPLE suppport for running this kernel on Arm Laptops for developer convenience) * It is expected for KVM and QEMU to continue to work as both host and guest [ Other Info ] * Anything else you think is useful to include * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board * and address these questions in advance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2044554/+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 2046280] Re: Add support for KD240 platform
** Summary changed: - Add support for Kd240 platform + Add support for KD240 platform ** Changed in: linux-xilinx-zynqmp (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2046280 Title: Add support for KD240 platform Status in linux-xilinx-zynqmp package in Ubuntu: In Progress Bug description: [ Impact ] * This change adds support for the KD240 Kria platform. * It is the same SoC as other Kria/ZCU platforms * This change will enable us to certify the KD240 platform with the linux-xilinx-zynqmp kernel [ Test Plan ] * Normal regression testing and certification testing will be run on currently certified platform * A release candidate KD240 image will be generated from -proposed and QA will run certification testing on it [ Where problems could occur ] * The device tree changes include changes to dtsi's used by other certified Xilinx platforms. [ Other Info ] * KD240 changes are backported from Xilinx 6.1 tree. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280/+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 2046280] [NEW] Add support for Kd240 platform
Public bug reported: [ Impact ] * This change adds support for the KD240 Kria platform. * It is the same SoC as other Kria/ZCU platforms * This change will enable us to certify the KD240 platform with the linux-xilinx-zynqmp kernel [ Test Plan ] * Normal regression testing and certification testing will be run on currently certified platform * A release candidate KD240 image will be generated from -proposed and QA will run certification testing on it [ Where problems could occur ] * The device tree changes include changes to dtsi's used by other certified Xilinx platforms. [ Other Info ] * KD240 changes are backported from Xilinx 6.1 tree. ** Affects: linux-xilinx-zynqmp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2046280 Title: Add support for Kd240 platform Status in linux-xilinx-zynqmp package in Ubuntu: New Bug description: [ Impact ] * This change adds support for the KD240 Kria platform. * It is the same SoC as other Kria/ZCU platforms * This change will enable us to certify the KD240 platform with the linux-xilinx-zynqmp kernel [ Test Plan ] * Normal regression testing and certification testing will be run on currently certified platform * A release candidate KD240 image will be generated from -proposed and QA will run certification testing on it [ Where problems could occur ] * The device tree changes include changes to dtsi's used by other certified Xilinx platforms. [ Other Info ] * KD240 changes are backported from Xilinx 6.1 tree. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280/+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 2045220] [NEW] Focal update: v5.4.258 upstream stable release
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:
upstream stable patchset 2023-11-30
from git://git.kernel.org/
NFS/pNFS: Report EINVAL errors from connect() to the server
SUNRPC: Mark the cred for revalidation if the server rejects it
tracing: Increase trace array ref count on enable and filter files
ata: libahci: clear pending interrupt status
ext4: remove the 'group' parameter of ext4_trim_extent
ext4: add new helper interface ext4_try_to_trim_range()
ext4: scope ret locally in ext4_try_to_trim_range()
ext4: change s_last_trim_minblks type to unsigned long
ext4: mark group as trimmed only if it was fully scanned
ext4: replace the traditional ternary conditional operator with with max()/min()
ext4: move setting of trimmed bit into ext4_try_to_trim_range()
ext4: do not let fstrim block system suspend
ASoC: meson: spdifin: start hw on dai probe
netfilter: nf_tables: disallow element removal on anonymous sets
bpf: Avoid deadlock when using queue and stack maps from NMI
selftests/tls: Add {} to avoid static checker warning
selftests: tls: swap the TX and RX sockets in some tests
ASoC: imx-audmix: Fix return error with devm_clk_get()
i40e: Fix for persistent lldp support
i40e: Remove scheduling while atomic possibility
i40e: Fix warning message and call stack during rmmod i40e driver
i40e: Fix VF VLAN offloading when port VLAN is configured
powerpc/perf/hv-24x7: Update domain value check
dccp: fix dccp_v4_err()/dccp_v6_err() again
net: hns3: add 5ms delay before clear firmware reset irq source
net: bridge: use DEV_STATS_INC()
team: fix null-ptr-deref when team device type is changed
net: rds: Fix possible NULL-pointer dereference
gpio: tb10x: Fix an error handling path in tb10x_gpio_probe()
i2c: mux: demux-pinctrl: check the return value of devm_kstrdup()
Input: i8042 - add quirk for TUXEDO Gemini 17 Gen1/Clevo PD70PN
scsi: qla2xxx: Fix update_fcport for current_topology
scsi: qla2xxx: Fix deletion race condition
drm/amd/display: Reinstate LFC optimization
drm/amd/display: Fix LFC multiplier changing erratically
drm/amd/display: prevent potential division by zero errors
ata: libata: disallow dev-initiated LPM transitions to unsupported states
MIPS: Alchemy: only build mmc support helpers if au1xmmc is enabled
clk: tegra: fix error return case for recalc_rate
ARM: dts: ti: omap: motorola-mapphone: Fix abe_clkctrl warning on boot
bus: ti-sysc: Fix SYSC_QUIRK_SWSUP_SIDLE_ACT handling for uart wake-up
xtensa: add default definition for XCHAL_HAVE_DIV32
xtensa: iss/network: make functions static
xtensa: boot: don't add include-dirs
xtensa: boot/lib: fix function prototypes
gpio: pmic-eic-sprd: Add can_sleep flag for PMIC EIC chip
parisc: sba: Fix compile warning wrt list of SBA devices
parisc: iosapic.c: Fix sparse warnings
parisc: drivers: Fix sparse warning
parisc: irq: Make irq_stack_union static to avoid sparse warning
selftests/ftrace: Correctly enable event in instance-event.tc
ring-buffer: Avoid softlockup in ring_buffer_resize()
ata: libata-eh: do not clear ATA_PFLAG_EH_PENDING in ata_eh_reset()
spi: nxp-fspi: reset the FLSHxCR1 registers
bpf: Clarify error expectations from bpf_clone_redirect
powerpc/watchpoints: Annotate atomic context in more places
fbdev/sh7760fb: Depend on FB=y
nvme-pci: do not set the NUMA node of device if it has none
watchdog: iTCO_wdt: No need to stop the timer in probe
watchdog: iTCO_wdt: Set NO_REBOOT if the watchdog is not already running
i40e: improve locking of mac_filter_hash
i40e: always propagate error value in i40e_set_vsi_promisc()
i40e: fix return of uninitialized aq_ret in i40e_set_vsi_promisc
smack: Record transmuting in smk_transmuted
smack: Retrieve transmuting information in smack_inode_getsecurity()
Smack:- Use overlay inode label in smack_inode_copy_up()
serial: 8250_port: Check IRQ data before use
nilfs2: fix potential use after free in nilfs_gccache_submit_read_data()
ALSA: hda: Disable power save for solving pop issue on Lenovo ThinkCentre M70q
ata: libata-scsi: ignore reserved bits for REPORT SUPPORTED OPERATION CODES
i2c: i801: unregister tco_pdev in i801_probe() error path
ring-buffer: Update "shortest_full" in polling
btrfs: properly report 0 avail for very full file systems
net: thunderbolt: Fix TCPv6 GSO checksum calculation
ata: libata-core: Fix ata_port_request_pm() locking
ata: libata-core: Fix port and device removal
ata: libata-core: Do not register PM operations for SAS ports
ata: libata-sata: increase PMP SRST timeout to 10s
fs: binfmt_elf_efpic: fix personality for ELF-FDPIC
rbd: move rbd_dev_refresh() definition
rbd:
[Kernel-packages] [Bug 2040354] Re: Add K24 device tree
** Tags removed: verification-needed-jammy-linux-xilinx-zynqmp ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2040354 Title: Add K24 device tree Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Jammy: Fix Committed Bug description: [ Impact ] * This ports the K24 device trees from the Xilinx 6.1 kernel (xlnx_rebase_v6.1_LTS_2023.1_update) * This will allow the same image.its file and thus flash-kernel package to be used for the K24 development images and the stable release. [ Test Plan ] * The k24 platform does not need to be tested since it is not a certified platform. The normal regression testing on K26 and ZCU platforms is sufficient. [ Where problems could occur ] * A bug in the device tree could cause a build error in the kernel. The device tree is not used by any certified images. [ Other Info ] The change squashes together the following changes from Xilinx xlnx_rebase_v6.1_LTS_2023.1_update branch. Patches that modified device tree other than: arch/arm64/boot/dts/xilinx/zynqmp-sck-kd-g-revA.dts arch/arm64/boot/dts/xilinx/zynqmp-sm-k24-revA.dts arch/arm64/boot/dts/xilinx/zynqmp-smk-k24-revA.dts were modified to remove the other changes. a89bdb9e6f1f arm64: zynqmp: Add/Update/Sync DTs for xilinx platforms f1fe53d988d8 arm64: zynqmp: Update ADI PHY properties for KD240 f660fc7bba89 arm64: zynqmp: Use MIO 77 for ADI PHY reset on KD240 41a6b53e0691 arm64: zynqmp: Fill model name for SOM CCs 958f20d8445e arm64: zynqmp: Fix memory size on k24 c3cc27055c19 arm64: zynqmp: Wire can0 on kd240-revA 9da2d3e73b17 arm64: zynqmp: Configure gem1 rx pins on kd240 board 646a2dfaaaf8 arm64: zynqmp: Cover K24/KD240 revB/1 boards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2040354/+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 2041782] [NEW] spi: spi-cadence-quadspi: Fix ospi resume failures conflicts
Public bug reported: jammy:xilinx-zynqmp is carrying a patch subject "spi: spi-cadence- quadspi: Fix ospi resume failure" from the Xilinx tree , branch xlnx_rebase_v5.15_LTS_2022.1_update . This commit hasn't been upstreamed and completely rewrites the function cqspi_resume(). A change has landed in the v5.15.111 upstream stable release which conflicts with this Xilinx patch in such a way that we don't know how to resolve the conflicts and keep the functionality intact. We have found where Xlinx resolved the merge on the XIlinx 6.1 branch but it doesn't seem correct. In the original commit: (https://github.com/Xilinx/linux- xlnx/commit/6edac18033db445439ca57c23b8cee29a6bbdf0f) in the function cqspi_resume() , the call to cqspi_controller_enable() is removed and ZynqMP specific controls are added. Upstream fixed an issue with suspend-resume (https://github.com/torvalds/linux/commit/2087e85bb66ee3652dafe732bb9b9b896229eafc). The upstream fix replaces the cqspi_controller_enable() with some clock initializations and a call to cqspi_controller_init() which does some register writes before calling cqspi_controller_enable(). Xilinx resolve the conflict by concatenating the two commit's changes to cqspi_resume() (https://github.com/Xilinx/linux-xlnx/blob/xlnx_rebase_v6.1_LTS_2023.1_update/drivers/spi/spi-cadence-quadspi.c#L2271), the end result is that cqspi_resume() consists of ZynqMP specific controls followed by a (nested) call to cqspi_controller_enable(), the exact function call that was removed in XIlinx's original commit. This bug is to track how this merge conflict is resolved. ** Affects: linux-xilinx-zynqmp (Ubuntu) Importance: Undecided Status: New ** Affects: linux-xilinx-zynqmp (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-xilinx-zynqmp (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2041782 Title: spi: spi-cadence-quadspi: Fix ospi resume failures conflicts Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Jammy: New Bug description: jammy:xilinx-zynqmp is carrying a patch subject "spi: spi-cadence- quadspi: Fix ospi resume failure" from the Xilinx tree , branch xlnx_rebase_v5.15_LTS_2022.1_update . This commit hasn't been upstreamed and completely rewrites the function cqspi_resume(). A change has landed in the v5.15.111 upstream stable release which conflicts with this Xilinx patch in such a way that we don't know how to resolve the conflicts and keep the functionality intact. We have found where Xlinx resolved the merge on the XIlinx 6.1 branch but it doesn't seem correct. In the original commit: (https://github.com/Xilinx/linux- xlnx/commit/6edac18033db445439ca57c23b8cee29a6bbdf0f) in the function cqspi_resume() , the call to cqspi_controller_enable() is removed and ZynqMP specific controls are added. Upstream fixed an issue with suspend-resume (https://github.com/torvalds/linux/commit/2087e85bb66ee3652dafe732bb9b9b896229eafc). The upstream fix replaces the cqspi_controller_enable() with some clock initializations and a call to cqspi_controller_init() which does some register writes before calling cqspi_controller_enable(). Xilinx resolve the conflict by concatenating the two commit's changes to cqspi_resume() (https://github.com/Xilinx/linux-xlnx/blob/xlnx_rebase_v6.1_LTS_2023.1_update/drivers/spi/spi-cadence-quadspi.c#L2271), the end result is that cqspi_resume() consists of ZynqMP specific controls followed by a (nested) call to cqspi_controller_enable(), the exact function call that was removed in XIlinx's original commit. This bug is to track how this merge conflict is resolved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2041782/+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 2040354] Re: Add K24 device tree
** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2040354 Title: Add K24 device tree Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Jammy: Fix Committed Bug description: [ Impact ] * This ports the K24 device trees from the Xilinx 6.1 kernel (xlnx_rebase_v6.1_LTS_2023.1_update) * This will allow the same image.its file and thus flash-kernel package to be used for the K24 development images and the stable release. [ Test Plan ] * The k24 platform does not need to be tested since it is not a certified platform. The normal regression testing on K26 and ZCU platforms is sufficient. [ Where problems could occur ] * A bug in the device tree could cause a build error in the kernel. The device tree is not used by any certified images. [ Other Info ] The change squashes together the following changes from Xilinx xlnx_rebase_v6.1_LTS_2023.1_update branch. Patches that modified device tree other than: arch/arm64/boot/dts/xilinx/zynqmp-sck-kd-g-revA.dts arch/arm64/boot/dts/xilinx/zynqmp-sm-k24-revA.dts arch/arm64/boot/dts/xilinx/zynqmp-smk-k24-revA.dts were modified to remove the other changes. a89bdb9e6f1f arm64: zynqmp: Add/Update/Sync DTs for xilinx platforms f1fe53d988d8 arm64: zynqmp: Update ADI PHY properties for KD240 f660fc7bba89 arm64: zynqmp: Use MIO 77 for ADI PHY reset on KD240 41a6b53e0691 arm64: zynqmp: Fill model name for SOM CCs 958f20d8445e arm64: zynqmp: Fix memory size on k24 c3cc27055c19 arm64: zynqmp: Wire can0 on kd240-revA 9da2d3e73b17 arm64: zynqmp: Configure gem1 rx pins on kd240 board 646a2dfaaaf8 arm64: zynqmp: Cover K24/KD240 revB/1 boards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2040354/+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 2040120] Re: Kernel configs deviate from generic kernel
** Changed in: linux-gke (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/2040120 Title: Kernel configs deviate from generic kernel Status in linux-gke package in Ubuntu: Incomplete Status in linux-gke source package in Jammy: Confirmed Bug description: After doing the config to annotation migration it became apparent that during previous cranks generic kernel configs were not correctly updated in the derivative linux-gke kernel. For the time being, the gke annotations file has been updated to match the configs prior to annotation migrations. These configs should be evaluated and updated in linux-gke to match the generic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/2040120/+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 2040354] [NEW] Add K24 device tree
Public bug reported: [ Impact ] * This ports the K24 device trees from the Xilinx 6.1 kernel (xlnx_rebase_v6.1_LTS_2023.1_update) * This will allow the same image.its file and thus flash-kernel package to be used for the K24 development images and the stable release. [ Test Plan ] * The k24 platform does not need to be tested since it is not a certified platform. The normal regression testing on K26 and ZCU platforms is sufficient. [ Where problems could occur ] * A bug in the device tree could cause a build error in the kernel. The device tree is not used by any certified images. [ Other Info ] The change squashes together the following changes from Xilinx xlnx_rebase_v6.1_LTS_2023.1_update branch. Patches that modified device tree other than: arch/arm64/boot/dts/xilinx/zynqmp-sck-kd-g-revA.dts arch/arm64/boot/dts/xilinx/zynqmp-sm-k24-revA.dts arch/arm64/boot/dts/xilinx/zynqmp-smk-k24-revA.dts were modified to remove the other changes. a89bdb9e6f1f arm64: zynqmp: Add/Update/Sync DTs for xilinx platforms f1fe53d988d8 arm64: zynqmp: Update ADI PHY properties for KD240 f660fc7bba89 arm64: zynqmp: Use MIO 77 for ADI PHY reset on KD240 41a6b53e0691 arm64: zynqmp: Fill model name for SOM CCs 958f20d8445e arm64: zynqmp: Fix memory size on k24 c3cc27055c19 arm64: zynqmp: Wire can0 on kd240-revA 9da2d3e73b17 arm64: zynqmp: Configure gem1 rx pins on kd240 board 646a2dfaaaf8 arm64: zynqmp: Cover K24/KD240 revB/1 boards ** Affects: linux-xilinx-zynqmp (Ubuntu) Importance: Undecided Status: New ** Affects: linux-xilinx-zynqmp (Ubuntu Jammy) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => linux-xilinx-zynqmp (Ubuntu) ** Also affects: linux-xilinx-zynqmp (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2040354 Title: Add K24 device tree Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Jammy: New Bug description: [ Impact ] * This ports the K24 device trees from the Xilinx 6.1 kernel (xlnx_rebase_v6.1_LTS_2023.1_update) * This will allow the same image.its file and thus flash-kernel package to be used for the K24 development images and the stable release. [ Test Plan ] * The k24 platform does not need to be tested since it is not a certified platform. The normal regression testing on K26 and ZCU platforms is sufficient. [ Where problems could occur ] * A bug in the device tree could cause a build error in the kernel. The device tree is not used by any certified images. [ Other Info ] The change squashes together the following changes from Xilinx xlnx_rebase_v6.1_LTS_2023.1_update branch. Patches that modified device tree other than: arch/arm64/boot/dts/xilinx/zynqmp-sck-kd-g-revA.dts arch/arm64/boot/dts/xilinx/zynqmp-sm-k24-revA.dts arch/arm64/boot/dts/xilinx/zynqmp-smk-k24-revA.dts were modified to remove the other changes. a89bdb9e6f1f arm64: zynqmp: Add/Update/Sync DTs for xilinx platforms f1fe53d988d8 arm64: zynqmp: Update ADI PHY properties for KD240 f660fc7bba89 arm64: zynqmp: Use MIO 77 for ADI PHY reset on KD240 41a6b53e0691 arm64: zynqmp: Fill model name for SOM CCs 958f20d8445e arm64: zynqmp: Fix memory size on k24 c3cc27055c19 arm64: zynqmp: Wire can0 on kd240-revA 9da2d3e73b17 arm64: zynqmp: Configure gem1 rx pins on kd240 board 646a2dfaaaf8 arm64: zynqmp: Cover K24/KD240 revB/1 boards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2040354/+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 2040120] Re: Kernel configs deviate from generic kernel
** Package changed: linux (Ubuntu) => linux-gke (Ubuntu) ** Also affects: linux-gke (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/2040120 Title: Kernel configs deviate from generic kernel Status in linux-gke package in Ubuntu: Incomplete Status in linux-gke source package in Jammy: New Bug description: After doing the config to annotation migration it became apparent that during previous cranks generic kernel configs were not correctly updated in the derivative linux-gke kernel. For the time being, the gke annotations file has been updated to match the configs prior to annotation migrations. These configs should be evaluated and updated in linux-gke to match the generic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/2040120/+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 2040120] [NEW] Kernel configs deviate from generic kernel
Public bug reported: After doing the config to annotation migration it became apparent that during previous cranks generic kernel configs were not correctly updated in the derivative linux-gke kernel. For the time being, the gke annotations file has been updated to match the configs prior to annotation migrations. These configs should be evaluated and updated in linux-gke to match the generic kernel. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2040120 Title: Kernel configs deviate from generic kernel Status in linux package in Ubuntu: New Bug description: After doing the config to annotation migration it became apparent that during previous cranks generic kernel configs were not correctly updated in the derivative linux-gke kernel. For the time being, the gke annotations file has been updated to match the configs prior to annotation migrations. These configs should be evaluated and updated in linux-gke to match the generic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040120/+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 2021962] Re: F/xilinx and J/xilinx uses different keyword in /proc/device-tree/compatible
The device trees comes directly from the Xilinx kernel (https://github.com/Xilinx/linux-xlnx) . It seems like in the focal kernel the overlay for the KV260 SOM did not set a compatible string so the it fell back to the compatible string defined by the baseboard (zynqmp-smk-k26-revA.dts) . When a device tree for rev B of the board was added the compatible string was added to the rev A device tree as well. The change was added here: https://github.com/Xilinx/linux-xlnx/commit/70604467dc949d3b77eabaa1288365cb25b2ec23#diff-f19b970e083cc67c8063c7698b0bb6554d69d43190d355adc20945526eda5831 I agree with Masahiro that Jammy is correct. Since the device trees are not in the kernel build and are provided by Xilinx I don't think this is something we can backport to Focal. ** Changed in: linux-xilinx-zynqmp (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2021962 Title: F/xilinx and J/xilinx uses different keyword in /proc/device- tree/compatible Status in ubuntu-kernel-tests: New Status in linux-xilinx-zynqmp package in Ubuntu: Won't Fix Bug description: While testing J/xilinx, I noticed that the keyword we use to grep from /proc/device-tree/compatible has to be changed into kv26 instead of k26 that we used for F/xilinx J/xilinx: $ cat /proc/device-tree/compatible xlnx,zynqmp-sk-kv260-rev1xlnx,zynqmp-sk-kv260-revBxlnx,zynqmp-sk-kv260xlnx,zynqmp F/xilinx: $ cat /proc/device-tree/compatible xlnx,zynqmp-smk-k26-rev1xlnx,zynqmp-smk-k26-revBxlnx,zynqmp-smk-k26-revAxlnx,zynqmp-smk-k26xlnx,zynqmp From what I can found on the Internet, KV260 is "a vision application development platform for Kria K26 SOMs (system-on-module)". But it's better to let the kernel maintainer (Portia) to answer that if this difference is expected. Related change for tests: https://code.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests/+merge/443543 --- External link: https://warthogs.atlassian.net/browse/PEL-439 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2021962/+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 1837037] Re: memcg_move_charge_at_immigrate_test from controllers in ubuntu_ltp
Found on linux-xilinx-zynqmp-5.15.0-1020.24/arm64 on zcu106 -- 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/1837037 Title: memcg_move_charge_at_immigrate_test from controllers in ubuntu_ltp Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Won't Fix Bug description: Similar to bug 1837035 This memcg_move_charge_at_immigrate_test test failed on an i386 node "pepe" with Disco kernel. It failed with: memcg_move_charge_at_immigrate_test 5 TINFO: Warming up pid: 2192 memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No such process memcg_move_charge_at_immigrate_test 5 TFAIL: Process 2192 exited with 1 after warm up <<>> tag=memcg_move_charge_at_immigrate stime=1563448078 cmdline="memcg_move_charge_at_immigrate_test.sh" contacts="" analysis=exit <<>> memcg_move_charge_at_immigrate_test 1 TINFO: Starting test 1 /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: echo: I/O error memcg_move_charge_at_immigrate_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_move_charge_at_immigrate_test 1 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_move_charge_at_immigrate_test 1 TINFO: Warming up pid: 2162 memcg_move_charge_at_immigrate_test 1 TINFO: Process is still here after warm up: 2162 memcg_move_charge_at_immigrate_test 1 TPASS: rss is 0 as expected memcg_move_charge_at_immigrate_test 2 TPASS: cache is 0 as expected memcg_move_charge_at_immigrate_test 3 TPASS: rss is 135168 as expected memcg_move_charge_at_immigrate_test 4 TPASS: cache is 0 as expected memcg_move_charge_at_immigrate_test 5 TINFO: Starting test 2 /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: echo: I/O error memcg_move_charge_at_immigrate_test 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_move_charge_at_immigrate_test 5 TINFO: Running memcg_process --mmap-anon --shm --mmap-file -s 135168 memcg_move_charge_at_immigrate_test 5 TINFO: Warming up pid: 2192 memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No such process memcg_move_charge_at_immigrate_test 5 TFAIL: Process 2192 exited with 1 after warm up memcg_move_charge_at_immigrate_test 6 TINFO: Starting test 3 /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: echo: I/O error memcg_move_charge_at_immigrate_test 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_move_charge_at_immigrate_test 6 TINFO: Running memcg_process --mmap-anon --shm --mmap-file -s 135168 memcg_move_charge_at_immigrate_test 6 TINFO: Warming up pid: 2207 memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No such process memcg_move_charge_at_immigrate_test 6 TFAIL: Process 2207 exited with 1 after warm up memcg_move_charge_at_immigrate_test 7 TINFO: Starting test 4 /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: echo: I/O error memcg_move_charge_at_immigrate_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_move_charge_at_immigrate_test 7 TINFO: Running memcg_process --mmap-anon --shm -s 135168 memcg_move_charge_at_immigrate_test 7 TINFO: Warming up pid: memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No such process memcg_move_charge_at_immigrate_test 7 TFAIL: Process exited with 1 after warm up <<>> initiation_status="ok" duration=4 termination_type=exited termination_id=1 corefile=no cutime=9 cstime=2 <<>> Steps to run this test: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "memcg_move_charge_at_immigrate memcg_move_charge_at_immigrate_test.sh" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: User Name 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 18 10:01 seq crw-rw 1 root audio 116, 33 Jul 18 10:01 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27.1 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jul 18 11:16:36 2019 IwConfig: Error: [Errno 2] No such file or directory:
[Kernel-packages] [Bug 1837035] Re: memcg_stat_rss from controllers in ubuntu_ltp failed
Found on linux-xilinx-zynqmp-5.15.0-1020.24/arm64 on zcu106 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1837035 Title: memcg_stat_rss from controllers in ubuntu_ltp failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: Confirmed Bug description: This issue was spotted on an i386 node "pepe" with Disco kernel, it failed with: memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process memcg_stat_rss 4 TFAIL: Process 1845 exited with 1 after warm up <<>> tag=memcg_stat_rss stime=1563448062 cmdline="memcg_stat_rss.sh" contacts="" analysis=exit <<>> memcg_stat_rss 1 TINFO: Starting test 1 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 1 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_stat_rss 1 TINFO: Warming up pid: 1784 memcg_stat_rss 1 TINFO: Process is still here after warm up: 1784 memcg_stat_rss 1 TPASS: rss is 135168 as expected memcg_stat_rss 2 TINFO: Starting test 2 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 2 TINFO: Running memcg_process --mmap-file -s 4096 memcg_stat_rss 2 TINFO: Warming up pid: 1804 memcg_stat_rss 2 TINFO: Process is still here after warm up: 1804 memcg_stat_rss 2 TPASS: rss is 0 as expected memcg_stat_rss 3 TINFO: Starting test 3 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 3 TINFO: Running memcg_process --shm -k 3 -s 4096 memcg_stat_rss 3 TINFO: Warming up pid: 1825 memcg_stat_rss 3 TINFO: Process is still here after warm up: 1825 memcg_stat_rss 3 TPASS: rss is 0 as expected memcg_stat_rss 4 TINFO: Starting test 4 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 4 TINFO: Running memcg_process --mmap-anon --mmap-file --shm -s 135168 memcg_stat_rss 4 TINFO: Warming up pid: 1845 memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process memcg_stat_rss 4 TFAIL: Process 1845 exited with 1 after warm up memcg_stat_rss 5 TINFO: Starting test 5 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 5 TINFO: Running memcg_process --mmap-lock1 -s 135168 memcg_stat_rss 5 TINFO: Warming up pid: 1858 memcg_stat_rss 5 TINFO: Process is still here after warm up: 1858 memcg_stat_rss 5 TPASS: rss is 135168 as expected memcg_stat_rss 6 TINFO: Starting test 6 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 6 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_stat_rss 6 TINFO: Warming up pid: 1878 memcg_stat_rss 6 TINFO: Process is still here after warm up: 1878 memcg_stat_rss 6 TPASS: rss is 135168 as expected memcg_stat_rss 7 TPASS: rss is 0 as expected memcg_stat_rss 8 TINFO: Starting test 7 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 8 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 8 TINFO: Running memcg_process --mmap-file -s 4096 memcg_stat_rss 8 TINFO: Warming up pid: 1901 memcg_stat_rss 8 TINFO: Process is still here after warm up: 1901 memcg_stat_rss 8 TPASS: rss is 0 as expected memcg_stat_rss 9 TPASS: rss is 0 as expected memcg_stat_rss 10 TINFO: Starting test 8 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 10 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 10 TINFO: Running memcg_process --shm -k 8 -s 4096 memcg_stat_rss 10 TINFO: Warming up pid: 1925 memcg_stat_rss 10 TINFO: Process is still here after warm up: 1925 memcg_stat_rss 10 TPASS: rss is 0 as expected memcg_stat_rss 11 TPASS: rss is 0 as expected memcg_stat_rss 12 TINFO: Starting test 9 /opt/ltp/testcases/bin/memcg_stat_rss.sh: 522: echo: echo: I/O error memcg_stat_rss 12 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_rss 12 TINFO: Running memcg_process --mmap-anon --mmap-file --shm -s 135168 memcg_stat_rss 12 TINFO: Warming up pid: 1948 memcg_process: shmget() failed: Invalid argument /opt/ltp/testcases/bin/memcg_stat_rss.sh: 168: kill: No such process memcg_stat_rss 12 TFAIL: Process 1948 exited with 1 after warm up memcg_stat_rss 13 TINFO: Starting test
[Kernel-packages] [Bug 1992912] Re: linux-xilinx-zynqmp/focal: main(): sched_setscheduler(): Operation not permitted
** Changed in: linux-xilinx-zynqmp (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/1992912 Title: linux-xilinx-zynqmp/focal: main(): sched_setscheduler(): Operation not permitted Status in ubuntu-kernel-tests: New Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Focal: Fix Committed Bug description: [SRU Justification] [Impact] The focal kernel is failing the ubuntu_ltp:sched:time-schedule01, ubuntu_ltp:sched:trace_sched01 and ubuntu_ltp:irq:irqbalance0 regression test due to sched_setscheduler being unable to a task class to SCHED_FIFO. This is due to have having CONFIG_RT_GROUP_SCHED enabled. Once RT_GROUP_SCHED is enabled it is impossible to schedule realtime tasks for non-root users until you allocate realtime bandwidth for them. There are multiple known issues with CONFIG_RT_GROUP_SCHED that are reported in the debian.master/config/annotations file: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284731 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873315 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665 [Fix] CONFIG_RT_GROUP_SCHED should be disabled. The config was enabled when we copied the Xilinx default config settings and there is not a justification for this exact config. There may even be a negative impact, from the kernel.org documentation: “The default values for sched_rt_period_us (100 or 1s) and sched_rt_runtime_us (95 or 0.95s). This gives 0.05s to be used by SCHED_OTHER (non-RT tasks).” This suggests this option will benefit RT systems, but be detrimental to non-RT systems, [Testcase] The annotations file will enforce that CONFIG_RT_GROUP_SCHED is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1992912/+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 1992912] Re: linux-xilinx-zynqmp/focal: main(): sched_setscheduler(): Operation not permitted
** Also affects: linux-xilinx-zynqmp (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/1992912 Title: linux-xilinx-zynqmp/focal: main(): sched_setscheduler(): Operation not permitted Status in ubuntu-kernel-tests: New Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Focal: New Bug description: [SRU Justification] [Impact] The focal kernel is failing the ubuntu_ltp:sched:time-schedule01, ubuntu_ltp:sched:trace_sched01 and ubuntu_ltp:irq:irqbalance0 regression test due to sched_setscheduler being unable to a task class to SCHED_FIFO. This is due to have having CONFIG_RT_GROUP_SCHED enabled. Once RT_GROUP_SCHED is enabled it is impossible to schedule realtime tasks for non-root users until you allocate realtime bandwidth for them. There are multiple known issues with CONFIG_RT_GROUP_SCHED that are reported in the debian.master/config/annotations file: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284731 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873315 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665 [Fix] CONFIG_RT_GROUP_SCHED should be disabled. The config was enabled when we copied the Xilinx default config settings and there is not a justification for this exact config. There may even be a negative impact, from the kernel.org documentation: “The default values for sched_rt_period_us (100 or 1s) and sched_rt_runtime_us (95 or 0.95s). This gives 0.05s to be used by SCHED_OTHER (non-RT tasks).” This suggests this option will benefit RT systems, but be detrimental to non-RT systems, [Testcase] The annotations file will enforce that CONFIG_RT_GROUP_SCHED is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1992912/+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 1995465] Re: linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security.
** Also affects: linux-xilinx-zynqmp (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-xilinx-zynqmp (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/1995465 Title: linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security. Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Focal: Fix Committed Bug description: [SRU Justification] [Impact] The linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security regression test due to kernel config options. The kernel configs were changed to match the Xilinx provided kernel configs which resulted in these configs being disabled. [Fix] Enable all configs checked in ubuntu_qrt_kernel_security. [Testcase] ubuntu_qrt_kernel caught this isuse and will continue to test whether these configs are enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/1995465/+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 1995465] Re: linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security.
Enable the following configs: PAGE_POISONING_ZERO PAGE_POISONING_NO_SANITY PAGE_POISONING SECURITY_LOCKDOWN_LSM SCHED_STACK_END_CHECK SECURITY_YAMA DEBUG_WX CONFIG_SECURITY_PERF_EVENTS_RESTRICT CONFIG_SECURITY_PERF_EVENTS_RESTRICT FORTIFY_SOURCE HARDENED_USERCOPY SLAB_FREELIST_RANDOM IP_ADVANCED_ROUTER SECURITY_TOMOYO ** Description changed: [SRU Justification] [Impact] - The linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security regression test due to kernel config options. The kernel configs were changed to + The linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security regression test due to kernel config options. The kernel configs were changed to match the Xilinx provided kernel configs which resulted in these configs being disabled. [Fix] - Enable the following configs: - PAGE_POISONING_ZERO - PAGE_POISONING_NO_SANITY - PAGE_POISONING - SECURITY_LOCKDOWN_LSM - SCHED_STACK_END_CHECK - SECURITY_YAMA - DEBUG_WX - CONFIG_SECURITY_PERF_EVENTS_RESTRICT - CONFIG_SECURITY_PERF_EVENTS_RESTRICT - FORTIFY_SOURCE - HARDENED_USERCOPY - SLAB_FREELIST_RANDOM - IP_ADVANCED_ROUTER - SECURITY_TOMOYO - RANDOMIZE_BASE + Enable all configs checked in ubuntu_qrt_kernel_security. + [Testcase] ubuntu_qrt_kernel caught this isuse and will continue to test whether these configs are enabled. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/1995465 Title: linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security. Status in linux-xilinx-zynqmp package in Ubuntu: New Bug description: [SRU Justification] [Impact] The linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security regression test due to kernel config options. The kernel configs were changed to match the Xilinx provided kernel configs which resulted in these configs being disabled. [Fix] Enable all configs checked in ubuntu_qrt_kernel_security. [Testcase] ubuntu_qrt_kernel caught this isuse and will continue to test whether these configs are enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/1995465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1992912] Re: linux-xilinx-zynqmp/focal: main(): sched_setscheduler(): Operation not permitted
** Description changed: [SRU Justification] [Impact] The focal kernel is failing the ubuntu_ltp:sched:time-schedule01 and ubuntu_ltp:sched:trace_sched01 regression test due to sched_setscheduler being unable to a task class to SCHED_FIFO. This is due to have having CONFIG_RT_GROUP_SCHED enabled. There are multiple known issues with CONFIG_RT_GROUP_SCHED that are reported in the debian.master/config/annotations file: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284731 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873315 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665 [Fix] CONFIG_RT_GROUP_SCHED should be disabled. The config was enabled when we copied the Xilinx default config settings and there is not a - justification for this exact config. + justification for this exact config. There may even be a negative + impact, from the kernel.org documentation: + + “The default values for sched_rt_period_us (100 or 1s) and + sched_rt_runtime_us (95 or 0.95s). This gives 0.05s to be used by + SCHED_OTHER (non-RT tasks).” + + This suggests this option will benefit RT systems, but be detrimental to + non-RT systems, [Testcase] + + The annotations file will enforce that CONFIG_RT_GROUP_SCHED is + disabled. ** Description changed: [SRU Justification] [Impact] - The focal kernel is failing the ubuntu_ltp:sched:time-schedule01 and ubuntu_ltp:sched:trace_sched01 regression test due to sched_setscheduler being unable to a task class to SCHED_FIFO. This is due to have having CONFIG_RT_GROUP_SCHED enabled. + The focal kernel is failing the ubuntu_ltp:sched:time-schedule01, ubuntu_ltp:sched:trace_sched01 and ubuntu_ltp:irq:irqbalance0 regression test due to sched_setscheduler being unable to a task class to SCHED_FIFO. This is due to have having CONFIG_RT_GROUP_SCHED enabled. Once RT_GROUP_SCHED is enabled it is impossible to schedule realtime tasks for non-root users until you allocate realtime bandwidth for them. There are multiple known issues with CONFIG_RT_GROUP_SCHED that are reported in the debian.master/config/annotations file: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284731 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873315 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665 [Fix] CONFIG_RT_GROUP_SCHED should be disabled. The config was enabled when we copied the Xilinx default config settings and there is not a justification for this exact config. There may even be a negative impact, from the kernel.org documentation: “The default values for sched_rt_period_us (100 or 1s) and sched_rt_runtime_us (95 or 0.95s). This gives 0.05s to be used by SCHED_OTHER (non-RT tasks).” This suggests this option will benefit RT systems, but be detrimental to non-RT systems, [Testcase] The annotations file will enforce that CONFIG_RT_GROUP_SCHED is disabled. ** Changed in: linux-xilinx-zynqmp (Ubuntu) Assignee: (unassigned) => Portia Stephens (portias) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/1992912 Title: linux-xilinx-zynqmp/focal: main(): sched_setscheduler(): Operation not permitted Status in ubuntu-kernel-tests: New Status in linux-xilinx-zynqmp package in Ubuntu: New Bug description: [SRU Justification] [Impact] The focal kernel is failing the ubuntu_ltp:sched:time-schedule01, ubuntu_ltp:sched:trace_sched01 and ubuntu_ltp:irq:irqbalance0 regression test due to sched_setscheduler being unable to a task class to SCHED_FIFO. This is due to have having CONFIG_RT_GROUP_SCHED enabled. Once RT_GROUP_SCHED is enabled it is impossible to schedule realtime tasks for non-root users until you allocate realtime bandwidth for them. There are multiple known issues with CONFIG_RT_GROUP_SCHED that are reported in the debian.master/config/annotations file: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284731 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873315 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665 [Fix] CONFIG_RT_GROUP_SCHED should be disabled. The config was enabled when we copied the Xilinx default config settings and there is not a justification for this exact config. There may even be a negative impact, from the kernel.org documentation: “The default values for sched_rt_period_us (100 or 1s) and sched_rt_runtime_us (95 or 0.95s). This gives 0.05s to be used by SCHED_OTHER (non-RT tasks).” This suggests this option will benefit RT systems, but be detrimental to non-RT systems, [Testcase] The annotations file will enforce that CONFIG_RT_GROUP_SCHED is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1992912/+subscriptions -- Mailing list: ht
[Kernel-packages] [Bug 1992912] Re: linux-xilinx-zynqmp/focal: main(): sched_setscheduler(): Operation not permitted
** Description changed: - The focal kernel is failing the ubuntu_ltp:sched:time-schedule01 and - ubuntu_ltp:sched:trace_sched01 regression test due to sched_setscheduler - being unable to a task class to SCHED_FIFO. + [SRU Justification] + + [Impact] + The focal kernel is failing the ubuntu_ltp:sched:time-schedule01 and ubuntu_ltp:sched:trace_sched01 regression test due to sched_setscheduler being unable to a task class to SCHED_FIFO. This is due to have having CONFIG_RT_GROUP_SCHED enabled. There are multiple known issues with CONFIG_RT_GROUP_SCHED that are reported in the debian.master/config/annotations file: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284731 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873315 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665 - We do not have a good reason to enable this , I see no processes using realtime scheduling. We should disable this setting to match the upstream Ubuntu focal arm64 kernel. The following tests are failing with this error: - * ubuntu_ltp:sched:time-schedule01 - * ubuntu_ltp:sched:trace_sched01 - * ubuntu_qrt_apparmor:test-apparmor + [Fix] + + CONFIG_RT_GROUP_SCHED should be disabled. The config was enabled when we + copied the Xilinx default config settings and there is not a + justification for this exact config. + + [Testcase] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/1992912 Title: linux-xilinx-zynqmp/focal: main(): sched_setscheduler(): Operation not permitted Status in ubuntu-kernel-tests: New Status in linux-xilinx-zynqmp package in Ubuntu: New Bug description: [SRU Justification] [Impact] The focal kernel is failing the ubuntu_ltp:sched:time-schedule01 and ubuntu_ltp:sched:trace_sched01 regression test due to sched_setscheduler being unable to a task class to SCHED_FIFO. This is due to have having CONFIG_RT_GROUP_SCHED enabled. There are multiple known issues with CONFIG_RT_GROUP_SCHED that are reported in the debian.master/config/annotations file: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284731 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873315 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665 [Fix] CONFIG_RT_GROUP_SCHED should be disabled. The config was enabled when we copied the Xilinx default config settings and there is not a justification for this exact config. There may even be a negative impact, from the kernel.org documentation: “The default values for sched_rt_period_us (100 or 1s) and sched_rt_runtime_us (95 or 0.95s). This gives 0.05s to be used by SCHED_OTHER (non-RT tasks).” This suggests this option will benefit RT systems, but be detrimental to non-RT systems, [Testcase] The annotations file will enforce that CONFIG_RT_GROUP_SCHED is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1992912/+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 1992912] Re: linux-xilinx-zynqmp/focal: main(): sched_setscheduler(): Operation not permitted
** Summary changed: - linux-xilinx-zynqmp: main(): sched_setscheduler(): Operation not permitted + linux-xilinx-zynqmp/focal: main(): sched_setscheduler(): Operation not permitted -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/1992912 Title: linux-xilinx-zynqmp/focal: main(): sched_setscheduler(): Operation not permitted Status in ubuntu-kernel-tests: New Status in linux-xilinx-zynqmp package in Ubuntu: New Bug description: The focal kernel is failing the ubuntu_ltp:sched:time-schedule01 and ubuntu_ltp:sched:trace_sched01 regression test due to sched_setscheduler being unable to a task class to SCHED_FIFO. There are multiple known issues with CONFIG_RT_GROUP_SCHED that are reported in the debian.master/config/annotations file: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284731 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873315 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665 We do not have a good reason to enable this , I see no processes using realtime scheduling. We should disable this setting to match the upstream Ubuntu focal arm64 kernel. The following tests are failing with this error: * ubuntu_ltp:sched:time-schedule01 * ubuntu_ltp:sched:trace_sched01 * ubuntu_qrt_apparmor:test-apparmor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1992912/+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 1995465] Re: linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security.
** Description changed: - The linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security - regression test due to kernel config options. The following tests are - failing: + [SRU Justification] - KernelSecurityConfigTest.test_010_kaslr_config - KernelSecurityConfigTest.test_100_config_security_tomoyo - KernelSecurityConfigTest.test_230_config_security_ipsec - KernelSecurityConfigTest.test_240_SLAB_freelist_randomization - KernelSecurityConfigTest.test_290_config_hardened_usercopy - KernelSecurityConfigTest.test_300_config_kernel_fortify - KernelSecurityConfigTest.test_310_config_security_perf_events_restrict - KernelSecurityConfigTest.test_320_config_arm_pan - KernelSecurityConfigTest.test_330_config_debug_wx - KernelSecurityConfigTest.test_360_config_security_yama - KernelSecurityConfigTest.test_380_config_sched_stack_end_check - KernelSecurityConfigTest.test_410_config_lock_down_kernel - KernelSecurityConfigTest.test_420_config_page_poisoning - KernelSecurityConfigTest.test_421_config_page_poisoning_no_sanity - KernelSecurityConfigTest.test_421_config_page_poisoning_zero - KernelSecurityConfigTest.test_430_config_module_sign - KernelSecurityConfigTest.test_440_config_module_sign_all + [Impact] + + The linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security regression test due to kernel config options. The kernel configs were changed to + match the Xilinx provided kernel configs which resulted in these configs being disabled. + + [Fix] + + Enable the following configs: + PAGE_POISONING_ZERO + PAGE_POISONING_NO_SANITY + PAGE_POISONING + SECURITY_LOCKDOWN_LSM + SCHED_STACK_END_CHECK + SECURITY_YAMA
[Kernel-packages] [Bug 1995465] [NEW] linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security.
Public bug reported: The linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security regression test due to kernel config options. The following tests are failing: KernelSecurityConfigTest.test_010_kaslr_config KernelSecurityConfigTest.test_100_config_security_tomoyo KernelSecurityConfigTest.test_230_config_security_ipsec KernelSecurityConfigTest.test_240_SLAB_freelist_randomization KernelSecurityConfigTest.test_290_config_hardened_usercopy KernelSecurityConfigTest.test_300_config_kernel_fortify KernelSecurityConfigTest.test_310_config_security_perf_events_restrict KernelSecurityConfigTest.test_320_config_arm_pan KernelSecurityConfigTest.test_330_config_debug_wx KernelSecurityConfigTest.test_360_config_security_yama KernelSecurityConfigTest.test_380_config_sched_stack_end_check KernelSecurityConfigTest.test_410_config_lock_down_kernel KernelSecurityConfigTest.test_420_config_page_poisoning KernelSecurityConfigTest.test_421_config_page_poisoning_no_sanity KernelSecurityConfigTest.test_421_config_page_poisoning_zero KernelSecurityConfigTest.test_430_config_module_sign KernelSecurityConfigTest.test_440_config_module_sign_all ** Affects: linux-xilinx-zynqmp (Ubuntu) Importance: Undecided Assignee: Portia Stephens (portias) Status: New ** Package changed: linux (Ubuntu) => linux-xilinx-zynqmp (Ubuntu) ** Changed in: linux-xilinx-zynqmp (Ubuntu) Assignee: (unassigned) => Portia Stephens (portias) -- 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/1995465 Title: linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security. Status in linux-xilinx-zynqmp package in Ubuntu: New Bug description: The linux-xilinx-zynqmp/focal fails ubuntu_qrt_kernel_security regression test due to kernel config options. The following tests are failing: KernelSecurityConfigTest.test_010_kaslr_config KernelSecurityConfigTest.test_100_config_security_tomoyo KernelSecurityConfigTest.test_230_config_security_ipsec KernelSecurityConfigTest.test_240_SLAB_freelist_randomi
[Kernel-packages] [Bug 1992912] Re: linux-xilinx-zynqmp: main(): sched_setscheduler(): Operation not permitted
** Description changed: - Multiple regression tests are failing on the linux-xilinx-zynqmp/focal kernel when calling sched_setscheduler() or with related operations. This is probably caused by enabling CONFIG_RT_GROUP_SCHED since similiar issues have been seen when enabling this config on other kernels. The following tests are failing with this error: + The focal kernel is failing the ubuntu_ltp:sched:time-schedule01 and + ubuntu_ltp:sched:trace_sched01 regression test due to sched_setscheduler + being unable to a task class to SCHED_FIFO. + + There are multiple known issues with CONFIG_RT_GROUP_SCHED that are reported in the debian.master/config/annotations file: + https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284731 + https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873315 + https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665 + + We do not have a good reason to enable this , I see no processes using realtime scheduling. We should disable this setting to match the upstream Ubuntu focal arm64 kernel. The following tests are failing with this error: * ubuntu_ltp:sched:time-schedule01 * ubuntu_ltp:sched:trace_sched01 * ubuntu_qrt_apparmor:test-apparmor -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/1992912 Title: linux-xilinx-zynqmp: main(): sched_setscheduler(): Operation not permitted Status in ubuntu-kernel-tests: New Status in linux-xilinx-zynqmp package in Ubuntu: New Bug description: The focal kernel is failing the ubuntu_ltp:sched:time-schedule01 and ubuntu_ltp:sched:trace_sched01 regression test due to sched_setscheduler being unable to a task class to SCHED_FIFO. There are multiple known issues with CONFIG_RT_GROUP_SCHED that are reported in the debian.master/config/annotations file: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284731 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873315 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665 We do not have a good reason to enable this , I see no processes using realtime scheduling. We should disable this setting to match the upstream Ubuntu focal arm64 kernel. The following tests are failing with this error: * ubuntu_ltp:sched:time-schedule01 * ubuntu_ltp:sched:trace_sched01 * ubuntu_qrt_apparmor:test-apparmor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1992912/+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
