From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 89176 invoked by alias); 8 Jan 2020 07:25:26 -0000 Mailing-List: contact libc-help-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: libc-help-owner@sourceware.org Received: (qmail 89166 invoked by uid 89); 8 Jan 2020 07:25:26 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.5 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.1 spammy=H*Ad:U*libc-help, corruption, H*MI:sk:CAMvyGd, H*f:sk:CAMvyGd X-HELO: mail-qk1-f177.google.com Received: from mail-qk1-f177.google.com (HELO mail-qk1-f177.google.com) (209.85.222.177) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 08 Jan 2020 07:25:25 +0000 Received: by mail-qk1-f177.google.com with SMTP id 21so1817599qky.4 for ; Tue, 07 Jan 2020 23:25:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xwKvcvxE9VKJ8CNgMVmoYBovY3ftIocx9OEohOKR/q0=; b=iTuhpSpDBciSxrr/kQvYJIheTeBfj+2ghfaqWMVgYPikFn28xjwWr95HkV6RGX/ISi apKjz0U+lwBCpDpbQRqfM4//xlGBls4CURjfGi0GvJeUzecN+48+FrLAijGpe1M7nD+O AdYWkNGGK5skdMqHf9OMkFqG4WGChU4HP3nI7rhb0WbPnCIu9Ex6w6oCY/iBi5571l7G n9cVdZF1bLOvaCqcZ7LgmKeXpCEQpQBPWo8TnnYI5H16TQtX/06uhTbgTymOAGIo5nVS R90sgx92eIJVLqKCmtNj/b3VnWEt4ZrgZLHIVWpzfE7I15v0WJpbC1XOgiixWbpe9HOY X8Xg== MIME-Version: 1.0 References: <87lfqjwsvh.fsf@oldenburg2.str.redhat.com> <87y2ujtps2.fsf@oldenburg2.str.redhat.com> In-Reply-To: <87y2ujtps2.fsf@oldenburg2.str.redhat.com> From: Tarun Tej K Date: Wed, 08 Jan 2020 07:25:00 -0000 Message-ID: Subject: Re: getaddrinfo() fails to use latest DNS address - v2.27 To: Florian Weimer Cc: libc-help@sourceware.org Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2020-01/txt/msg00009.txt.bz2 > 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