From: Jens Axboe <axboe@kernel.dk>
To: Gabriel Krisman Bertazi <krisman@suse.de>
Cc: io-uring@vger.kernel.org, csander@purestorage.com
Subject: Re: [PATCH liburing v3 0/4] liburing: getsockname support
Date: Wed, 03 Dec 2025 13:23:55 -0700 [thread overview]
Message-ID: <176479343527.889438.3714060142202075784.b4-ty@kernel.dk> (raw)
In-Reply-To: <20251203195223.3578559-1-krisman@suse.de>
On Wed, 03 Dec 2025 14:52:14 -0500, Gabriel Krisman Bertazi wrote:
> 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.
>
> [...]
Applied, thanks!
[1/4] liburing: Introduce getsockname operation
commit: c1541b0421602ea26ce1c5bba9f3a9403224f971
[2/4] test/bind-listen.t: Use ephemeral port
commit: 79ef754d7bff5c8216b57b4eed42448f28a4e88a
[3/4] bind-listen.t: Add tests for getsockname
commit: a75b1b69e437311c7b3c9839a7d4510fb9be20a3
[4/4] man/io_uring_prep_getsockname.3: Add man page
commit: 419c9ca5bf5d6dd942504213a68a4862e733392b
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-12-03 20:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 19:52 [PATCH liburing v3 0/4] liburing: getsockname support Gabriel Krisman Bertazi
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 ` Jens Axboe [this message]
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=176479343527.889438.3714060142202075784.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=csander@purestorage.com \
--cc=io-uring@vger.kernel.org \
--cc=krisman@suse.de \
/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