From: Eric Dumazet <eric.dumazet@gmail.com>
To: Shaohua Li <shaohua.li@intel.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
cl@linux.com, tj@kernel.org
Subject: Re: [PATCH 3/4]percpu_counter: fix code for 32bit systems
Date: Tue, 12 Apr 2011 11:03:55 +0200 [thread overview]
Message-ID: <1302599035.3233.27.camel@edumazet-laptop> (raw)
In-Reply-To: <1302595444.3981.129.camel@sli10-conroe>
Le mardi 12 avril 2011 à 16:04 +0800, Shaohua Li a écrit :
> percpu_counter.counter is a 's64'. Accessing it in 32-bit system is racing.
> we need some locking to protect it otherwise some very wrong value could be
> accessed.
>
> Signed-off-by: Shaohua Li <shaohua.li@intel.com>
> ---
> include/linux/percpu_counter.h | 43 +++++++++++++++++++++++++++++++----------
> 1 file changed, 33 insertions(+), 10 deletions(-)
>
> Index: linux/include/linux/percpu_counter.h
> ===================================================================
> --- linux.orig/include/linux/percpu_counter.h 2011-04-12 15:48:44.000000000 +0800
> +++ linux/include/linux/percpu_counter.h 2011-04-12 15:48:54.000000000 +0800
> @@ -54,7 +54,15 @@ static inline s64 percpu_counter_sum(str
>
> static inline s64 percpu_counter_read(struct percpu_counter *fbc)
> {
> +#if BITS_PER_LONG == 32
> + s64 count;
> + spin_lock(&fbc->lock);
> + count = fbc->count;
> + spin_unlock(&fbc->lock);
> + return count;
> +#else
> return fbc->count;
> +#endif
> }
>
Hmm... did you test this with LOCKDEP on ?
You add a possible deadlock here.
Hint : Some percpu_counter are used from irq context.
This interface assumes caller take the appropriate locking.
next prev parent reply other threads:[~2011-04-12 9:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 8:04 Shaohua Li
2011-04-12 9:03 ` Eric Dumazet [this message]
2011-04-13 1:01 ` Shaohua Li
2011-04-13 2:32 ` Eric Dumazet
2011-04-13 2:41 ` Shaohua Li
2011-04-13 2:47 ` Eric Dumazet
2011-04-13 3:03 ` Shaohua Li
2011-04-13 3:50 ` tj
2011-04-13 4:37 ` Shaohua Li
2011-04-13 3:53 ` Eric Dumazet
2011-04-13 4:00 ` tj
2011-04-12 19:02 ` Tejun Heo
2011-04-13 1:05 ` Shaohua Li
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=1302599035.3233.27.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--cc=tj@kernel.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
all inboxes | Powered by JetHome®