public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fabian@ritter-vogt.de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nscd/29415] New: getaddrinfo with AI_ADDRCONFIG returns addresses with wrong family
Date: Wed, 27 Jul 2022 09:36:31 +0000	[thread overview]
Message-ID: <bug-29415-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=29415

            Bug ID: 29415
           Summary: getaddrinfo with AI_ADDRCONFIG returns addresses with
                    wrong family
           Product: glibc
           Version: 2.35
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: nscd
          Assignee: unassigned at sourceware dot org
          Reporter: fabian@ritter-vogt.de
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---

Processes cache network interface information such as whether IPv4 or IPv6
are enabled. This is only checked again if the "netlink timestamp" provided
by nscd changed, which is triggered by netlink socket activity.

However, this mechanism is currently broken. This means that e.g. processes
which started before network configuration got unusuable addresses from
getaddrinfo, like IPv6 only even though only IPv4 is available:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1041

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2022-07-27  9:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27  9:36 fabian@ritter-vogt.de [this message]
2022-08-29 13:52 ` [Bug nscd/29415] " mliska at suse dot cz
2022-08-29 19:56 ` mliska at suse dot cz
2022-08-30  6:47 ` fweimer 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=bug-29415-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).