From: Jens Axboe <axboe@kernel.dk>
To: io-uring <io-uring@vger.kernel.org>
Cc: Pavel Begunkov <asml.silence@gmail.com>
Subject: Re: [PATCH] io_uring/kbuf: ensure ring ctx is held locked over io_put_kbuf()
Date: Wed, 20 Aug 2025 18:31:28 -0600 [thread overview]
Message-ID: <b7d3cc3d-36af-4ba0-bdfe-e38f8188dd15@kernel.dk> (raw)
In-Reply-To: <e2f14b20-2ad4-4e59-9966-26dd6aa70f31@kernel.dk>
On 8/20/25 5:16 PM, Jens Axboe wrote:
> The issue_flags will tell us if this is needed or not, however a
> previous commit was a bit too eager with the cleanups and removed the
> required locking in case IO_URING_F_UNLOCKED is set in the issue_flags.
Actually, disregard that one - on closer inspection, it doesn't matter
anymore. On the legacy side, it's just being freed. For ring buffers,
they would already have been committed.
--
Jens Axboe
next prev parent reply other threads:[~2025-08-21 0:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 23:16 [PATCH] io_uring/kbuf: ensure ring ctx is held locked over io_put_kbuf() Jens Axboe
2025-08-21 0:31 ` Jens Axboe [this message]
2025-08-21 6:54 ` [syzbot ci] " syzbot ci
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=b7d3cc3d-36af-4ba0-bdfe-e38f8188dd15@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.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