public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Jens Axboe <axboe@kernel.dk>, Gabriel Krisman Bertazi <krisman@suse.de>
Cc: netdev@vger.kernel.org, io-uring@vger.kernel.org,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH 0/3] Introduce getsockname io_uring_cmd
Date: Wed, 19 Nov 2025 17:29:16 -0800	[thread overview]
Message-ID: <20251119172916.7fd4a8f1@kernel.org> (raw)
In-Reply-To: <8ab727b0-e377-457b-9b3e-2499ea38abc0@kernel.dk>

On Wed, 19 Nov 2025 16:30:38 -0700 Jens Axboe wrote:
> On 10/24/25 9:48 AM, Gabriel Krisman Bertazi wrote:
> > 
> > This feature has been requested a few times in the liburing repository
> > and Discord channels, such as in [1,2].  If anything, it also helps
> > solve a long standing issue in the bind-listen test that results in
> > occasional test failures.
> > 
> > The patchset is divided in three parts: Patch 1 merges the getpeername
> > and getsockname implementation in the network layer, making further
> > patches easier; Patch 2 splits out a helper used by io_uring, like done
> > for other network commands; Finally, patch 3 plumbs the new command in
> > io_uring.
> > 
> > The syscall path was tested by booting a Linux distro, which does all
> > sorts of getsockname/getpeername syscalls.  The io_uring side was tested
> > with a couple of new liburing subtests available at:
> > 
> >    https://github.com/krisman/liburing.git -b socket
> > 
> > Based on top of Jens' for-next.  
> 
> Ping netdev / networking folks on patches 1+2...

Hm, I think I was hoping to exercise the moderately recent MAINTAINERS
entry here:

NETWORKING [SOCKETS]
M:	Eric Dumazet <edumazet@google.com>
M:	Kuniyuki Iwashima <kuniyu@google.com>
M:	Paolo Abeni <pabeni@redhat.com>
M:	Willem de Bruijn <willemb@google.com>
S:	Maintained
F:	include/linux/sock_diag.h
F:	include/linux/socket.h
F:	include/linux/sockptr.h
F:	include/net/sock.h
F:	include/net/sock_reuseport.h
F:	include/uapi/linux/socket.h
F:	net/core/*sock*
F:	net/core/scm.c
F:	net/socket.c

but now I realize that the submitter hasn't actually CCed the
maintainers :S

Gabriel, please repost this with a more comprehensive CC list...

      reply	other threads:[~2025-11-20  1:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-24 15:48 [PATCH 0/3] Introduce getsockname io_uring_cmd Gabriel Krisman Bertazi
2025-10-24 15:48 ` [PATCH 1/3] socket: Unify getsockname and getpeername implementation Gabriel Krisman Bertazi
2025-10-24 15:48 ` [PATCH 2/3] socket: Split out a getsockname helper for io_uring Gabriel Krisman Bertazi
2025-10-24 15:49 ` [PATCH 3/3] io_uring: Introduce getsockname io_uring cmd Gabriel Krisman Bertazi
2025-10-25 13:27   ` Jens Axboe
2025-10-27 21:20     ` Gabriel Krisman Bertazi
2025-10-27 21:48       ` Jens Axboe
2025-10-25 13:27 ` [PATCH 0/3] Introduce getsockname io_uring_cmd Jens Axboe
2025-11-19 23:30 ` Jens Axboe
2025-11-20  1:29   ` Jakub Kicinski [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=20251119172916.7fd4a8f1@kernel.org \
    --to=kuba@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=io-uring@vger.kernel.org \
    --cc=krisman@suse.de \
    --cc=netdev@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