public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pasky at suse dot cz" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/9753] New: __res_maybe_init() not reinitializing state properly
Date: Sat, 17 Jan 2009 01:05:00 -0000	[thread overview]
Message-ID: <20090117010542.9753.pasky@suse.cz> (raw)

With the latest CVS changes in libresolv (also included in FC10),
res_state.nscount is not always initialized to 1 anymore. However,
__res_maybe_init() code will reinitialize the state only if nscount is > 0 for
unknown reasons - I think it is just an oversight in the original code. Attached
patch proposes to fix it.

This exhibits in random resolution failures if nscd is started before
/etc/resolv.conf has been set up - I did not go through the code in detail but I
assume the existing threads will never get the new res state because nscount ==
0 in their original state.

-- 
           Summary: __res_maybe_init() not reinitializing state properly
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: pasky at suse dot cz
                CC: glibc-bugs at sources dot redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=9753

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2009-01-17  1:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-17  1:05 pasky at suse dot cz [this message]
2009-01-17  1:07 ` [Bug libc/9753] " pasky at suse dot cz
2009-02-07  4:29 ` drepper at redhat dot com

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=20090117010542.9753.pasky@suse.cz \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.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.
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).