** Summary changed:
- Early cherry-pick to resolve io_uring hang in 2025.02.10 cycle
+ io_uring hang in 2025.02.10 cycle causing processes to be stuck in D state
** Description changed:
SRU Justification
[Impact]
GKE requested an early cherry-pick of 8d09a88ef9d3 ("io_uring: always lock
__io_cqring_overflow_flush")
due to an issue created by commit eac2ca2d682f ("io_uring: check if we need
to reschedule during overflow flush") which is planned to be included in the
6.8 kernel updates for the 2025.02.10 cycle.
The following cycle (2025.03.17) is already planned to include the fix
commit in all 6.8 kernels, but GKE would like the fix to be picked early
to be included in their kernels for 2025.02.10 cycle updates.
+
+ This cherry-pick will be dropped from the kernels after it is received
+ via the parent generic kernel.
[Fix]
Cherry-pick 8d09a88ef9d3 ("io_uring: always lock
__io_cqring_overflow_flush") to noble:gke and noble:gkeop, which are the
only GKE kernels planned to receive the break commit via stable updates.
[Test Plan]
Compile and boot test.
[Regression potential]
Because this commit is already expected to arrive next cycle and is
cleanly applied, there is very very low chance of regression.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2099347
Title:
io_uring hang in 2025.02.10 cycle causing processes to be stuck in D
state
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/2099347/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
