[Bug libc/17363] getnetgrent returns a truncated list if one of the netgroups in its tree is empty

[cvs-commit at gcc dot gnu.org]

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

--- Comment #1 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  58b930ae216bfa98cd60212b954b07b9963d6d04 (commit)
      from  71ae86478edc7b21872464f43fb29ff650c1681a (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=58b930ae216bfa98cd60212b954b07b9963d6d04

commit 58b930ae216bfa98cd60212b954b07b9963d6d04
Author: Siddhesh Poyarekar <siddhesh@redhat.com>
Date:   Wed Sep 10 21:51:50 2014 +0530

    Return failure in getnetgrent only when all netgroups have been searched
(#17363)

    The netgroups lookup code fails when one of the groups in the search
    tree is empty.  In such a case it only returns the leaves of the tree
    after the blank netgroup.  This is because the line parser returns a
    NOTFOUND status when the netgroup exists but is empty.  The
    __getnetgrent_internal implementation needs to be fixed to try
    remaining groups if the current group is entry.  This patch implements
    this fix.  Tested on x86_64.

        [BZ #17363]
        * inet/getnetgrent_r.c (__internal_getnetgrent_r): Try next
        group if the current group is empty.

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

Summary of changes:
 ChangeLog            |    6 ++++++
 NEWS                 |    6 ++++++
 inet/getnetgrent_r.c |    5 ++++-
 3 files changed, 16 insertions(+), 1 deletions(-)

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