diff options
author | Nadav Amit <namit@vmware.com> | 2021-08-07 17:13:42 -0700 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2021-08-08 21:21:11 -0600 |
commit | 20c0b380f971e7d48f5d978bc27d827f7eabb21a (patch) | |
tree | 502ab1f31055a72f8c56dc43190978fcb1d7915b /net/bluetooth/amp.c | |
parent | ef98eb0409c31c39ab55ff46b2721c3b4f84c122 (diff) |
io_uring: Use WRITE_ONCE() when writing to sq_flags
The compiler should be forbidden from any strange optimization for async
writes to user visible data-structures. Without proper protection, the
compiler can cause write-tearing or invent writes that would confuse the
userspace.
However, there are writes to sq_flags which are not protected by
WRITE_ONCE(). Use WRITE_ONCE() for these writes.
This is purely a theoretical issue. Presumably, any compiler is very
unlikely to do such optimizations.
Fixes: 75b28affdd6a ("io_uring: allocate the two rings together")
Cc: Jens Axboe <axboe@kernel.dk>
Cc: Pavel Begunkov <asml.silence@gmail.com>
Signed-off-by: Nadav Amit <namit@vmware.com>
Link: https://lore.kernel.org/r/20210808001342.964634-3-namit@vmware.com
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'net/bluetooth/amp.c')
0 files changed, 0 insertions, 0 deletions