From: Leon Romanovsky <leon@kernel.org>
To: Zhu Yanjun <zyjzyj2000@gmail.com>, Jason Gunthorpe <jgg@ziepe.ca>,
Tristan Madani <tristmd@gmail.com>
Cc: linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org,
Tristan Madani <tristan@talencesecurity.com>
Subject: Re: [PATCH v10 0/2] RDMA/rxe: copy send WQE to kernel buffer (TOCTOU hardening)
Date: Tue, 03 Nov 2026 08:52:02 -0500 [thread overview]
Message-ID: <179371392293.1727833.9297401437119983949.b4-ty@kernel.org> (raw)
In-Reply-To: <20261030193235.3470653-1-tristan@talencesecurity.com>
On Fri, 30 Oct 2026 19:32:33 +0000, Tristan Madani wrote:
> The SoftRoCE (rxe) send queue is mmap-ed into userspace, allowing
> the requester and completer to process work queue entries (WQEs)
> whose fields can change between kernel reads.
>
> This series copies each WQE to a kernel-private buffer before
> processing: patch 1 for the requester, patch 2 for the completer.
> Both paths validate opcode bounds and SGE indices after copying,
> preserve DMA progress across multi-packet operations, and write
> back updated fields to the shared queue via WRITE_ONCE / smp_store_release.
>
> [...]
Applied, thanks!
[1/2] RDMA/rxe: copy send WQE to kernel buffer before processing
https://git.kernel.org/rdma/rdma/c/a668a8564748d5
[2/2] RDMA/rxe: copy send WQE to kernel buffer in completer path
https://git.kernel.org/rdma/rdma/c/195c20429f13fd
Best regards,
--
Leon Romanovsky <leon@kernel.org>
prev parent reply other threads:[~2026-11-03 13:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 19:32 Tristan Madani
2026-10-30 19:32 ` [PATCH v10 1/2] RDMA/rxe: copy send WQE to kernel buffer before processing Tristan Madani
2026-10-30 22:20 ` Zhu Yanjun
2026-10-30 19:32 ` [PATCH v10 2/2] RDMA/rxe: copy send WQE to kernel buffer in completer path Tristan Madani
2026-10-30 22:22 ` Zhu Yanjun
2026-11-03 13:52 ` Leon Romanovsky [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=179371392293.1727833.9297401437119983949.b4-ty@kernel.org \
--to=leon@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tristan@talencesecurity.com \
--cc=tristmd@gmail.com \
--cc=zyjzyj2000@gmail.com \
/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
all inboxes | Powered by JetHome®