summaryrefslogtreecommitdiff
path: root/arch/arm64/kvm
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2025-01-04 01:45:59 +0300
committerLinus Torvalds <torvalds@linux-foundation.org>2025-01-04 01:45:59 +0300
commita984e234fcdce25a276be882c799e5fda1b32812 (patch)
treeb776366a18ff8059a0660bc80ac11461744d4aee /arch/arm64/kvm
parentaba74e639f8d76d29b94991615e33319d7371b63 (diff)
parented123c948d06688d10f3b10a7bce1d6fbfd1ed07 (diff)
downloadlinux-a984e234fcdce25a276be882c799e5fda1b32812.tar.xz
Merge tag 'io_uring-6.13-20250103' of git://git.kernel.dk/linux
Pull io_uring fixes from Jens Axboe: - Fix an issue with the read multishot support and posting of CQEs from io-wq context - Fix a regression introduced in this cycle, where making the timeout lock a raw one uncovered another locking dependency. As a result, move the timeout flushing outside of the timeout lock, punting them to a local list first - Fix use of an uninitialized variable in io_async_msghdr. Doesn't really matter functionally, but silences a valid KMSAN complaint that it's not always initialized - Fix use of incrementally provided buffers for read on non-pollable files, where the buffer always gets committed upfront. Unfortunately the buffer address isn't resolved first, so the read ends up using the updated rather than the current value * tag 'io_uring-6.13-20250103' of git://git.kernel.dk/linux: io_uring/kbuf: use pre-committed buffer address for non-pollable file io_uring/net: always initialize kmsg->msg.msg_inq upfront io_uring/timeout: flush timeouts outside of the timeout lock io_uring/rw: fix downgraded mshot read
Diffstat (limited to 'arch/arm64/kvm')
0 files changed, 0 insertions, 0 deletions