From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>,
[email protected], Jann Horn <[email protected]>
Cc: [email protected], [email protected]
Subject: Re: [PATCH] io_uring/rsrc: require cloned buffers to share accounting contexts
Date: Tue, 14 Jan 2025 11:10:04 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Tue, 14 Jan 2025 18:49:00 +0100, Jann Horn wrote:
> When IORING_REGISTER_CLONE_BUFFERS is used to clone buffers from uring
> instance A to uring instance B, where A and B use different MMs for
> accounting, the accounting can go wrong:
> If uring instance A is closed before uring instance B, the pinned memory
> counters for uring instance B will be decremented, even though the pinned
> memory was originally accounted through uring instance A; so the MM of
> uring instance B can end up with negative locked memory.
>
> [...]
Applied, thanks!
[1/1] io_uring/rsrc: require cloned buffers to share accounting contexts
commit: 19d340a2988d4f3e673cded9dde405d727d7e248
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-01-14 18:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 17:49 [PATCH] io_uring/rsrc: require cloned buffers to share accounting contexts Jann Horn
2025-01-14 17:57 ` Jens Axboe
2025-01-14 18:10 ` 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=173687820427.1326090.9681462149230294879.b4-ty@kernel.dk \
[email protected] \
[email protected] \
[email protected] \
[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