From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH] netlink: Ignore EHOSTUNREACH failures when duplicating routes
Date: Wed, 19 Jun 2024 11:56:33 +1000 [thread overview]
Message-ID: <ZnI60fC9LYuwMU4q@zatzit> (raw)
In-Reply-To: <20240618115611.1798383-1-sbrivio@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2350 bytes --]
On Tue, Jun 18, 2024 at 01:56:11PM +0200, Stefano Brivio wrote:
> To implicitly resolve possible dependencies between routes as we
> duplicate them into the target namespace, we go through a set of n
> routes n times, and ignore EEXIST responses to netlink messages (we
> already inserted the route) and ENETUNREACH (we didn't insert the
> route yet, but we need to insert another one first).
>
> Until now, we didn't ignore EHOSTUNREACH responses. However,
> NetworkManager users with multiple non-subnet routes for the same
> interface report that pasta exits with "no route to host" while
> duplicating routes.
>
> This happens because NetworkManager sets the 'noprefixroute' attribute
> on addresses, meaning that the kernel won't create subnet routes
> automatically depending on the prefix length of the address. We copy
> this attribute as we copy the address into the target namespace, and
> as a result, the kernel doesn't create subnet routes in the target
> namespace either.
>
> This means that the gateway for routes that are inserted later can be
> unreachable at some points during the sequence of route duplication.
> That is, we don't just have dependencies between regular routes, but
> we can also have dependencies between regular routes and subnet
> routes, as subnet routes are not automatically inserted in advance.
Nice explanation, thank you.
> Link: https://github.com/containers/podman/issues/22824
> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> netlink.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/netlink.c b/netlink.c
> index 4dbddb2..0be4ea3 100644
> --- a/netlink.c
> +++ b/netlink.c
> @@ -655,7 +655,8 @@ int nl_route_dup(int s_src, unsigned int ifi_src,
> rc = nl_do(s_dst, nh, RTM_NEWROUTE,
> (flags & ~NLM_F_DUMP_FILTERED) | NLM_F_CREATE,
> nh->nlmsg_len);
> - if (rc < 0 && rc != -ENETUNREACH && rc != -EEXIST)
> + if (rc < 0 && rc != -EEXIST &&
> + rc != -ENETUNREACH && rc != -EHOSTUNREACH)
> return rc;
> }
> }
--
David Gibson (he or they) | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you, not the other way
| around.
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-06-19 1:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 11:56 [PATCH] netlink: Ignore EHOSTUNREACH failures when duplicating routes Stefano Brivio
2024-06-19 1:56 ` David Gibson [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=ZnI60fC9LYuwMU4q@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=sbrivio@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).