All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis Henriques <luis.henriques@canonical.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: stable@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH -stable] netfilter: nf_tables: fix error handling of rule replacement
Date: Wed, 20 May 2015 13:12:39 +0100	[thread overview]
Message-ID: <20150520121239.GA1708@ares> (raw)
In-Reply-To: <1431802251-4781-1-git-send-email-pablo@netfilter.org>

On Sat, May 16, 2015 at 08:50:45PM +0200, Pablo Neira Ayuso wrote:
> [ upstream commit 59900e0a019e7c2bdb7809a03ed5742d311b15b3 ]
>

Thank you, Pablo.

I've took a look at these 7 patches, and most of them seem to be
applicable to the 3.16 kernel as well.  I'm queuing the following set
for the next 3.16 release:

 59900e0a019e ("netfilter: nf_tables: fix error handling of rule replacement")
 78146572b9cd ("netfilter: Zero the tuple in nfnl_cthelper_parse_tuple()")
 9889840f5988 ("netfilter: nf_tables: check for overflow of rule dlen field")
 749177ccc74f ("netfilter: nft_compat: set IP6T_F_PROTO flag if protocol is set")
 d6b6cb1d3e6f ("netfilter: nf_tables: allow to change chain policy without hook if it exists")
 16c45eda9603 ("netfilter: nft_rbtree: fix locking")

So, from your initial set, I've dropped only 4017a7ee693d ("netfilter:
restore rule tracing via nfnetlink_log").

Cheers,
--
Luís

WARNING: multiple messages have this Message-ID (diff)
From: Luis Henriques <luis.henriques@canonical.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: stable@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH -stable] netfilter: nf_tables: fix error handling of rule replacement
Date: Wed, 20 May 2015 13:12:39 +0100	[thread overview]
Message-ID: <20150520121239.GA1708@ares> (raw)
In-Reply-To: <1431802251-4781-1-git-send-email-pablo@netfilter.org>

On Sat, May 16, 2015 at 08:50:45PM +0200, Pablo Neira Ayuso wrote:
> [ upstream commit 59900e0a019e7c2bdb7809a03ed5742d311b15b3 ]
>

Thank you, Pablo.

I've took a look at these 7 patches, and most of them seem to be
applicable to the 3.16 kernel as well.  I'm queuing the following set
for the next 3.16 release:

 59900e0a019e ("netfilter: nf_tables: fix error handling of rule replacement")
 78146572b9cd ("netfilter: Zero the tuple in nfnl_cthelper_parse_tuple()")
 9889840f5988 ("netfilter: nf_tables: check for overflow of rule dlen field")
 749177ccc74f ("netfilter: nft_compat: set IP6T_F_PROTO flag if protocol is set")
 d6b6cb1d3e6f ("netfilter: nf_tables: allow to change chain policy without hook if it exists")
 16c45eda9603 ("netfilter: nft_rbtree: fix locking")

So, from your initial set, I've dropped only 4017a7ee693d ("netfilter:
restore rule tracing via nfnetlink_log").

Cheers,
--
Lu�s

  parent reply	other threads:[~2015-05-20 12:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-16 18:50 [PATCH -stable] netfilter: nf_tables: fix error handling of rule replacement Pablo Neira Ayuso
2015-05-16 18:50 ` [PATCH -stable] netfilter: Zero the tuple in nfnl_cthelper_parse_tuple() Pablo Neira Ayuso
2015-05-19 11:31   ` Jiri Slaby
2015-05-16 18:50 ` [PATCH -stable] netfilter: nf_tables: check for overflow of rule dlen field Pablo Neira Ayuso
2015-05-16 18:50 ` [PATCH -stable] netfilter: nft_compat: set IP6T_F_PROTO flag if protocol is set Pablo Neira Ayuso
2015-05-16 18:50 ` [PATCH -stable] netfilter: restore rule tracing via nfnetlink_log Pablo Neira Ayuso
2015-05-16 18:50 ` [PATCH -stable] netfilter: nf_tables: allow to change chain policy without hook if it exists Pablo Neira Ayuso
2015-05-16 18:50 ` [PATCH -stable] netfilter: nft_rbtree: fix locking Pablo Neira Ayuso
2015-06-29 23:00   ` Greg KH
2015-07-01 11:38     ` Pablo Neira Ayuso
2015-05-20 12:12 ` Luis Henriques [this message]
2015-05-20 12:12   ` [PATCH -stable] netfilter: nf_tables: fix error handling of rule replacement Luis Henriques

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=20150520121239.GA1708@ares \
    --to=luis.henriques@canonical.com \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=stable@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.