public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "schwab@linux-m68k.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nss/27416] New: __nss_database_lookup2 ignores defconfig
Date: Sun, 14 Feb 2021 19:58:05 +0000 [thread overview]
Message-ID: <bug-27416-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27416
Bug ID: 27416
Summary: __nss_database_lookup2 ignores defconfig
Product: glibc
Version: 2.33
Status: NEW
Severity: normal
Priority: P2
Component: nss
Assignee: unassigned at sourceware dot org
Reporter: schwab@linux-m68k.org
CC: dj at redhat dot com
Target Milestone: ---
If nsswitch.conf contains no entry for a nonstandard database it is assumed
empty, even if the caller of __nss_database_lookup2 provides a default config.
This breaks nss_compat.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-02-14 19:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 19:58 schwab@linux-m68k.org [this message]
2021-02-14 20:05 ` [Bug nss/27416] __nss_database_lookup2 ignores defconfig and alternate_name schwab@linux-m68k.org
2022-01-09 21:38 ` aurelien at aurel32 dot net
2022-01-10 12:37 ` 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-27416-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).