public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nscd/26130] Inconsistent nscd cache during pruning
Date: Mon, 28 Aug 2023 06:42:41 +0000	[thread overview]
Message-ID: <bug-26130-131-sMgjqOWvrW@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26130-131@http.sourceware.org/bugzilla/>

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

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fweimer at redhat dot com

--- Comment #3 from Florian Weimer <fweimer at redhat dot com> ---
commit 5e74e6f85842892bc25da8e8c70d8dadd485941a
Author: Andreas Schwab <schwab@suse.de>
Date:   Wed Jun 17 16:05:13 2020 +0200

    nscd: bump GC cycle during cache pruning (bug 26130)

    While nscd prunes a cache it becomes inconsistent temporarily, which is
    visible to clients if that cache is shared.  Bump the GC cycle counter so
    that the clients notice the modification window.

    Uniformly use atomic_fetch_add to modify the GC cycle counter.

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

      parent reply	other threads:[~2023-08-28  6:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-17 14:01 [Bug nscd/26130] New: " schwab@linux-m68k.org
2020-06-22  8:56 ` [Bug nscd/26130] " schwab@linux-m68k.org
2020-09-17 16:01 ` schwab@linux-m68k.org
2023-08-28  6:42 ` fweimer at redhat dot com [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-26130-131-sMgjqOWvrW@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).