From: Greg KH <gregkh@linuxfoundation.org>
To: Florian Westphal <fw@strlen.de>
Cc: stable@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 4.14.y 0/2] netfilter: nat: fix soft lockup when most ports are used
Date: Thu, 3 Feb 2022 18:44:12 +0100 [thread overview]
Message-ID: <YfwUbNbE5ILR+a0w@kroah.com> (raw)
In-Reply-To: <20220203124155.16693-1-fw@strlen.de>
On Thu, Feb 03, 2022 at 01:41:53PM +0100, Florian Westphal wrote:
> First patch removes old rovers, they are inherently racy
> and cause packet drops/delays.
>
> Second patch avoids iterating entire range of ports: It takes way
> too long when most tuples are in use.
>
> First patch is slightly mangled; nf_nat_proto_common.c needs minor adjustment
> in context.
Both sets of backports now queued up, thanks.
greg k-h
prev parent reply other threads:[~2022-02-03 17:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 12:41 [PATCH 4.14.y 0/2] netfilter: nat: fix soft lockup when most ports are used Florian Westphal
2022-02-03 12:41 ` [PATCH 4.14.y 1/2] netfilter: nat: remove l4 protocol port rovers Florian Westphal
2022-02-03 12:41 ` [PATCH 4.14.y 2/2] netfilter: nat: limit port clash resolution attempts Florian Westphal
2022-02-03 17:44 ` Greg KH [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=YfwUbNbE5ILR+a0w@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.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 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).