From: Florian Westphal <fw@strlen.de>
To: <netfilter-devel@vger.kernel.org>
Cc: marcmicalizzi@gmail.com
Subject: [PATCH nf 0/5] netfilter: flow table fixes
Date: Tue, 21 May 2019 13:24:29 +0200 [thread overview]
Message-ID: <20190521112434.11767-1-fw@strlen.de> (raw)
This series fixes several issues I spotted while investigating
a 'tcp connection stalls with flow offload on' bug report.
I'm not sure if the original problem is fixed, however, the test script
in patch 5 will fail without the fixes from patches 1 and 2.
Patches 3 and 4 fix additional problems, however, these are by code
review only.
Florian Westphal (5):
netfilter: nf_flow_table: ignore DF bit setting
netfilter: nft_flow_offload: set liberal tracking mode for tcp
netfilter: nft_flow_offload: don't offload when sequence numbers need adjustment
netfilter: nft_flow_offload: IPCB is only valid for ipv4 family
selftests: netfilter: add flowtable test script
net/netfilter/nf_flow_table_ip.c | 3
net/netfilter/nft_flow_offload.c | 31 +-
tools/testing/selftests/netfilter/Makefile | 2
tools/testing/selftests/netfilter/nft_flowtable.sh | 324 +++++++++++++++++++++
next reply other threads:[~2019-05-21 11:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 11:24 Florian Westphal [this message]
2019-05-21 11:24 ` [PATCH nf 1/5] netfilter: nf_flow_table: ignore DF bit setting Florian Westphal
2019-05-21 11:24 ` [PATCH nf 2/5] netfilter: nft_flow_offload: set liberal tracking mode for tcp Florian Westphal
2019-05-21 11:24 ` [PATCH nf 3/5] netfilter: nft_flow_offload: don't offload when sequence numbers need adjustment Florian Westphal
2019-05-21 11:24 ` [PATCH nf 4/5] netfilter: nft_flow_offload: IPCB is only valid for ipv4 family Florian Westphal
2019-05-21 11:24 ` [PATCH nf 5/5] selftests: netfilter: add flowtable test script Florian Westphal
2019-05-22 8:55 ` [PATCH nf 0/5] netfilter: flow table fixes Pablo Neira Ayuso
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=20190521112434.11767-1-fw@strlen.de \
--to=fw@strlen.de \
--cc=marcmicalizzi@gmail.com \
--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).