Normal What were you trying to do that didn't work?
liburing 2.12 includes support for zero copy receive, among other things, which is something we'd like to make use of. This would also bring CentOS Stream 9 in line with CentOS Stream 10, which already ships 2.12. abidiff between 2.5 and 2.12 is clear, so this should be a safe rebase:
$ abidiff 9/usr/lib64/liburing.so.2.5 10/usr/lib64/liburing.so.2.12 Functions changes summary: 0 Removed, 0 Changed, 0 Added function Variables changes summary: 0 Removed, 0 Changed, 0 Added variable Function symbols changes summary: 0 Removed, 19 Added function symbols not referenced by debug info Variable symbols changes summary: 0 Removed, 0 Added variable symbol not referenced by debug info 19 Added function symbols not referenced by debug info: [A] __io_uring_clone_buffers@@LIBURING_2.10 [A] __io_uring_clone_buffers_offset@@LIBURING_2.10 [A] io_uring_buf_ring_head@@LIBURING_2.6 [A] io_uring_clone_buffers@@LIBURING_2.8 [A] io_uring_clone_buffers_offset@@LIBURING_2.9 [A] io_uring_memory_size@@LIBURING_2.11 [A] io_uring_memory_size_params@@LIBURING_2.11 [A] io_uring_register_clock@@LIBURING_2.8 [A] io_uring_register_ifq@@LIBURING_2.10 [A] io_uring_register_napi@@LIBURING_2.6 [A] io_uring_register_region@@LIBURING_2.9 [A] io_uring_register_sync_msg@@LIBURING_2.11 [A] io_uring_register_wait_reg@@LIBURING_2.9 [A] io_uring_resize_rings@@LIBURING_2.9 [A] io_uring_set_iowait@@LIBURING_2.10 [A] io_uring_submit_and_wait_min_timeout@@LIBURING_2.8 [A] io_uring_submit_and_wait_reg@@LIBURING_2.9 [A] io_uring_unregister_napi@@LIBURING_2.6 [A] io_uring_wait_cqes_min_timeout@@LIBURING_2.8 $ abidiff 9/usr/lib64/liburing-ffi.so.2.5 10/usr/lib64/liburing-ffi.so.2.12 Functions changes summary: 0 Removed, 0 Changed, 0 Added function Variables changes summary: 0 Removed, 0 Changed, 0 Added variable Function symbols changes summary: 0 Removed, 42 Added function symbols not referenced by debug info Variable symbols changes summary: 0 Removed, 0 Added variable symbol not referenced by debug info 42 Added function symbols not referenced by debug info: [A] __io_uring_clone_buffers@@LIBURING_2.10 [A] __io_uring_clone_buffers_offset@@LIBURING_2.10 [A] io_uring_buf_ring_available@@LIBURING_2.6 [A] io_uring_clone_buffers@@LIBURING_2.8 [A] io_uring_clone_buffers_offset@@LIBURING_2.9 [A] io_uring_memory_size@@LIBURING_2.11 [A] io_uring_memory_size_params@@LIBURING_2.11 [A] io_uring_prep_bind@@LIBURING_2.7 [A] io_uring_prep_cmd_discard@@LIBURING_2.8 [A] io_uring_prep_cmd_sock@@LIBURING_2.5 [A] io_uring_prep_epoll_wait@@LIBURING_2.10 [A] io_uring_prep_fadvise64@@LIBURING_2.7 [A] io_uring_prep_fixed_fd_install@@LIBURING_2.6 [A] io_uring_prep_ftruncate@@LIBURING_2.6 [A] io_uring_prep_futex_wait@@LIBURING_2.5 [A] io_uring_prep_futex_waitv@@LIBURING_2.5 [A] io_uring_prep_futex_wake@@LIBURING_2.5 [A] io_uring_prep_listen@@LIBURING_2.7 [A] io_uring_prep_madvise64@@LIBURING_2.7 [A] io_uring_prep_open@@LIBURING_2.8 [A] io_uring_prep_open_direct@@LIBURING_2.8 [A] io_uring_prep_pipe@@LIBURING_2.12 [A] io_uring_prep_pipe_direct@@LIBURING_2.12 [A] io_uring_prep_read_multishot@@LIBURING_2.5 [A] io_uring_prep_readv_fixed@@LIBURING_2.10 [A] io_uring_prep_send_bundle@@LIBURING_2.6 [A] io_uring_prep_sendmsg_zc_fixed@@LIBURING_2.10 [A] io_uring_prep_waitid@@LIBURING_2.5 [A] io_uring_prep_writev_fixed@@LIBURING_2.10 [A] io_uring_register_clock@@LIBURING_2.8 [A] io_uring_register_ifq@@LIBURING_2.10 [A] io_uring_register_napi@@LIBURING_2.4 [A] io_uring_register_region@@LIBURING_2.9 [A] io_uring_register_sync_msg@@LIBURING_2.11 [A] io_uring_register_wait_reg@@LIBURING_2.9 [A] io_uring_resize_rings@@LIBURING_2.9 [A] io_uring_set_iowait@@LIBURING_2.10 [A] io_uring_sqe_set_buf_group@@LIBURING_2.9 [A] io_uring_submit_and_wait_min_timeout@@LIBURING_2.8 [A] io_uring_submit_and_wait_reg@@LIBURING_2.9 [A] io_uring_unregister_napi@@LIBURING_2.4 [A] io_uring_wait_cqes_min_timeout@@LIBURING_2.8 $
What is the impact of this issue to you?
We can't leverage features in liburing 2.12
Please provide the package NVR for which the bug is seen:
How reproducible is this bug?:
always
Steps to reproduce
- dnf install liburing
Expected results
liburing 2.12 is available
Actual results
liburing 2.12 is not available
