All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Vimal Agrawal <avimalin@gmail.com>
Cc: netfilter-devel@vger.kernel.org, pablo@netfilter.org,
	fw@strlen.dea, vimal.agrawal@sophos.com
Subject: Re: [PATCH] netfilter: nat: limit port clash resolution attempts
Date: Thu, 3 Feb 2022 13:43:55 +0100	[thread overview]
Message-ID: <20220203124355.GA19591@breakpoint.cc> (raw)
In-Reply-To: <20220203051329.118778-1-vimal.agrawal@sophos.com>

Vimal Agrawal <avimalin@gmail.com> wrote:
> commit a504b703bb1da526a01593da0e4be2af9d9f5fa8 ("netfilter: nat:
> limit port clash resolution attempts")

I've forwarded this to stable@ for inclusion into 4.14.y.

I've also sent a request for 4.19.y (applies with no changes) and
a backported version for 4.9.y.

4.4.y is EOL, so no action done in that department.

      parent reply	other threads:[~2022-02-03 12:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03  5:13 [PATCH] netfilter: nat: limit port clash resolution attempts Vimal Agrawal
2022-02-03  6:10 ` Vimal Agrawal
2022-02-03 12:43 ` Florian Westphal [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=20220203124355.GA19591@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=avimalin@gmail.com \
    --cc=fw@strlen.dea \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=vimal.agrawal@sophos.com \
    /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.