From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] netfilter: nf_tables: fix oops when deleting a chain with references
Date: Wed, 29 Jan 2014 20:22:54 +0100 [thread overview]
Message-ID: <20140129192254.GB11531@localhost> (raw)
In-Reply-To: <20140125080407.GA15949@macbook.localnet>
On Sat, Jan 25, 2014 at 08:04:07AM +0000, Patrick McHardy wrote:
> commit 780f57420cdac84eabec388868678ede19f7d682
> Author: Patrick McHardy <kaber@trash.net>
> Date: Fri Jan 24 13:23:52 2014 +0000
>
> netfilter: nf_tables: fix oops when deleting a chain with references
>
> THe following commands trigger an oops:
>
> # nft -i
> nft> add table filter
> nft> add chain filter input { type filter hook input priority 0; }
> nft> add chain filter test
> nft> add rule filter input jump test
> nft> delete chain filter test
>
> We need to check the chain use counter before allowing destruction since
> we might have references from sets or jump rules.
Applied, thanks Patrick.
prev parent reply other threads:[~2014-01-29 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-25 8:04 [PATCH] netfilter: nf_tables: fix oops when deleting a chain with references Patrick McHardy
2014-01-29 19:22 ` Pablo Neira Ayuso [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=20140129192254.GB11531@localhost \
--to=pablo@netfilter.org \
--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 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).