summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorPavel Begunkov <asml.silence@gmail.com>2026-03-02 13:10:37 +0000
committerJens Axboe <axboe@kernel.dk>2026-03-09 07:21:54 -0600
commitd8345a21902af5d754f2c2aadf877de989e3cac3 (patch)
treee334f79568a7906e08a665c42c5bc7acc7394243 /tools/perf/scripts/python/stackcollapse.py
parent0e78aa188cbddc6311ff24938b1c8d3850b35708 (diff)
io_uring/timeout: immediate timeout arg
One the things the user has always keep in mind is that any user pointers they put into an SQE is not going to be read by the kernel until submission happens, and the user has to ensure the pointee stays alive until then. For example, snippet below will lead to UAF of the on stack variable ts. Instead of passing the timeout value as a pointer allow to store it immediately in the SQE. The user has to set a new flag called IORING_TIMEOUT_IMMEDIATE_ARG, in which case sqe->addr for timeout or sqe->addr2 for timeout update requests will be interpreted as a time value in nanosecods. void prep_timeout(struct io_uring_sqe *sqe) { struct __kernel_timespec ts = {...}; prep_timeout(sqe, &ts); } void submit() { sqe = get_sqe(); prep_timeout(sqe); io_uring_submit(); } Signed-off-by: Pavel Begunkov <asml.silence@gmail.com> Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions