]> www.infradead.org Git - users/dwmw2/linux.git/commit
io_uring/register: use atomic_read/write for sq_flags migration
authorJens Axboe <axboe@kernel.dk>
Fri, 24 Jan 2025 21:32:25 +0000 (14:32 -0700)
committerJens Axboe <axboe@kernel.dk>
Fri, 24 Jan 2025 21:36:43 +0000 (14:36 -0700)
commita23ad06bfee5e51cd9e51aebf11401e7b4b5d00a
tree03dac5af79ac67ab965e9374bf79bc1e6e27f983
parentff74954e4e9374f24b95dd46ef0bb1b5fa0a46f2
io_uring/register: use atomic_read/write for sq_flags migration

A previous commit changed all of the migration from the old to the new
ring for resizing to use READ/WRITE_ONCE. However, ->sq_flags is an
atomic_t, and while most archs won't complain on this, some will indeed
flag this:

io_uring/register.c:554:9: sparse: sparse: cast to non-scalar
io_uring/register.c:554:9: sparse: sparse: cast from non-scalar

Just use atomic_set/atomic_read for handling this case.

Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202501242000.A2sKqaCL-lkp@intel.com/
Fixes: 2c5aae129f42 ("io_uring/register: document io_register_resize_rings() shared mem usage")
Signed-off-by: Jens Axboe <axboe@kernel.dk>
io_uring/register.c