[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131008072114.GA4455@gmail.com>
Date: Tue, 8 Oct 2013 09:21:14 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Christoph Lameter <cl@...ux.com>
Cc: Tejun Heo <tj@...nel.org>, akpm@...uxfoundation.org,
Eric Dumazet <edumazet@...gle.com>, netdev@...r.kernel.org,
Steven Rostedt <srostedt@...hat.com>,
linux-kernel@...r.kernel.org,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [raw v1 2/4] [NET] Use raw_cpu ops for SNMP stats
* Christoph Lameter <cl@...ux.com> wrote:
> SNMP stats are not protected by preemption but by bh handling.
Most forms of bh exclusion work via the preemption count though, and
softirq contexts themselves are generally not preemptible [to other CPUs]
either.
So the warnings should, in most cases, not trigger.
> Since protection is provided outside of preemption raw_cpu_ops
> need to be used to avoid false positives.
Could you quote the warning that pops up? It might be better to annotate
the specific safe usages than to potentially hide bugs:
> --- linux.orig/include/net/snmp.h 2013-10-07 09:16:07.595206864 -0500
> +++ linux/include/net/snmp.h 2013-10-07 09:16:07.591206909 -0500
> @@ -126,7 +126,7 @@ struct linux_xfrm_mib {
> extern __typeof__(type) __percpu *name[SNMP_ARRAY_SZ]
>
> #define SNMP_INC_STATS_BH(mib, field) \
> - __this_cpu_inc(mib[0]->mibs[field])
> + raw_cpu_inc(mib[0]->mibs[field])
>
> #define SNMP_INC_STATS_USER(mib, field) \
> this_cpu_inc(mib[0]->mibs[field])
> @@ -141,7 +141,7 @@ struct linux_xfrm_mib {
> this_cpu_dec(mib[0]->mibs[field])
>
> #define SNMP_ADD_STATS_BH(mib, field, addend) \
> - __this_cpu_add(mib[0]->mibs[field], addend)
> + raw_cpu_add(mib[0]->mibs[field], addend)
>
> #define SNMP_ADD_STATS_USER(mib, field, addend) \
> this_cpu_add(mib[0]->mibs[field], addend)
Doing this will hide any true bugs if any of these primitives is used in
an unsafe context.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists