[Kernel-packages] [Bug 1952222] Re: io_uring regression - lost write request
This bug was fixed in the package linux-hwe-5.13 - 5.13.0-41.46~20.04.1
---
linux-hwe-5.13 (5.13.0-41.46~20.04.1) focal; urgency=medium
* focal/linux-hwe-5.13: 5.13.0-41.46~20.04.1 -proposed tracker (LP:
#1969013)
[ Ubuntu: 5.13.0-41.46 ]
* impish/linux: 5.13.0-41.46 -proposed tracker (LP: #1969014)
* NVMe devices fail to probe due to ACPI power state change (LP: #1942624)
- ACPI: power: Rework turning off unused power resources
- ACPI: PM: Do not turn off power resources in unknown state
* Recent 5.13 kernel has broken KVM support (LP: #1966499)
- KVM: Add infrastructure and macro to mark VM as bugged
- KVM: x86: Use KVM_BUG/KVM_BUG_ON to handle bugs that are fatal to the VM
- KVM: VMX: prepare sync_pir_to_irr for running with APICv disabled
* LRMv6: add multi-architecture support (LP: #1968774)
- [Packaging] resync dkms-build{,--nvidia-N}
* io_uring regression - lost write request (LP: #195)
- io-wq: split bounded and unbounded work into separate lists
* xfrm interface cannot be changed anymore (LP: #1968591)
- xfrm: fix the if_id check in changelink
* Use kernel-testing repo from launchpad for ADT tests (LP: #1968016)
- [Debian] Use kernel-testing repo from launchpad
* vmx_ldtr_test in ubuntu_kvm_unit_tests failed (FAIL: Expected 0 for L1 LDTR
selector (got 50)) (LP: #1956315)
- KVM: nVMX: Set LDTR to its architecturally defined value on nested VM-Exit
* audio from external sound card is distorted (LP: #1966066)
- ALSA: usb-audio: Fix packet size calculation regression
* Impish update: upstream stable patchset 2022-04-12 (LP: #1968771)
- cgroup/cpuset: Fix a race between cpuset_attach() and cpu hotplug
- btrfs: tree-checker: check item_size for inode_item
- btrfs: tree-checker: check item_size for dev_item
- clk: jz4725b: fix mmc0 clock gating
- vhost/vsock: don't check owner in vhost_vsock_stop() while releasing
- parisc/unaligned: Fix fldd and fstd unaligned handlers on 32-bit kernel
- parisc/unaligned: Fix ldw() and stw() unalignment handlers
- KVM: x86/mmu: make apf token non-zero to fix bug
- drm/amdgpu: disable MMHUB PG for Picasso
- drm/i915: Correctly populate use_sagv_wm for all pipes
- sr9700: sanity check for packet length
- USB: zaurus: support another broken Zaurus
- CDC-NCM: avoid overflow in sanity checking
- x86/fpu: Correct pkru/xstate inconsistency
- tee: export teedev_open() and teedev_close_context()
- optee: use driver internal tee_context for some rpc
- ping: remove pr_err from ping_lookup
- perf data: Fix double free in perf_session__delete()
- bnx2x: fix driver load from initrd
- bnxt_en: Fix active FEC reporting to ethtool
- hwmon: Handle failure to register sensor with thermal zone correctly
- bpf: Do not try bpf_msg_push_data with len 0
- selftests: bpf: Check bpf_msg_push_data return value
- bpf: Add schedule points in batch ops
- io_uring: add a schedule point in io_add_buffers()
- net: __pskb_pull_tail() & pskb_carve_frag_list() drop_monitor friends
- tipc: Fix end of loop tests for list_for_each_entry()
- gso: do not skip outer ip header in case of ipip and net_failover
- openvswitch: Fix setting ipv6 fields causing hw csum failure
- drm/edid: Always set RGB444
- net/mlx5e: Fix wrong return value on ioctl EEPROM query failure
- net/sched: act_ct: Fix flow table lookup after ct clear or switching zones
- net: ll_temac: check the return value of devm_kmalloc()
- net: Force inlining of checksum functions in net/checksum.h
- nfp: flower: Fix a potential leak in nfp_tunnel_add_shared_mac()
- netfilter: nf_tables: fix memory leak during stateful obj update
- net/smc: Use a mutex for locking "struct smc_pnettable"
- surface: surface3_power: Fix battery readings on batteries without a
serial
number
- udp_tunnel: Fix end of loop test in udp_tunnel_nic_unregister()
- net/mlx5: Fix possible deadlock on rule deletion
- net/mlx5: Fix wrong limitation of metadata match on ecpf
- net/mlx5e: kTLS, Use CHECKSUM_UNNECESSARY for device-offloaded packets
- spi: spi-zynq-qspi: Fix a NULL pointer dereference in
zynq_qspi_exec_mem_op()
- regmap-irq: Update interrupt clear register for proper reset
- RDMA/rtrs-clt: Fix possible double free in error case
- RDMA/rtrs-clt: Move free_permit from free_clt to rtrs_clt_close
- configfs: fix a race in configfs_{,un}register_subsystem()
- RDMA/ib_srp: Fix a deadlock
- tracing: Have traceon and traceoff trigger honor the instance
- iio: adc: men_z188_adc: Fix a resource leak in an error handling path
- iio: adc: ad7124: fix mask used for setting AIN_BUFP & AIN_BUFM bits
- iio: imu: st_lsm6dsx: wait for settling time in st_lsm6dsx_read_oneshot
- iio: Fix error handling for PM
- sc16is7xx: Fix for incorrect data being transmitted
- ata:
[Kernel-packages] [Bug 1952222] Re: io_uring regression - lost write request
This bug was fixed in the package linux - 5.13.0-41.46
---
linux (5.13.0-41.46) impish; urgency=medium
* impish/linux: 5.13.0-41.46 -proposed tracker (LP: #1969014)
* NVMe devices fail to probe due to ACPI power state change (LP: #1942624)
- ACPI: power: Rework turning off unused power resources
- ACPI: PM: Do not turn off power resources in unknown state
* Recent 5.13 kernel has broken KVM support (LP: #1966499)
- KVM: Add infrastructure and macro to mark VM as bugged
- KVM: x86: Use KVM_BUG/KVM_BUG_ON to handle bugs that are fatal to the VM
- KVM: VMX: prepare sync_pir_to_irr for running with APICv disabled
* LRMv6: add multi-architecture support (LP: #1968774)
- [Packaging] resync dkms-build{,--nvidia-N}
* io_uring regression - lost write request (LP: #195)
- io-wq: split bounded and unbounded work into separate lists
* xfrm interface cannot be changed anymore (LP: #1968591)
- xfrm: fix the if_id check in changelink
* Use kernel-testing repo from launchpad for ADT tests (LP: #1968016)
- [Debian] Use kernel-testing repo from launchpad
* vmx_ldtr_test in ubuntu_kvm_unit_tests failed (FAIL: Expected 0 for L1 LDTR
selector (got 50)) (LP: #1956315)
- KVM: nVMX: Set LDTR to its architecturally defined value on nested VM-Exit
* audio from external sound card is distorted (LP: #1966066)
- ALSA: usb-audio: Fix packet size calculation regression
* Impish update: upstream stable patchset 2022-04-12 (LP: #1968771)
- cgroup/cpuset: Fix a race between cpuset_attach() and cpu hotplug
- btrfs: tree-checker: check item_size for inode_item
- btrfs: tree-checker: check item_size for dev_item
- clk: jz4725b: fix mmc0 clock gating
- vhost/vsock: don't check owner in vhost_vsock_stop() while releasing
- parisc/unaligned: Fix fldd and fstd unaligned handlers on 32-bit kernel
- parisc/unaligned: Fix ldw() and stw() unalignment handlers
- KVM: x86/mmu: make apf token non-zero to fix bug
- drm/amdgpu: disable MMHUB PG for Picasso
- drm/i915: Correctly populate use_sagv_wm for all pipes
- sr9700: sanity check for packet length
- USB: zaurus: support another broken Zaurus
- CDC-NCM: avoid overflow in sanity checking
- x86/fpu: Correct pkru/xstate inconsistency
- tee: export teedev_open() and teedev_close_context()
- optee: use driver internal tee_context for some rpc
- ping: remove pr_err from ping_lookup
- perf data: Fix double free in perf_session__delete()
- bnx2x: fix driver load from initrd
- bnxt_en: Fix active FEC reporting to ethtool
- hwmon: Handle failure to register sensor with thermal zone correctly
- bpf: Do not try bpf_msg_push_data with len 0
- selftests: bpf: Check bpf_msg_push_data return value
- bpf: Add schedule points in batch ops
- io_uring: add a schedule point in io_add_buffers()
- net: __pskb_pull_tail() & pskb_carve_frag_list() drop_monitor friends
- tipc: Fix end of loop tests for list_for_each_entry()
- gso: do not skip outer ip header in case of ipip and net_failover
- openvswitch: Fix setting ipv6 fields causing hw csum failure
- drm/edid: Always set RGB444
- net/mlx5e: Fix wrong return value on ioctl EEPROM query failure
- net/sched: act_ct: Fix flow table lookup after ct clear or switching zones
- net: ll_temac: check the return value of devm_kmalloc()
- net: Force inlining of checksum functions in net/checksum.h
- nfp: flower: Fix a potential leak in nfp_tunnel_add_shared_mac()
- netfilter: nf_tables: fix memory leak during stateful obj update
- net/smc: Use a mutex for locking "struct smc_pnettable"
- surface: surface3_power: Fix battery readings on batteries without a
serial
number
- udp_tunnel: Fix end of loop test in udp_tunnel_nic_unregister()
- net/mlx5: Fix possible deadlock on rule deletion
- net/mlx5: Fix wrong limitation of metadata match on ecpf
- net/mlx5e: kTLS, Use CHECKSUM_UNNECESSARY for device-offloaded packets
- spi: spi-zynq-qspi: Fix a NULL pointer dereference in
zynq_qspi_exec_mem_op()
- regmap-irq: Update interrupt clear register for proper reset
- RDMA/rtrs-clt: Fix possible double free in error case
- RDMA/rtrs-clt: Move free_permit from free_clt to rtrs_clt_close
- configfs: fix a race in configfs_{,un}register_subsystem()
- RDMA/ib_srp: Fix a deadlock
- tracing: Have traceon and traceoff trigger honor the instance
- iio: adc: men_z188_adc: Fix a resource leak in an error handling path
- iio: adc: ad7124: fix mask used for setting AIN_BUFP & AIN_BUFM bits
- iio: imu: st_lsm6dsx: wait for settling time in st_lsm6dsx_read_oneshot
- iio: Fix error handling for PM
- sc16is7xx: Fix for incorrect data being transmitted
- ata: pata_hpt37x: disable primary channel on HPT371
- Revert "USB: serial: ch341: add new Product ID for CH341A"
- usb: gadget:
[Kernel-packages] [Bug 1952222] Re: io_uring regression - lost write request
Hello @metze, The Impish kernel with the patches for this issue is currently in -proposed. Could you please test this kernel to check whether it's fixed? Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/195 Title: io_uring regression - lost write request Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.13 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: Confirmed Status in linux-oem-5.13 source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Fix Committed Status in linux-hwe-5.13 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: There's a regression with io_uring reported against 5.11-5.14 kernels, see: https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_- ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b From reading the thread and looking at the history in linux-stable/linux-5.15.y, I assume that Linux 5.15.3 is the first fully fixed version. And 5.10 was not affected. Sadly all other versions are EOL for kernel.org. But ubuntu provides 5.11, 5.13 and 5.14 based kernels, which most likely have the bug. I'm reporting it against linux-hwe-5.13 as that's what I test on most systems, but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952222] Re: io_uring regression - lost write request
This bug is awaiting verification that the linux/5.13.0-41.46 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/195 Title: io_uring regression - lost write request Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.13 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: Confirmed Status in linux-oem-5.13 source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Fix Committed Status in linux-hwe-5.13 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: There's a regression with io_uring reported against 5.11-5.14 kernels, see: https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_- ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b From reading the thread and looking at the history in linux-stable/linux-5.15.y, I assume that Linux 5.15.3 is the first fully fixed version. And 5.10 was not affected. Sadly all other versions are EOL for kernel.org. But ubuntu provides 5.11, 5.13 and 5.14 based kernels, which most likely have the bug. I'm reporting it against linux-hwe-5.13 as that's what I test on most systems, but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952222] Re: io_uring regression - lost write request
** Changed in: linux (Ubuntu Impish) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/195 Title: io_uring regression - lost write request Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.13 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: Confirmed Status in linux-oem-5.13 source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Fix Committed Status in linux-hwe-5.13 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: There's a regression with io_uring reported against 5.11-5.14 kernels, see: https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_- ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b From reading the thread and looking at the history in linux-stable/linux-5.15.y, I assume that Linux 5.15.3 is the first fully fixed version. And 5.10 was not affected. Sadly all other versions are EOL for kernel.org. But ubuntu provides 5.11, 5.13 and 5.14 based kernels, which most likely have the bug. I'm reporting it against linux-hwe-5.13 as that's what I test on most systems, but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952222] Re: io_uring regression - lost write request
** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/195 Title: io_uring regression - lost write request Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.13 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: Confirmed Status in linux-oem-5.13 source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Confirmed Status in linux-hwe-5.13 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: There's a regression with io_uring reported against 5.11-5.14 kernels, see: https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_- ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b From reading the thread and looking at the history in linux-stable/linux-5.15.y, I assume that Linux 5.15.3 is the first fully fixed version. And 5.10 was not affected. Sadly all other versions are EOL for kernel.org. But ubuntu provides 5.11, 5.13 and 5.14 based kernels, which most likely have the bug. I'm reporting it against linux-hwe-5.13 as that's what I test on most systems, but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952222] Re: io_uring regression - lost write request
sent the patch to the list for impish, and hwe-5.13 will get it from there -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/195 Title: io_uring regression - lost write request Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.13 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: Confirmed Status in linux-oem-5.13 source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Confirmed Status in linux-hwe-5.13 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: There's a regression with io_uring reported against 5.11-5.14 kernels, see: https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_- ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b From reading the thread and looking at the history in linux-stable/linux-5.15.y, I assume that Linux 5.15.3 is the first fully fixed version. And 5.10 was not affected. Sadly all other versions are EOL for kernel.org. But ubuntu provides 5.11, 5.13 and 5.14 based kernels, which most likely have the bug. I'm reporting it against linux-hwe-5.13 as that's what I test on most systems, but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952222] Re: io_uring regression - lost write request
@tjaalton what will happen to impish 5.13 and focal hwe-5.13? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/195 Title: io_uring regression - lost write request Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.13 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: Confirmed Status in linux-oem-5.13 source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Confirmed Status in linux-hwe-5.13 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: There's a regression with io_uring reported against 5.11-5.14 kernels, see: https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_- ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b From reading the thread and looking at the history in linux-stable/linux-5.15.y, I assume that Linux 5.15.3 is the first fully fixed version. And 5.10 was not affected. Sadly all other versions are EOL for kernel.org. But ubuntu provides 5.11, 5.13 and 5.14 based kernels, which most likely have the bug. I'm reporting it against linux-hwe-5.13 as that's what I test on most systems, but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952222] Re: io_uring regression - lost write request
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1024.26 --- linux-oem-5.14 (5.14.0-1024.26) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1024.26 -proposed tracker (LP: #1961191) * Packaging resync (LP: #1786013) - [Config] Update config to match upstream stable release - [Packaging] update variants * CVE-2022-0435 - tipc: improve size validations for received domain records * CVE-2022-0492 - cgroup-v1: Require capabilities to set release_agent * Use EC GPE for s2idle wakeup on AMD platforms (LP: #1960771) - ACPI: PM: Revert "Only mark EC GPE for wakeup on Intel systems" * USB port lost function after unplugging usb drive (LP: #1958850) - block: add disk sequence number - mm: hide laptop_mode_wb_timer entirely behind the BDI API - block: pass a gendisk to blk_queue_update_readahead - block: add a queue_has_disk helper - block: move the bdi from the request_queue to the gendisk - block: remove the bd_bdi in struct block_device - nvme: use blk_mq_alloc_disk - st: do not allocate a gendisk - sg: do not allocate a gendisk - block: cleanup the lockdep handling in *alloc_disk - block: remove alloc_disk and alloc_disk_node - block: remove the minors argument to __alloc_disk_node - block: pass a request_queue to __blk_alloc_disk - block: hold a request_queue reference for the lifetime of struct gendisk - block: add an explicit ->disk backpointer to the request_queue - writeback: make the laptop_mode prototypes available unconditionally - sg: pass the device name to blk_trace_setup - block: factor out a blk_try_enter_queue helper - block: drain file system I/O on del_gendisk - block: keep q_usage_counter in atomic mode after del_gendisk - block: drain queue after disk is removed from sysfs - nvdimm/pmem: stop using q_usage_count as external pgmap refcount - nvdimm/pmem: cleanup the disk if pmem_release_disk() is yet assigned * Focal update: upstream stable patchset 2022-01-31 (LP: #1959569) - iommu/amd: Restore GA log/tail pointer on host resume -- Timo Aaltonen Thu, 17 Feb 2022 13:23:43 +0200 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Confirmed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0435 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0492 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/195 Title: io_uring regression - lost write request Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.13 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: Confirmed Status in linux-oem-5.13 source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Confirmed Status in linux-hwe-5.13 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: There's a regression with io_uring reported against 5.11-5.14 kernels, see: https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_- ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b From reading the thread and looking at the history in linux-stable/linux-5.15.y, I assume that Linux 5.15.3 is the first fully fixed version. And 5.10 was not affected. Sadly all other versions are EOL for kernel.org. But ubuntu provides 5.11, 5.13 and 5.14 based kernels, which most likely have the bug. I'm reporting it against linux-hwe-5.13 as that's what I test on most systems, but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952222] Re: io_uring regression - lost write request
thanks for testing! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/195 Title: io_uring regression - lost write request Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.13 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: Confirmed Status in linux-oem-5.13 source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Impish: Confirmed Status in linux-hwe-5.13 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: There's a regression with io_uring reported against 5.11-5.14 kernels, see: https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_- ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b From reading the thread and looking at the history in linux-stable/linux-5.15.y, I assume that Linux 5.15.3 is the first fully fixed version. And 5.10 was not affected. Sadly all other versions are EOL for kernel.org. But ubuntu provides 5.11, 5.13 and 5.14 based kernels, which most likely have the bug. I'm reporting it against linux-hwe-5.13 as that's what I test on most systems, but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952222] Re: io_uring regression - lost write request
5.14.0-1023.25 seems to work fine.
I used the steps similar to
https://lore.kernel.org/io-uring/CABVffEM79CZ+4SW0+yP0+NioMX=shhoobcefbhqs6g6hex2...@mail.gmail.com/
cmake -DPLUGIN_{MROONGA,ROCKSDB,CONNECT,SPIDER,SPHINX,S3,COLUMNSTORE}=NO
-DWITH_URING=ON ../mariadb-server
make -j8
mysql-test/mtr --mysqld=--innodb_use_native_aio=1 --nowarnings --parallel=4
--force encryption.innochecksum{,} --mysqld=--innodb_io_capacity=5
--mysqld=--innodb_io_capacity_max=9
And it failed twice with 5.14.0-1022.24, while it finished twice on
5.14.0-1023.25
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/195
Title:
io_uring regression - lost write request
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-5.13 package in Ubuntu:
Invalid
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-hwe-5.13 source package in Focal:
Confirmed
Status in linux-oem-5.13 source package in Focal:
Won't Fix
Status in linux-oem-5.14 source package in Focal:
Confirmed
Status in linux source package in Impish:
Confirmed
Status in linux-hwe-5.13 source package in Impish:
Invalid
Status in linux-oem-5.13 source package in Impish:
Invalid
Status in linux-oem-5.14 source package in Impish:
Invalid
Bug description:
There's a regression with io_uring reported against 5.11-5.14 kernels,
see:
https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_-
ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b
From reading the thread and looking at the history in
linux-stable/linux-5.15.y,
I assume that Linux 5.15.3 is the first fully fixed version.
And 5.10 was not affected.
Sadly all other versions are EOL for kernel.org.
But ubuntu provides 5.11, 5.13 and 5.14 based kernels,
which most likely have the bug.
I'm reporting it against linux-hwe-5.13 as that's what I test on most systems,
but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952222] Re: io_uring regression - lost write request
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1023.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/195 Title: io_uring regression - lost write request Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.13 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: Confirmed Status in linux-oem-5.13 source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Impish: Confirmed Status in linux-hwe-5.13 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: There's a regression with io_uring reported against 5.11-5.14 kernels, see: https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_- ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b From reading the thread and looking at the history in linux-stable/linux-5.15.y, I assume that Linux 5.15.3 is the first fully fixed version. And 5.10 was not affected. Sadly all other versions are EOL for kernel.org. But ubuntu provides 5.11, 5.13 and 5.14 based kernels, which most likely have the bug. I'm reporting it against linux-hwe-5.13 as that's what I test on most systems, but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952222] Re: io_uring regression - lost write request
Thanks Timo for taking a look! ** Changed in: linux-hwe-5.13 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu Impish) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/195 Title: io_uring regression - lost write request Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.13 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: Confirmed Status in linux-oem-5.13 source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Impish: Confirmed Status in linux-hwe-5.13 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: There's a regression with io_uring reported against 5.11-5.14 kernels, see: https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_- ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b From reading the thread and looking at the history in linux-stable/linux-5.15.y, I assume that Linux 5.15.3 is the first fully fixed version. And 5.10 was not affected. Sadly all other versions are EOL for kernel.org. But ubuntu provides 5.11, 5.13 and 5.14 based kernels, which most likely have the bug. I'm reporting it against linux-hwe-5.13 as that's what I test on most systems, but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952222] Re: io_uring regression - lost write request
oem-5.13 will migrate to oem-5.14 next cycle ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux-hwe-5.13 (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- 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/195 Title: io_uring regression - lost write request Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.13 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: New Status in linux-oem-5.13 source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Impish: New Status in linux-hwe-5.13 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: There's a regression with io_uring reported against 5.11-5.14 kernels, see: https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_- ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b From reading the thread and looking at the history in linux-stable/linux-5.15.y, I assume that Linux 5.15.3 is the first fully fixed version. And 5.10 was not affected. Sadly all other versions are EOL for kernel.org. But ubuntu provides 5.11, 5.13 and 5.14 based kernels, which most likely have the bug. I'm reporting it against linux-hwe-5.13 as that's what I test on most systems, but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952222] Re: io_uring regression - lost write request
the fix is in 5.15-rc1 and up, jammy has 5.15.x ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-hwe-5.13 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-hwe-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.13 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-oem-5.14 (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-hwe-5.13 (Ubuntu Impish) 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/195 Title: io_uring regression - lost write request Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.13 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: New Status in linux-oem-5.13 source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Impish: New Status in linux-hwe-5.13 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: There's a regression with io_uring reported against 5.11-5.14 kernels, see: https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_- ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b From reading the thread and looking at the history in linux-stable/linux-5.15.y, I assume that Linux 5.15.3 is the first fully fixed version. And 5.10 was not affected. Sadly all other versions are EOL for kernel.org. But ubuntu provides 5.11, 5.13 and 5.14 based kernels, which most likely have the bug. I'm reporting it against linux-hwe-5.13 as that's what I test on most systems, but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952222] Re: io_uring regression - lost write request
apport-collect is not useful, someone needs to read the initial comment and backport the existing fixes from 5.15.y ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux-hwe-5.13 (Ubuntu) Status: New => Confirmed ** Changed in: linux-oem-5.13 (Ubuntu) Status: New => Confirmed ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/195 Title: io_uring regression - lost write request Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.13 package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Confirmed Bug description: There's a regression with io_uring reported against 5.11-5.14 kernels, see: https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_- ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b From reading the thread and looking at the history in linux-stable/linux-5.15.y, I assume that Linux 5.15.3 is the first fully fixed version. And 5.10 was not affected. Sadly all other versions are EOL for kernel.org. But ubuntu provides 5.11, 5.13 and 5.14 based kernels, which most likely have the bug. I'm reporting it against linux-hwe-5.13 as that's what I test on most systems, but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952222] Re: io_uring regression - lost write request
** Also 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/195 Title: io_uring regression - lost write request Status in linux package in Ubuntu: New Status in linux-hwe-5.13 package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Bug description: There's a regression with io_uring reported against 5.11-5.14 kernels, see: https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_- ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b From reading the thread and looking at the history in linux-stable/linux-5.15.y, I assume that Linux 5.15.3 is the first fully fixed version. And 5.10 was not affected. Sadly all other versions are EOL for kernel.org. But ubuntu provides 5.11, 5.13 and 5.14 based kernels, which most likely have the bug. I'm reporting it against linux-hwe-5.13 as that's what I test on most systems, but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
