From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] netfilter: nf_tables: fix oops when using gotos
Date: Fri, 7 Feb 2014 16:30:41 +0000 [thread overview]
Message-ID: <20140207163041.GA24391@macbook.localnet> (raw)
In-Reply-To: <20140207162658.GA5258@localhost>
On Fri, Feb 07, 2014 at 05:26:58PM +0100, Pablo Neira Ayuso wrote:
> On Fri, Feb 07, 2014 at 05:23:30PM +0100, Pablo Neira Ayuso wrote:
> > On Fri, Feb 07, 2014 at 05:18:51PM +0100, Pablo Neira Ayuso wrote:
> > > Fix an oops if you use the "goto" operation, you will end up in
> > > non-base chain with no counters and no default policy. While at
> > > it, uninlined nft_chain_stats() since it doesn't make sense to
> > > optimize a debugging facility that is rarely used.
> > >
> > > Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
> > > ---
> > > I noticed this when testing the compat layer.
> > >
> > > @Patrick: When working on this I noticed I accidentally has skipped
> > > this patch: http://www.spinics.net/lists/netfilter-devel/msg29828.html
> > > I have included this change in this fix. Sorry for that.
> >
> > Oops, unlined the wrong function...
>
> I'm going to push this leftover fix to nf:
>
> http://patchwork.ozlabs.org/patch/308930/
>
> Will resend a v2 to fix the goto issue.
Thanks! I was also considering moving this to jump labels and enable
the label on nft meta set trace. Not sure if its worth it though,
will do some benchmarking at some point ...
prev parent reply other threads:[~2014-02-07 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 16:18 [PATCH] netfilter: nf_tables: fix oops when using gotos Pablo Neira Ayuso
2014-02-07 16:23 ` Pablo Neira Ayuso
2014-02-07 16:26 ` Pablo Neira Ayuso
2014-02-07 16:30 ` Patrick McHardy [this message]
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=20140207163041.GA24391@macbook.localnet \
--to=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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;
as well as URLs for NNTP newsgroup(s).