From: Jens Axboe <[email protected]>
To: [email protected], Pavel Begunkov <[email protected]>
Subject: Re: [PATCH 1/1] io_uring: prevent opcode speculation
Date: Sat, 15 Feb 2025 08:15:44 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <7eddbf31c8ca0a3947f8ed98271acc2b4349c016.1739568408.git.asml.silence@gmail.com>
On Fri, 14 Feb 2025 22:48:15 +0000, Pavel Begunkov wrote:
> sqe->opcode is used for different tables, make sure we santitise it
> against speculations.
>
>
Applied, thanks!
[1/1] io_uring: prevent opcode speculation
commit: 1e988c3fe1264708f4f92109203ac5b1d65de50b
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-02-15 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 22:48 [PATCH 1/1] io_uring: prevent opcode speculation Pavel Begunkov
2025-02-15 4:39 ` lizetao
2025-02-15 15:15 ` Jens Axboe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=173963254457.12458.1902250086361474768.b4-ty@kernel.dk \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox