summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/libxed.py
diff options
context:
space:
mode:
authorJoanne Koong <joannelkoong@gmail.com>2025-03-18 03:30:28 +0300
committerMiklos Szeredi <mszeredi@redhat.com>2025-03-31 15:59:27 +0300
commit1dfe2a220e9cd85861a853b00d8620222b960c1f (patch)
treef9bb92e91d7710034478dcbd33affb2f2588b4db /tools/perf/scripts/python/libxed.py
parent27992ef80770d61a57f6c3a551735b08cefdffa3 (diff)
downloadlinux-1dfe2a220e9cd85861a853b00d8620222b960c1f.tar.xz
fuse: fix uring race condition for null dereference of fc
There is a race condition leading to a kernel crash from a null dereference when attemping to access fc->lock in fuse_uring_create_queue(). fc may be NULL in the case where another thread is creating the uring in fuse_uring_create() and has set fc->ring but has not yet set ring->fc when fuse_uring_create_queue() reads ring->fc. There is another race condition as well where in fuse_uring_register(), ring->nr_queues may still be 0 and not yet set to the new value when we compare qid against it. This fix sets fc->ring only after ring->fc and ring->nr_queues have been set, which guarantees now that ring->fc is a proper pointer when any queues are created and ring->nr_queues reflects the right number of queues if ring is not NULL. We must use smp_store_release() and smp_load_acquire() semantics to ensure the ordering will remain correct where fc->ring is assigned only after ring->fc and ring->nr_queues have been assigned. Signed-off-by: Joanne Koong <joannelkoong@gmail.com> Fixes: 24fe962c86f5 ("fuse: {io-uring} Handle SQEs - register commands") Reviewed-by: Bernd Schubert <bschubert@ddn.com> Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/libxed.py')
0 files changed, 0 insertions, 0 deletions