diff options
| author | Jens Axboe <axboe@kernel.dk> | 2025-01-25 00:32:25 +0300 |
|---|---|---|
| committer | Jens Axboe <axboe@kernel.dk> | 2025-01-25 00:36:43 +0300 |
| commit | a23ad06bfee5e51cd9e51aebf11401e7b4b5d00a (patch) | |
| tree | 03dac5af79ac67ab965e9374bf79bc1e6e27f983 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | ff74954e4e9374f24b95dd46ef0bb1b5fa0a46f2 (diff) | |
| download | linux-a23ad06bfee5e51cd9e51aebf11401e7b4b5d00a.tar.xz | |
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>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions