APPLIED: [SRU][N:linux-gke/N:linux-gkeop][PATCH 0/1] io_uring: always lock __io_cqring_overflow_flush

[Ian Whitfield]

On Thu, Feb 20, 2025 at 07:30:03PM -0800, Ian Whitfield wrote:
> BugLink: https://bugs.launchpad.net/bugs/2099347
> 
> [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 the generic 6.8 kernel, 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.
> 
> Pavel Begunkov (1):
>   io_uring: always lock __io_cqring_overflow_flush
> 
>  io_uring/io_uring.c | 13 ++++++++-----
>  1 file changed, 8 insertions(+), 5 deletions(-)
> 
> -- 
> 2.43.0
> 

Applied to noble:linux-gke master-next and gkeop-next branches.