From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org, Pavel Begunkov <asml.silence@gmail.com>
Cc: dw@davidwei.uk
Subject: Re: [PATCH 1/1] io_uring/zcrx: disallow user selected dmabuf offset and size
Date: Mon, 14 Jul 2025 08:57:27 -0600 [thread overview]
Message-ID: <175250504719.127578.17592684126023227858.b4-ty@kernel.dk> (raw)
In-Reply-To: <be899f1afed32053eb2e2079d0da241514674aca.1752443579.git.asml.silence@gmail.com>
On Mon, 14 Jul 2025 11:57:23 +0100, Pavel Begunkov wrote:
> zcrx shouldn't be so frivolous about cutting a dmabuf sgtable and taking
> a subrange into it, the dmabuf layer might be not expecting that. It
> shouldn't be a problem for now, but since the zcrx dmabuf support is new
> and there shouldn't be any real users, let's play safe and reject user
> provided ranges into dmabufs. Also, it shouldn't be needed as userspace
> should size them appropriately.
>
> [...]
Applied, thanks!
[1/1] io_uring/zcrx: disallow user selected dmabuf offset and size
commit: 08ca1409c4fa37ec93de08b9963390ed68a5ae8c
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-07-14 14:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 10:57 [PATCH 1/1] io_uring/zcrx: disallow user selected dmabuf offset and size Pavel Begunkov
2025-07-14 14:57 ` 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=175250504719.127578.17592684126023227858.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=dw@davidwei.uk \
--cc=io-uring@vger.kernel.org \
/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