Re: [PATCH 5.10] io_uring: prevent opcode speculation

Alexey Panov <[email protected]>
Newsgroups org.kernel.vger.io-uring,org.kernel.vger.linux-kernel,org.kernel.vger.stable
Message-ID <[email protected]>
On Thu, Jun 11, 2026 at 11:26:24AM -0400, Sasha Levin wrote:
> The 5.10 backport itself looks fine, but I can't take it on its own:
> 1e988c3fe126 is still missing from 6.6.y and 6.12.y (it's present in
> 7.0, 6.18, 6.1 and 5.15), and we don't add a fix to an older tree while
> a newer one is missing it. Once 6.6.y and 6.12.y carry it, I'll queue
> the 5.10 backport.

Hi Sasha,

Unless I am missing something, the fix is already present in both trees:

  6.6.y:  b9826e3b26ec ("io_uring: prevent opcode speculation"),
          included since v6.6.80
  6.12.y: 506b9b5e8c2d ("io_uring: prevent opcode speculation"),
          included since v6.12.17

Both commits explicitly reference upstream commit 1e988c3fe126 and were
committed on February 27, 2025.

Could you please re-check and queue the 5.10 backport?
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.