From: Gabriel Krisman Bertazi <krisman@suse.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: Gabriel Krisman Bertazi <krisman@suse.de>,
io-uring@vger.kernel.org, csander@purestorage.com
Subject: [PATCH liburing v3 0/4] liburing: getsockname support
Date: Wed, 3 Dec 2025 14:52:14 -0500 [thread overview]
Message-ID: <20251203195223.3578559-1-krisman@suse.de> (raw)
Changes since v2:
The main change from the previous iteration is ensuring the test won't
regress in older kernels. This is done by installing the socket fd and
fallbacking to the syscall. I avoided reverting to using a fixed port
because that is flaky and would also require recreating the socket.
This is the library counterpart for the kernel support. Also available
at:
https://github.com/krisman/liburing -b socket
---
CC: io-uring@vger.kernel.org
CC: csander@purestorage.com
Gabriel Krisman Bertazi (4):
liburing: Introduce getsockname operation
test/bind-listen.t: Use ephemeral port
bind-listen.t: Add tests for getsockname
man/io_uring_prep_getsockname.3: Add man page
man/io_uring_prep_getsockname.3 | 78 +++++++++++++
src/include/liburing.h | 13 +++
src/include/liburing/io_uring.h | 1 +
test/bind-listen.c | 188 +++++++++++++++++++++++++++++---
4 files changed, 267 insertions(+), 13 deletions(-)
create mode 100644 man/io_uring_prep_getsockname.3
--
2.52.0
next reply other threads:[~2025-12-03 19:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 19:52 Gabriel Krisman Bertazi [this message]
2025-12-03 19:52 ` [PATCH liburing v3 1/4] liburing: Introduce getsockname operation Gabriel Krisman Bertazi
2025-12-03 19:52 ` [PATCH liburing v3 2/4] test/bind-listen.t: Use ephemeral port Gabriel Krisman Bertazi
2025-12-03 19:52 ` [PATCH liburing v3 3/4] bind-listen.t: Add tests for getsockname Gabriel Krisman Bertazi
2025-12-03 19:52 ` [PATCH liburing v3 4/4] man/io_uring_prep_getsockname.3: Add man page Gabriel Krisman Bertazi
2025-12-03 20:23 ` [PATCH liburing v3 0/4] liburing: getsockname support Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251203195223.3578559-1-krisman@suse.de \
--to=krisman@suse.de \
--cc=axboe@kernel.dk \
--cc=csander@purestorage.com \
--cc=io-uring@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox