From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top,
Andrew Sayers <andrew-bugs.passt.top@pileofstuff.org>,
Paul Holzinger <pholzing@redhat.com>
Subject: Re: [PATCH 1/2] conf: Split add_dns_resolv() into separate IPv4 and IPv6 versions
Date: Mon, 14 Apr 2025 11:30:58 +0200 [thread overview]
Message-ID: <20250414113058.2886caf5@elisabeth> (raw)
In-Reply-To: <Z_xtav84GrpdyKzG@zatzit>
On Mon, 14 Apr 2025 12:05:30 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:
> On Fri, Apr 11, 2025 at 11:14:38AM +0200, Stefano Brivio wrote:
> > Not really valuable by itself, but dropping one level of nested blocks
> > makes the next change more convenient.
> >
> > No functional changes intended.
> >
> > Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
>
> Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
>
> Not in scope for this code motion, but I did spot another bug here..
>
> > ---
> > conf.c | 101 ++++++++++++++++++++++++++++++++++-----------------------
> > 1 file changed, 60 insertions(+), 41 deletions(-)
> >
> > diff --git a/conf.c b/conf.c
> > index 168646f..18ed11c 100644
> > --- a/conf.c
> > +++ b/conf.c
> > @@ -414,6 +414,62 @@ static unsigned add_dns6(struct ctx *c, const struct in6_addr *addr,
> > return 1;
> > }
> >
> > +/**
> > + * add_dns_resolv4() - Possibly add one IPv4 nameserver from host's resolv.conf
> > + * @c: Execution context
> > + * @ns: Nameserver address
> > + * @idx: Pointer to index of current IPv4 resolver entry, set on return
> > + */
> > +static void add_dns_resolv4(struct ctx *c, struct in_addr *ns, unsigned *idx)
> > +{
> > + if (IN4_IS_ADDR_UNSPECIFIED(&c->ip4.dns_host))
> > + c->ip4.dns_host = *ns;
> > +
> > + /* Special handling if guest or container can only access local
> > + * addresses via redirect, or if the host gateway is also a resolver and
> > + * we shadow its address
> > + */
> > + if (IN4_IS_ADDR_LOOPBACK(ns) ||
> > + IN4_ARE_ADDR_EQUAL(ns, &c->ip4.map_host_loopback)) {
>
> The second bit here is wrong. We check if the nameserver address is
> the --map-host-loopback address - meaning we can't use it in the
> guest - then try to use it in the guest anyway. That path should
> instead return, like the ns == 127.0.0.1 && map_host_loopback ==
> 0.0.0.0 case.
I'm not sure why we can't use the --map-host-loopback address in the
guest. DNS traffic has the priority, right?
Together with 2/2, do you still see an issue?
That is, if there's no --dns-forward and no address maps to a local
resolver, there's no way to reach the local resolver and we return, but
in any other case, I guess we can pick that address.
--
Stefano
next prev parent reply other threads:[~2025-04-14 9:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 9:14 [PATCH 0/2] Fix --dns-forward with --no-map-gw Stefano Brivio
2025-04-11 9:14 ` [PATCH 1/2] conf: Split add_dns_resolv() into separate IPv4 and IPv6 versions Stefano Brivio
2025-04-14 2:05 ` David Gibson
2025-04-14 9:30 ` Stefano Brivio [this message]
2025-04-11 9:14 ` [PATCH 2/2] conf: Honour --dns-forward for local resolver even with --no-map-gw Stefano Brivio
2025-04-14 2:07 ` David Gibson
2025-04-11 15:14 ` [PATCH 0/2] Fix --dns-forward " Paul Holzinger
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=20250414113058.2886caf5@elisabeth \
--to=sbrivio@redhat.com \
--cc=andrew-bugs.passt.top@pileofstuff.org \
--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).