linux-kernel - [PATCH] percpu_counter: Fix __percpu_counter

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4936EB04.8000609@cosmosbay.com>
Date:	Wed, 03 Dec 2008 21:24:36 +0100
From:	Eric Dumazet <dada1@...mosbay.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
CC:	linux kernel <linux-kernel@...r.kernel.org>,
	"David S. Miller" <davem@...emloft.net>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: [PATCH] percpu_counter: Fix __percpu_counter_sum()

Eric Dumazet a écrit :
> Hi Andrew
> 
> While working on percpu_counter on net-next-2.6, I found
> a CPU unplug race in percpu_counter_destroy()
> 
> (Very unlikely of course)
> 
> Thank you
> 
> [PATCH] percpu_counter: fix CPU unplug race in percpu_counter_destroy()
> 
> We should first delete the counter from percpu_counters list
> before freeing memory, or a percpu_counter_hotcpu_callback()
> could dereference a NULL pointer.
> 
> Signed-off-by: Eric Dumazet <dada1@...mosbay.com>
> ---
> lib/percpu_counter.c |    4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
> 

Well, this percpu_counter stuff is simply not working at all.

We added some percpu_counters to network tree for 2.6.29 and we get
drift bugs if calling __percpu_counter_sum() while some heavy duty
benches are running, on a 8 cpus machine

1) __percpu_counter_sum() is buggy, it should not write
on per_cpu_ptr(fbc->counters, cpu), or another cpu
could get its changes lost.

__percpu_counter_sum should be read only (const struct percpu_counter *fbc),
and no locking needed.

2) Un-needed lock in percpu_counter_set()
   This wont block another cpu doing an _add anyway.
   Not a bug, but disturbing, giving false feeling of protection.
   percpu_counter are not precise, we cannot reliably set them
   or read them. Period.
   In fact percpu_counter_set() callers should use
   percpu_counter_add(). (only used from lib/proportions.c )

Thank you

[PATCH] percpu_counter: Fix __percpu_counter_sum()

This function should not write into percpu local storage,
without proper locking, or some changes done on other cpus
might be lost.

Adding proper locking would need to use atomic
operations in fast path and would be expensive.

Results of __percpu_counter_sum() can be wrong, this is a
known fact.

We also dont need to acquire the lock, this gives
no better results.

Signed-off-by: Eric Dumazet <dada1@...mosbay.com>
---
 lib/percpu_counter.c |    5 -----
 1 files changed, 5 deletions(-)

View attachment "__percpu_counter_sum.patch" of type "text/plain" (506 bytes)