io_uring regression - lost write request

Bug #1952222 reported by Stefan Metzmacher
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned
Focal
Undecided
Unassigned
Impish
Undecided
Unassigned
linux-hwe-5.13 (Ubuntu)
Undecided
Unassigned
Focal
Undecided
Unassigned
Impish
Undecided
Unassigned
linux-oem-5.13 (Ubuntu)
Undecided
Unassigned
Focal
Undecided
Unassigned
Impish
Undecided
Unassigned
linux-oem-5.14 (Ubuntu)
Undecided
Unassigned
Focal
Undecided
Timo Aaltonen
Impish
Undecided
Unassigned

Bug Description

There's a regression with io_uring reported against 5.11-5.14 kernels, see:

https://lore.kernel.<email address hidden>/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.

affects: samba (Ubuntu) → linux-hwe-5.13 (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1952222

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Stefan Metzmacher (metze) wrote :

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
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

the fix is in 5.15-rc1 and up, jammy has 5.15.x

Changed in linux (Ubuntu):
status: Confirmed → Fix Released
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
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

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):
assignee: nobody → Timo Aaltonen (tjaalton)
status: New → Confirmed
Revision history for this message
Stefan Metzmacher (metze) wrote :

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
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers