netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Eric Leblond <eric@regit.org>
Cc: Netfilter Devel <netfilter-devel@vger.kernel.org>, brouer@redhat.com
Subject: Re: [PATCH] netfilter: synproxy: fix conntrackd interaction
Date: Mon, 15 May 2017 19:55:49 +0200	[thread overview]
Message-ID: <20170515175549.GA6393@salvia> (raw)
In-Reply-To: <fbaa0cbd-a13d-46e3-a796-023439433dda@email.android.com>

On Mon, May 15, 2017 at 07:49:18PM +0200, Eric Leblond wrote:
>    Hello,
>    Le 15 mai 2017 6:52 PM, Pablo Neira Ayuso <pablo@netfilter.org> a
>    écrit :
> 
>      On Thu, May 11, 2017 at 06:56:38PM +0200, Eric Leblond wrote:
>      > This patch fixes the creation of connection tracking entry from
>      > netlink when synproxy is used. It was missing the addition of
>      > the synproxy extension.
>      >
>      > This was causing kernel crashes when a conntrack entry created by
>      > conntrackd was used after the switch of traffic from active node
>      > to the passive node.
>      Applied, thanks Eric.
> 
>    Thanks Pablo !
>    Will you push it to stable as it is causing a crash on older kernel
>    like 3.16?

Does this compile cleanly as is?

If so, I can just request -stable maintainer to take it as soon as
this hits upstream.

  parent reply	other threads:[~2017-05-15 17:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-11 13:22 [PATCH] netfilter: synproxy: fix conntrackd interaction Eric Leblond
2017-05-11 16:14 ` Jesper Dangaard Brouer
2017-05-11 16:56   ` Eric Leblond
2017-05-15 16:52     ` Pablo Neira Ayuso
     [not found]       ` <fbaa0cbd-a13d-46e3-a796-023439433dda@email.android.com>
2017-05-15 17:55         ` Pablo Neira Ayuso [this message]
2017-05-15 21:53           ` Eric Leblond

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=20170515175549.GA6393@salvia \
    --to=pablo@netfilter.org \
    --cc=brouer@redhat.com \
    --cc=eric@regit.org \
    --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).