aboutsummaryrefslogtreecommitdiff
path: root/drivers/fpga/fpga-bridge.c
diff options
context:
space:
mode:
authorJens Axboe <[email protected]>2024-11-29 07:20:28 -0700
committerJens Axboe <[email protected]>2024-11-29 07:20:28 -0700
commit7eb75ce7527129d7f1fee6951566af409a37a1c4 (patch)
tree91a2fd805f90410062190d2a6d12cbaca1cf37ce /drivers/fpga/fpga-bridge.c
parent43eef70e7e2ac74e7767731dd806720c7fb5e010 (diff)
io_uring/tctx: work around xa_store() allocation error issue
syzbot triggered the following WARN_ON: WARNING: CPU: 0 PID: 16 at io_uring/tctx.c:51 __io_uring_free+0xfa/0x140 io_uring/tctx.c:51 which is the WARN_ON_ONCE(!xa_empty(&tctx->xa)); sanity check in __io_uring_free() when a io_uring_task is going through its final put. The syzbot test case includes injecting memory allocation failures, and it very much looks like xa_store() can fail one of its memory allocations and end up with ->head being non-NULL even though no entries exist in the xarray. Until this issue gets sorted out, work around it by attempting to iterate entries in our xarray, and WARN_ON_ONCE() if one is found. Reported-by: [email protected] Link: https://lore.kernel.org/io-uring/[email protected]/ Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'drivers/fpga/fpga-bridge.c')
0 files changed, 0 insertions, 0 deletions