From: Eyal Birger <eyal.birger@gmail.com>
To: steffen.klassert@secunet.com, herbert@gondor.apana.org.au,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
dsahern@kernel.org, pabeni@redhat.com
Cc: netdev@vger.kernel.org, devel@linux-ipsec.org,
Eyal Birger <eyal.birger@gmail.com>
Subject: [PATCH ipsec,v2 0/2] xfrm: respect ip proto rules criteria in xfrm dst lookups
Date: Mon, 2 Sep 2024 04:07:17 -0700 [thread overview]
Message-ID: <20240902110719.502566-1-eyal.birger@gmail.com> (raw)
This series fixes the route lookup when done for xfrm to regard
L4 criteria specified in ip rules.
The first patch is a minor refactor to allow passing more parameters
to dst lookup functions.
The second patch actually passes L4 information to these lookup functions.
Signed-off-by: Eyal Birger <eyal.birger@gmail.com>
---
v2: fix first patch based on reviews from Steffen Klassert and
Simon Horman
Eyal Birger (2):
xfrm: extract dst lookup parameters into a struct
xfrm: respect ip protocols rules criteria when performing dst lookups
include/net/xfrm.h | 28 ++++++++++++-----------
net/ipv4/xfrm4_policy.c | 40 +++++++++++++++------------------
net/ipv6/xfrm6_policy.c | 31 +++++++++++++-------------
net/xfrm/xfrm_device.c | 11 ++++++---
net/xfrm/xfrm_policy.c | 49 +++++++++++++++++++++++++++++++----------
5 files changed, 94 insertions(+), 65 deletions(-)
--
2.34.1
next reply other threads:[~2024-09-02 11:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 11:07 Eyal Birger [this message]
2024-09-02 11:07 ` [PATCH ipsec,v2 1/2] xfrm: extract dst lookup parameters into a struct Eyal Birger
2024-09-02 11:07 ` [PATCH ipsec,v2 2/2] xfrm: respect ip protocols rules criteria when performing dst lookups Eyal Birger
2024-09-02 13:52 ` [devel-ipsec] [PATCH ipsec, v2 0/2] xfrm: respect ip proto rules criteria in xfrm " Antony Antony
2024-09-02 20:39 ` Antony Antony
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=20240902110719.502566-1-eyal.birger@gmail.com \
--to=eyal.birger@gmail.com \
--cc=davem@davemloft.net \
--cc=devel@linux-ipsec.org \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=steffen.klassert@secunet.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.