public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top, Paul Holzinger <pholzing@redhat.com>
Subject: Re: [PATCH 5/7] netlink, pasta: Fetch link-local address from namespace interface once it's up
Date: Thu, 15 Aug 2024 08:53:02 +0200	[thread overview]
Message-ID: <20240815085302.7df90fa6@elisabeth> (raw)
In-Reply-To: <Zr1wSrzT_lzakOjT@zatzit.fritz.box>

On Thu, 15 Aug 2024 13:04:42 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:

> On Thu, Aug 15, 2024 at 12:54:27AM +0200, Stefano Brivio wrote:
> > As soon as we bring up the interface, the Linux kernel will set up a
> > link-local address for it, so we can fetch it and start using right
> > away, if we need a link-local address to communicate to the container
> > before we see any traffic coming from it.
> > 
> > Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
> > ---
> >  netlink.c | 47 +++++++++++++++++++++++++++++++++++++++++++++++
> >  netlink.h |  1 +
> >  pasta.c   |  7 +++++++
> >  3 files changed, 55 insertions(+)
> > 
> > diff --git a/netlink.c b/netlink.c
> > index 4b49de1..3b37087 100644
> > --- a/netlink.c
> > +++ b/netlink.c
> > @@ -836,6 +836,53 @@ int nl_addr_get(int s, unsigned int ifi, sa_family_t af,
> >  	return status;
> >  }
> >  
> > +/**
> > + * nl_addr_get_ll() - Get first IPv6 link-local address for a given interface
> > + * @s:		Netlink socket
> > + * @ifi:	Interface index in outer network namespace
> > + * @addr:	Link-local address to fill
> > + *
> > + * Return: 0 on success, negative error code on failure
> > + */
> > +int nl_addr_get_ll(int s, unsigned int ifi, void *addr)  
> 
> Given this is explicitly for IPv6, I don't see a reason not to use
> (struct in6_addr *addr) for greater type safety.

I'll change that.

> > +{
> > +	struct req_t {
> > +		struct nlmsghdr nlh;
> > +		struct ifaddrmsg ifa;
> > +	} req = {
> > +		.ifa.ifa_family		= AF_INET6,
> > +		.ifa.ifa_index		= ifi,
> > +	};
> > +	struct nlmsghdr *nh;
> > +	bool found = false;
> > +	char buf[NLBUFSIZ];
> > +	ssize_t status;
> > +	uint32_t seq;
> > +
> > +	seq = nl_send(s, &req, RTM_GETADDR, NLM_F_DUMP, sizeof(req));
> > +	nl_foreach_oftype(nh, status, s, buf, seq, RTM_NEWADDR) {
> > +		struct ifaddrmsg *ifa = (struct ifaddrmsg *)NLMSG_DATA(nh);
> > +		struct rtattr *rta;
> > +		size_t na;
> > +
> > +		if (ifa->ifa_index != ifi || ifa->ifa_scope != RT_SCOPE_LINK ||
> > +		    found)
> > +			continue;
> > +
> > +		for (rta = IFA_RTA(ifa), na = IFA_PAYLOAD(nh); RTA_OK(rta, na);
> > +		     rta = RTA_NEXT(rta, na)) {
> > +			if (rta->rta_type != IFA_ADDRESS)
> > +				continue;
> > +
> > +			if (!found) {
> > +				memcpy(addr, RTA_DATA(rta), RTA_PAYLOAD(rta));
> > +				found = true;
> > +			}
> > +		}
> > +	}
> > +	return status;
> > +}
> > +
> >  /**
> >   * nl_add_set() - Set IP addresses for given interface and address family
> >   * @s:		Netlink socket
> > diff --git a/netlink.h b/netlink.h
> > index 66a44ad..bdfdef0 100644
> > --- a/netlink.h
> > +++ b/netlink.h
> > @@ -19,6 +19,7 @@ int nl_addr_get(int s, unsigned int ifi, sa_family_t af,
> >  		void *addr, int *prefix_len, void *addr_l);
> >  int nl_addr_set(int s, unsigned int ifi, sa_family_t af,
> >  		const void *addr, int prefix_len);
> > +int nl_addr_get_ll(int s, unsigned int ifi, void *addr);
> >  int nl_addr_set_ll_nodad(int s, unsigned int ifi);
> >  int nl_addr_dup(int s_src, unsigned int ifi_src,
> >  		int s_dst, unsigned int ifi_dst, sa_family_t af);
> > diff --git a/pasta.c b/pasta.c
> > index 838bbb3..cebf54f 100644
> > --- a/pasta.c
> > +++ b/pasta.c
> > @@ -340,6 +340,13 @@ void pasta_ns_conf(struct ctx *c)
> >  		}
> >  
> >  		if (c->ifi6) {
> > +			rc = nl_addr_get_ll(nl_sock_ns, c->pasta_ifi,
> > +					    &c->ip6.addr_ll_seen);
> > +			if (rc < 0) {
> > +				die("Can't fetch LL address from namespace: %s",
> > +				    strerror(-rc));  
> 
> Again, we can generally cope with not having an addr_ll_seen
> initially, so I think a warn() would make more sense.

Of course. I'll fix this as well.

-- 
Stefano


  reply	other threads:[~2024-08-15  6:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-14 22:54 [PATCH 0/7] Prevent DAD for link-local addresses in containers Stefano Brivio
2024-08-14 22:54 ` [PATCH 1/7] netlink: Fix typo in function comment for nl_addr_get() Stefano Brivio
2024-08-15  2:39   ` David Gibson
2024-08-14 22:54 ` [PATCH 2/7] netlink, pasta: Split MTU setting functionality out of nl_link_up() Stefano Brivio
2024-08-15  2:41   ` David Gibson
2024-08-14 22:54 ` [PATCH 3/7] netlink, pasta: Turn nl_link_up() into a generic function to set link flags Stefano Brivio
2024-08-15  2:42   ` David Gibson
2024-08-14 22:54 ` [PATCH 4/7] netlink, pasta: Disable DAD for link-local addresses on namespace interface Stefano Brivio
2024-08-15  3:01   ` David Gibson
2024-08-15  6:52     ` Stefano Brivio
2024-08-14 22:54 ` [PATCH 5/7] netlink, pasta: Fetch link-local address from namespace interface once it's up Stefano Brivio
2024-08-15  3:04   ` David Gibson
2024-08-15  6:53     ` Stefano Brivio [this message]
2024-08-14 22:54 ` [PATCH 6/7] pasta: Disable neighbour solicitations on device up to prevent DAD Stefano Brivio
2024-08-15  3:06   ` David Gibson
2024-08-14 22:54 ` [PATCH 7/7] netlink: Fix typo in function comment for nl_addr_set() Stefano Brivio
2024-08-15  3:07   ` 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=20240815085302.7df90fa6@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=passt-dev@passt.top \
    --cc=pholzing@redhat.com \
    /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).