diff options
author | Jens Axboe <axboe@kernel.dk> | 2025-09-18 22:59:15 +0300 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2025-09-18 22:59:15 +0300 |
commit | df8922afc37aa2111ca79a216653a629146763ad (patch) | |
tree | c75fa1b2325c54e460cea5d7732c3dfe659fd190 /drivers/gpu/drm/amd/amdgpu/amdgpu_encoders.c | |
parent | 3539b1467e94336d5854ebf976d9627bfb65d6c3 (diff) | |
download | linux-df8922afc37aa2111ca79a216653a629146763ad.tar.xz |
io_uring/msg_ring: kill alloc_cache for io_kiocb allocations
A recent commit:
fc582cd26e88 ("io_uring/msg_ring: ensure io_kiocb freeing is deferred for RCU")
fixed an issue with not deferring freeing of io_kiocb structs that
msg_ring allocates to after the current RCU grace period. But this only
covers requests that don't end up in the allocation cache. If a request
goes into the alloc cache, it can get reused before it is sane to do so.
A recent syzbot report would seem to indicate that there's something
there, however it may very well just be because of the KASAN poisoning
that the alloc_cache handles manually.
Rather than attempt to make the alloc_cache sane for that use case, just
drop the usage of the alloc_cache for msg_ring request payload data.
Fixes: 50cf5f3842af ("io_uring/msg_ring: add an alloc cache for io_kiocb entries")
Link: https://lore.kernel.org/io-uring/68cc2687.050a0220.139b6.0005.GAE@google.com/
Reported-by: syzbot+baa2e0f4e02df602583e@syzkaller.appspotmail.com
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_encoders.c')
0 files changed, 0 insertions, 0 deletions