public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: io-uring@vger.kernel.org
Cc: David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH v1 0/3] io_uring mm related abuses
Date: Tue, 24 Jun 2025 11:38:27 +0100	[thread overview]
Message-ID: <a6be01c8-5e36-447d-acd1-3491bb50faaa@gmail.com> (raw)
In-Reply-To: <cover.1750760501.git.asml.silence@gmail.com>

On 6/24/25 11:35, Pavel Begunkov wrote:
> Patch 1 uses unpin_user_folio instead of the page variant.
> Patches 2-3 make sure io_uring doesn't make any assumptions
> about user pointer alignments.

I didn't reproduce the alignment issue, sth wrong with my
KASAN'ed machine, need to fix that, and it did't trigger
without it.

> 
> Pavel Begunkov (3):
>    io_uring/rsrc: fix folio unpinning
>    io_uring/rsrc: don't rely on user vaddr alignment
>    io_uring: don't assume uaddr alignment in io_vec_fill_bvec
> 
>   io_uring/rsrc.c | 28 +++++++++++++++++++++-------
>   io_uring/rsrc.h |  1 +
>   2 files changed, 22 insertions(+), 7 deletions(-)
> 

-- 
Pavel Begunkov


      parent reply	other threads:[~2025-06-24 10:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-24 10:35 [PATCH v1 0/3] io_uring mm related abuses Pavel Begunkov
2025-06-24 10:35 ` [PATCH v1 1/3] io_uring/rsrc: fix folio unpinning Pavel Begunkov
2025-06-24 11:57   ` David Hildenbrand
2025-06-24 12:08     ` Pavel Begunkov
2025-06-24 10:35 ` [PATCH v1 2/3] io_uring/rsrc: don't rely on user vaddr alignment Pavel Begunkov
2025-06-24 11:53   ` David Hildenbrand
2025-06-24 12:20     ` Pavel Begunkov
2025-06-24 12:26       ` David Hildenbrand
2025-06-24 12:37         ` Pavel Begunkov
2025-06-24 12:30       ` Pavel Begunkov
2025-06-24 12:42   ` David Hildenbrand
2025-06-24 12:54     ` Pavel Begunkov
2025-06-24 10:35 ` [PATCH v1 3/3] io_uring: don't assume uaddr alignment in io_vec_fill_bvec Pavel Begunkov
2025-06-24 10:38 ` Pavel Begunkov [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=a6be01c8-5e36-447d-acd1-3491bb50faaa@gmail.com \
    --to=asml.silence@gmail.com \
    --cc=david@redhat.com \
    --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