From: Tarun Tej K <tarun4690@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-help@sourceware.org
Subject: Re: getaddrinfo() fails to use latest DNS address - v2.27
Date: Wed, 08 Jan 2020 07:25:00 -0000 [thread overview]
Message-ID: <CAMvyGd8cFmVcmXzb1cae7urej8Kw1g04qJh3CLhnv_1UmcYNbQ@mail.gmail.com> (raw)
In-Reply-To: <87y2ujtps2.fsf@oldenburg2.str.redhat.com>
> It could mean that reloading is disabled. There are a few possible
> causes:
>
> * The noreload option is specified in /etc/resolv.conf.
>
> * The application sets RES_NORELOAD in res.options directly.
>
> * The application updates other data in _res, so that it no longer
> matches the previously read configuration.
>
> The last part could also happen due to completely different bugs,
> e.g. after heap corruption.
>
> Regarding bugs, I'm not aware of any. In general, reloading of the
> configuration is inhibited for a thread if it has an attached context.
> Maybe there is a bug in this area. Do you have a coredump? It should
> be visible in the current variable in resolv/resolv_context.c.
>
> > Also could you suggest any other tool other than strace to see the
> > call trace of libc runtime?
>
> Systemtap might be an option.
>
Thanks. I'll try those.
Is there any function apart from res_init() and res_ninit() which will
clear the global conf and force to load the global conf freshly upon
the next getaddrinfo()?
Thanks
Tarun
next prev parent reply other threads:[~2020-01-08 7:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 6:01 Tarun Tej K
2020-01-07 8:52 ` Florian Weimer
2020-01-07 9:45 ` Tarun Tej K
2020-01-07 12:27 ` Florian Weimer
2020-01-08 7:25 ` Tarun Tej K [this message]
2020-01-08 7:41 ` Florian Weimer
2020-01-20 14:50 ` Filip Ochnik
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=CAMvyGd8cFmVcmXzb1cae7urej8Kw1g04qJh3CLhnv_1UmcYNbQ@mail.gmail.com \
--to=tarun4690@gmail.com \
--cc=fweimer@redhat.com \
--cc=libc-help@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).