[Bug nscd/16878] nscd enters busy loop on long netgroup entry via nss_ldap of nslcd

["cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

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

--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".

The branch, master has been updated
       via  c3ec475c5dd16499aa040908e11d382c3ded9692 (commit)
      from  aa2f176d6f75b86b91e544c2e494066ac8f88cbd (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=c3ec475c5dd16499aa040908e11d382c3ded9692

commit c3ec475c5dd16499aa040908e11d382c3ded9692
Author: Siddhesh Poyarekar <siddhesh@redhat.com>
Date:   Mon May 26 11:40:08 2014 +0530

    Use NSS_STATUS_TRYAGAIN to indicate insufficient buffer (BZ #16878)

    The netgroups nss modules in the glibc tree use NSS_STATUS_UNAVAIL
    (with errno as ERANGE) when the supplied buffer does not have
    sufficient space for the result.  This is wrong, because the canonical
    way to indicate insufficient buffer is to set the errno to ERANGE and
    the status to NSS_STATUS_TRYAGAIN, as is used by all other modules.

    This fixes nscd behaviour when the nss_ldap module returns
    NSS_STATUS_TRYAGAIN to indicate that a netgroup entry is too long to
    fit into the supplied buffer.

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog                    |    8 ++++++++
 NEWS                         |    6 +++---
 nscd/netgroupcache.c         |   14 ++++++++------
 nss/nss_files/files-netgrp.c |    2 +-
 4 files changed, 20 insertions(+), 10 deletions(-)

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