about summary refs log tree commit diff
path: root/nscd/cache.c
diff options
context:
space:
mode:
authorAndreas Schwab <schwab@suse.de>2020-06-17 16:05:13 +0200
committerAndreas Schwab <schwab@suse.de>2020-09-17 17:59:11 +0200
commit5e74e6f85842892bc25da8e8c70d8dadd485941a (patch)
treeecccee562fbf549b47bdecfc07aa3fa41b065b2b /nscd/cache.c
parent94cd37ebb293321115a36a422b091fdb72d2fb08 (diff)
downloadglibc-5e74e6f85842892bc25da8e8c70d8dadd485941a.tar.gz
glibc-5e74e6f85842892bc25da8e8c70d8dadd485941a.tar.xz
glibc-5e74e6f85842892bc25da8e8c70d8dadd485941a.zip
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.
Diffstat (limited to 'nscd/cache.c')
-rw-r--r--nscd/cache.c9
1 files changed, 9 insertions, 0 deletions
diff --git a/nscd/cache.c b/nscd/cache.c
index 0c4dfc0dcf..38ddd6d7ec 100644
--- a/nscd/cache.c
+++ b/nscd/cache.c
@@ -452,6 +452,11 @@ prune_cache (struct database_dyn *table, time_t now, int fd)
 	  pthread_rwlock_wrlock (&table->lock);
 	}
 
+      /* Now we start modifying the data.  Make sure all readers of the
+	 data are aware of this and temporarily don't use the data.  */
+      atomic_fetch_add_relaxed (&table->head->gc_cycle, 1);
+      assert ((table->head->gc_cycle & 1) == 1);
+
       while (first <= last)
 	{
 	  if (mark[first])
@@ -492,6 +497,10 @@ prune_cache (struct database_dyn *table, time_t now, int fd)
 	  ++first;
 	}
 
+      /* Now we are done modifying the data.  */
+      atomic_fetch_add_relaxed (&table->head->gc_cycle, 1);
+      assert ((table->head->gc_cycle & 1) == 0);
+
       /* It's all done.  */
       pthread_rwlock_unlock (&table->lock);