From: Jens Axboe <axboe@kernel.dk>
To: Joanne Koong <joannelkoong@gmail.com>
Cc: csander@purestorage.com, io-uring@vger.kernel.org
Subject: Re: [PATCH v1] io_uring/kbuf: use WRITE_ONCE() for userspace-shared buffer ring fields
Date: Fri, 05 Dec 2025 09:52:51 -0700 [thread overview]
Message-ID: <176495357153.1162213.11911701547224537851.b4-ty@kernel.dk> (raw)
In-Reply-To: <20251204235450.1219662-1-joannelkoong@gmail.com>
On Thu, 04 Dec 2025 15:54:50 -0800, Joanne Koong wrote:
> buf->addr and buf->len reside in memory shared with userspace. They
> should be written with WRITE_ONCE() to guarantee atomic stores and
> prevent tearing or other unsafe compiler optimizations.
>
>
Applied, thanks!
[1/1] io_uring/kbuf: use WRITE_ONCE() for userspace-shared buffer ring fields
commit: a4c694bfc2455e82b7caf6045ca893d123e0ed11
Best regards,
--
Jens Axboe
next prev parent reply other threads:[~2025-12-05 16:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 23:54 [PATCH v1] io_uring/kbuf: use WRITE_ONCE() for userspace-shared buffer ring fields Joanne Koong
2025-12-05 16:51 ` Jens Axboe
2025-12-05 16:52 ` Jens Axboe [this message]
2025-12-05 16:55 ` Caleb Sander Mateos
2025-12-05 16:56 ` Jens Axboe
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=176495357153.1162213.11911701547224537851.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=csander@purestorage.com \
--cc=io-uring@vger.kernel.org \
--cc=joannelkoong@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