It is my opinion at this time that the bug is really in glibc. These
functions like _nss_extrausers_endgrent() must share state from call to
call, and therefore cannot possibly be thread safe.
Unfortunately, the fix with making the shared state thread-local could
probably make problems for caller
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libnss-extrausers (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1602264
T
Note that this is https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=831390.
We have been running with a custom build of the package, that adds
__thread to the relevant variables as suggested in that bug, and haven't
seen any crashes in this module since.
> On 13 Dec 2016, at 16:30, ChristianEhrh
Given the pre-analysis I agree with Maik, reassigning to libnss-
extrausers
** Package changed: libvirt (Ubuntu) => libnss-extrausers (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1602264
Ti
I'm pretty sure this bug is actually in libnss-extrausers (see top of
stack trace).
libvirtd is trying a getgrouplist, which is calling out to the various
NSS modules through glibc.
In libnss-extrausers, this construct in group.c:
static FILE *groupsfile = NULL;
[...]
enum nss_status _nss_extr
