Created attachment 1061638 [details] gdb "where full" results, plus a couple of variables Description of problem: With a working hesiod configuration, and hesiod enabled for group resolution, multiple applications are crashing while initializing a supplemental groups list. Version-Release number of selected component (if applicable): glibc-2.21.90-21.fc23.x86_64 coreutils-8.24-2.fc23.x86_64 used to reproduce the bug How reproducible: Always Steps to Reproduce: 1. cat > /etc/hesiod.conf << EOF lhs=.hs rhs=.devel.redhat.com EOF 2. Add "hesiod" as a source for "group" information in /etc/nsswitch.conf. Mine reads "files hesiod". 3. Run "groups nalin" or similar. Actual results: "groups" segfaults. I'll attach the gdb backtrace. Expected results: The expected groups list. Additional info:
Caused by upstream commit 2212c1420c92a33b0e0bd9a34938c9814a56c0f7. Bug reported upstream. There are various ways to fix this, but which approach is best is unclear.
Reproducer without changing /etc: cat > /etc/hesiod.conf << EOF lhs=.hs rhs=.devel.redhat.com EOF HESIOD_CONFIG=hesiod.conf getent -s hesiod group 0 0 I'm reverting the upstream commit which introduced this bug.
glibc-2.22-9.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-0f9e9a34ce
glibc-2.22-9.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-0f9e9a34ce
glibc-2.22-9.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
Due to this change, a glibc update to the fixed versions *without* a reboot (or process restart) may cause name resolution failures.