From: DJ Delorie <dj@redhat.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] nss_dns: Do not call res_dnok in getnetby* implementation
Date: Mon, 11 Mar 2019 15:35:58 -0400 [thread overview]
Message-ID: <xnwol55hlt.fsf@greed.delorie.com> (raw)
In-Reply-To: <20190308204424.0744F80DD6B5@oldenburg2.str.redhat.com> (message from Florian Weimer on Fri, 08 Mar 2019 21:44:23 +0100)
Florian Weimer <fweimer@redhat.com> writes:
> 2019-03-08 Florian Weimer <fweimer@redhat.com>
>
> * resolv/nss_dns/dns-network.c (getanswer_r): Do not call
> res_dnok.
I checked and it does seem that *bp only comes from ns_name_ntop, so as
long as the assumption that ns_name_ntop always produces a valid name is
valid, this patch looks OK to me.
next prev parent reply other threads:[~2019-03-11 19:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 20:44 [PATCH] nss_dns: Do not call res_dnok in getnetby* implementation Florian Weimer
2019-03-11 19:35 ` DJ Delorie [this message]
2020-06-04 13:08 ` Carlos O'Donell via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xnwol55hlt.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).