From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Jon Maloy <jmaloy@redhat.com>,
passt-dev@passt.top, lvivier@redhat.com, dgibson@redhat.com
Subject: Re: [PATCH v2] tcp.c: leverage MSG_PEEK with offset kernel capability when available
Date: Fri, 19 Jan 2024 11:45:05 +0100 [thread overview]
Message-ID: <20240119105630.089c5d34@elisabeth> (raw)
In-Reply-To: <Zam8roGyDLWIJHsD@zatzit>
On Fri, 19 Jan 2024 11:05:02 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:
> On Thu, Jan 18, 2024 at 05:23:26PM +0100, Stefano Brivio wrote:
> > Not a full review, but a couple of comments, mostly about stuff I also
> > had in pkt_selfie.c (review of v1):
> >
> > On Thu, 18 Jan 2024 14:05:38 +1100
> > David Gibson <david@gibson.dropbear.id.au> wrote:
> >
> > > On Sun, Jan 14, 2024 at 01:07:55PM -0500, Jon Maloy wrote:
> > > >
> > > > [...]
> > > >
> > > > +
> > > > + s[0] = socket(AF_INET, SOCK_STREAM, IPPROTO_TCP);
> > > > + s[1] = socket(AF_INET, SOCK_STREAM | SOCK_NONBLOCK, IPPROTO_TCP);
> > > > + if (s[0] < 0 || s[1] < 0) {
> > > > + perror("Temporary probe socket creation failed\n");
> > > > + goto out;
> > > > + }
> > > > + if (0 > bind(s[0], &a, sizeof(a))) {
> > >
> > > Since the socket address is unspecified, why do you need to bind at
> > > all? It might be clearer to explicitly set a to localhost + a
> > > specific port - because you're in a temporary namespace, you can rely
> > > on every port being available.
> >
> > There are two advantages of bind() without port, and then getsockname():
> > first, ip_unprivileged_port_start might have whatever value in our new
> > namespace (we don't touch it), and I wouldn't take for granted we'll
> > have CAP_SYS_ADMIN in it for all the possible start-up combinations.
> >
> > Second, there's no need for a magic value.
>
> Good point. Note that at present we're not bind()ing to an address
> either.
>
> > > > + perror("Temporary probe socket bind() failed\n");
> > > > + goto out;
> > > > + }
> > > > + if (0 > getsockname(s[0], &a, &((socklen_t) { sizeof(a) }))) {
> > > > + perror("Temporary probe socket getsockname() failed\n");
> > > > + goto out;
> > > > + }
> > > > + if (0 > listen(s[0], 0)) {
> > > > + perror("Temporary probe socket listen() failed\n");
> > > > + goto out;
> > > > + }
> > > > + if (0 <= connect(s[1], &a, sizeof(a)) || errno != EINPROGRESS) {
> > > > + perror("Temporary probe socket connect() failed\n");
> > > > + goto out;
> > > > + }
> > >
> > > This is assuming that a will now contain the correct address to
> > > connect to. Although it will have the right port, I think the address
> > > may still be unspecified for the listening socket.
> >
> > Hmm, why? From getsockname(2):
> >
> > getsockname() returns the current address to which the socket
> > sockfd is bound [...]
>
> But we've only bound ourselves to 0.0.0.0, which while perfectly
> cromulent for a listening socket, is no good for connect().
Hah, "cromulent" just embiggened my dictionary! Why not, though? From
RFC 6890, 2.2.2:
+----------------------+----------------------------+
| Attribute | Value |
+----------------------+----------------------------+
| Address Block | 0.0.0.0/8 |
| Name | "This host on this network"|
and:
$ strace -e connect ./pkt_selfie
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=891325, si_uid=1000, si_status=0, si_utime=0, si_stime=0} ---
connect(5, {sa_family=AF_INET, sin_port=htons(51155), sin_addr=inet_addr("0.0.0.0")}, 16) = -1 EINPROGRESS (Operation now in progress)
MSG_PEEK with offset not supported
+++ exited with 0 +++
with pkt_selfie.c from review of v1:
https://archives.passt.top/passt-dev/20231206160808.3d312733@elisabeth/
--
Stefano
next prev parent reply other threads:[~2024-01-19 10:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-14 18:07 [PATCH v2] tcp.c: leverage MSG_PEEK with offset kernel capability when available Jon Maloy
2024-01-18 3:05 ` David Gibson
2024-01-18 16:23 ` Stefano Brivio
2024-01-19 0:05 ` David Gibson
2024-01-19 10:45 ` Stefano Brivio [this message]
2024-01-20 4:47 ` David Gibson
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=20240119105630.089c5d34@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=dgibson@redhat.com \
--cc=jmaloy@redhat.com \
--cc=lvivier@redhat.com \
--cc=passt-dev@passt.top \
/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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).