From: Xin Long <lucien.xin@gmail.com>
To: network dev <netdev@vger.kernel.org>,
netfilter-devel@vger.kernel.org, linux-sctp@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
Florian Westphal <fw@strlen.de>,
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
Simon Horman <horms@kernel.org>
Subject: [PATCHv2 nf 0/2] netfilter: handle the sctp collision properly and add selftest
Date: Tue, 3 Oct 2023 13:17:52 -0400 [thread overview]
Message-ID: <cover.1696353375.git.lucien.xin@gmail.com> (raw)
Patch 1/2 is to fix the insufficient processing for sctp collision in netfilter
nf_conntrack, and Patch 2/2 is to add a selftest for it, as Florian suggested.
Xin Long (2):
netfilter: handle the connecting collision properly in
nf_conntrack_proto_sctp
selftests: netfilter: test for sctp collision processing in
nf_conntrack
include/linux/netfilter/nf_conntrack_sctp.h | 1 +
net/netfilter/nf_conntrack_proto_sctp.c | 43 ++++++--
tools/testing/selftests/netfilter/Makefile | 5 +-
.../netfilter/conntrack_sctp_collision.sh | 89 +++++++++++++++++
.../selftests/netfilter/sctp_collision.c | 99 +++++++++++++++++++
5 files changed, 225 insertions(+), 12 deletions(-)
create mode 100755 tools/testing/selftests/netfilter/conntrack_sctp_collision.sh
create mode 100644 tools/testing/selftests/netfilter/sctp_collision.c
--
2.39.1
next reply other threads:[~2023-10-03 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 17:17 Xin Long [this message]
2023-10-03 17:17 ` [PATCHv2 nf 1/2] netfilter: handle the connecting collision properly in nf_conntrack_proto_sctp Xin Long
2023-10-03 17:17 ` [PATCHv2 nf 2/2] selftests: netfilter: test for sctp collision processing in nf_conntrack Xin Long
2023-10-07 14:47 ` [PATCHv2 nf 0/2] netfilter: handle the sctp collision properly and add selftest Simon Horman
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=cover.1696353375.git.lucien.xin@gmail.com \
--to=lucien.xin@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=horms@kernel.org \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.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.