[Bug nscd/26130] New: Inconsistent nscd cache during pruning

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[Bug nscd/26130] New: Inconsistent nscd cache during pruning

Sourceware - glibc-bugs mailing list
https://sourceware.org/bugzilla/show_bug.cgi?id=26130

            Bug ID: 26130
           Summary: Inconsistent nscd cache during pruning
           Product: glibc
           Version: 2.22
            Status: NEW
          Severity: normal
          Priority: P2
         Component: nscd
          Assignee: unassigned at sourceware dot org
          Reporter: [hidden email]
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---

During cache pruning the nscd cache is temparily inconsistent which is visible
to clients that read a shared cache.

--
You are receiving this mail because:
You are on the CC list for the bug.
Reply | Threaded
Open this post in threaded view
|

[Bug nscd/26130] Inconsistent nscd cache during pruning

Sourceware - glibc-bugs mailing list
https://sourceware.org/bugzilla/show_bug.cgi?id=26130

--- Comment #1 from Andreas Schwab <[hidden email]> ---
Created attachment 12633
  --> https://sourceware.org/bugzilla/attachment.cgi?id=12633&action=edit
getent.c

Run this in separate shells:

S1# while :; do touch /etc/group; done
S2# ./getent root
S3# ./getent wheel

--
You are receiving this mail because:
You are on the CC list for the bug.
Reply | Threaded
Open this post in threaded view
|

[Bug nscd/26130] Inconsistent nscd cache during pruning

Sourceware - glibc-bugs mailing list
In reply to this post by Sourceware - glibc-bugs mailing list
https://sourceware.org/bugzilla/show_bug.cgi?id=26130

Andreas Schwab <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |2.33
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #2 from Andreas Schwab <[hidden email]> ---
Fixed in 2.33.

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