All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@vger.kernel.org, fw@strlen.de, eric.dumazet@gmail.com
Subject: Re: [PATCH nf-next,v2] netfilter: nft_counter: convert it to use per-cpu counters
Date: Fri, 19 Jun 2015 11:59:17 +0200	[thread overview]
Message-ID: <20150619095917.GA7177@salvia> (raw)
In-Reply-To: <20150619095012.GE22946@acer.localdomain>

On Fri, Jun 19, 2015 at 11:50:12AM +0200, Patrick McHardy wrote:
> On 19.06, Pablo Neira Ayuso wrote:
> > On Fri, Jun 19, 2015 at 11:39:37AM +0200, Patrick McHardy wrote:
> > > > +	struct nft_counter_percpu_priv *priv = nft_expr_priv(expr);
> > > > +	struct nft_counter_percpu __percpu *cpu_stats;
> > > > +	struct nft_counter_percpu *this_cpu;
> > > > +
> > > > +	cpu_stats = netdev_alloc_pcpu_stats(struct nft_counter_percpu);
> > > > +	if (cpu_stats == NULL)
> > > > +		return ENOMEM;
> > > > +
> > > > +	preempt_disable();
> > > 
> > > Seems unnecessary, the stats are not active durign ->init().
> > 
> > I know, I need to find a better way to silent a lockdep preempt splat
> > that I'm getting here because of illegal use of this_cpu_ptr() with
> > preemption enabled.
> 
> Ok guess it doesn't really hurt.

I'm going to leave it in place, OK?

  reply	other threads:[~2015-06-19  9:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-19  9:36 [PATCH nf-next,v2] netfilter: nft_counter: convert it to use per-cpu counters Pablo Neira Ayuso
2015-06-19  9:39 ` Patrick McHardy
2015-06-19  9:49   ` Pablo Neira Ayuso
2015-06-19  9:50     ` Patrick McHardy
2015-06-19  9:59       ` Pablo Neira Ayuso [this message]
2015-06-19 10:00         ` Patrick McHardy
2015-06-19 13:43     ` Marcelo Ricardo Leitner

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=20150619095917.GA7177@salvia \
    --to=pablo@netfilter.org \
    --cc=eric.dumazet@gmail.com \
    --cc=fw@strlen.de \
    --cc=kaber@trash.net \
    --cc=netfilter-devel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.