From: Leon Romanovsky <leon@kernel.org>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH xfrm-next v7 4/8] xfrm: add TX datapath support for IPsec packet offload mode
Date: Mon, 21 Nov 2022 13:10:15 +0200 [thread overview]
Message-ID: <Y3tcl3H/d9tkj/v8@unreal> (raw)
In-Reply-To: <20221118102310.GQ704954@gauss3.secunet.de>
On Fri, Nov 18, 2022 at 11:23:10AM +0100, Steffen Klassert wrote:
> On Thu, Nov 17, 2022 at 02:32:10PM +0200, Leon Romanovsky wrote:
> > On Thu, Nov 17, 2022 at 12:59:39PM +0100, Steffen Klassert wrote:
> > > On Wed, Nov 09, 2022 at 02:54:32PM +0200, Leon Romanovsky wrote:
> > > > From: Leon Romanovsky <leonro@nvidia.com>
> > >
> > > > @@ -2708,6 +2710,23 @@ static struct dst_entry *xfrm_bundle_create(struct xfrm_policy *policy,
> > > > if (!dev)
> > > > goto free_dst;
> > > >
> > > > + dst1 = &xdst0->u.dst;
> > > > + /* Packet offload: both policy and SA should be offloaded */
> > > > + if ((policy->xdo.type == XFRM_DEV_OFFLOAD_PACKET &&
> > > > + dst1->xfrm->xso.type != XFRM_DEV_OFFLOAD_PACKET) ||
> > > > + (policy->xdo.type != XFRM_DEV_OFFLOAD_PACKET &&
> > > > + dst1->xfrm->xso.type == XFRM_DEV_OFFLOAD_PACKET)) {
> > > > + err = -EINVAL;
> > > > + goto free_dst;
> > > > + }
> > > > +
> > > > + /* Packet offload: both policy and SA should have same device */
> > > > + if (policy->xdo.type == XFRM_DEV_OFFLOAD_PACKET &&
> > > > + policy->xdo.dev != dst1->xfrm->xso.dev) {
> > > > + err = -EINVAL;
> > > > + goto free_dst;
> > > > + }
> > > > +
> > >
> > > This is the wrong place for these checks. Things went already wrong
> > > in the lookup if policy and state do not match here.
> >
> > Where do you think we should put such checks?
>
> You need to create a new lookup key for this and match the policies
> template against the TS of the state. This happens in xfrm_state_find.
> Unfortunately this affects also the SW datapath even without HW
> policies/states. So please try to make it a NOP if there are no HW
> policies/states.
Do you think that this will be enough?
+static bool xfrm_state_and_policy_mixed(struct xfrm_state *x,
+ struct xfrm_policy *p)
+{
+ /* Packet offload: both policy and SA should be offloaded */
+ if (p->xdo.type == XFRM_DEV_OFFLOAD_PACKET &&
+ x->xso.type != XFRM_DEV_OFFLOAD_PACKET)
+ return true;
+
+ if (p->xdo.type != XFRM_DEV_OFFLOAD_PACKET &&
+ x->xso.type == XFRM_DEV_OFFLOAD_PACKET)
+ return true;
+
+ if (p->xdo.type != XFRM_DEV_OFFLOAD_PACKET)
+ return false;
+
+ /* Packet offload: both policy and SA should have same device */
+ if (p->xdo.dev != x->xso.dev)
+ return true;
+
+ return false;
+}
+
struct xfrm_state *
xfrm_state_find(const xfrm_address_t *daddr, const xfrm_address_t *saddr,
const struct flowi *fl, struct xfrm_tmpl *tmpl,
@@ -1228,6 +1250,10 @@ xfrm_state_find(const xfrm_address_t *daddr, const xfrm_address_t *saddr,
*err = -EAGAIN;
x = NULL;
}
+ if (x && xfrm_state_and_policy_mixed(x, pol)) {
+ *err = -EINVAL;
+ x = NULL;
+ }
} else {
*err = acquire_in_progress ? -EAGAIN : error;
}
(END)
>
next prev parent reply other threads:[~2022-11-21 11:15 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 12:54 [PATCH xfrm-next v7 0/8] Extend XFRM core to allow packet offload configuration Leon Romanovsky
2022-11-09 12:54 ` [PATCH xfrm-next v7 1/8] xfrm: add new packet offload flag Leon Romanovsky
2022-11-09 12:54 ` [PATCH xfrm-next v7 2/8] xfrm: allow state packet offload mode Leon Romanovsky
2022-11-09 12:54 ` [PATCH xfrm-next v7 3/8] xfrm: add an interface to offload policy Leon Romanovsky
2022-11-09 12:54 ` [PATCH xfrm-next v7 4/8] xfrm: add TX datapath support for IPsec packet offload mode Leon Romanovsky
2022-11-17 11:59 ` Steffen Klassert
2022-11-17 12:32 ` Leon Romanovsky
2022-11-18 10:23 ` Steffen Klassert
2022-11-21 11:10 ` Leon Romanovsky [this message]
2022-11-09 12:54 ` [PATCH xfrm-next v7 5/8] xfrm: add RX datapath protection " Leon Romanovsky
2022-11-09 12:54 ` [PATCH xfrm-next v7 6/8] xfrm: speed-up lookup of HW policies Leon Romanovsky
2022-11-17 12:12 ` Steffen Klassert
2022-11-17 12:51 ` Leon Romanovsky
2022-11-18 10:49 ` Steffen Klassert
2022-11-20 19:17 ` Leon Romanovsky
2022-11-21 9:44 ` Steffen Klassert
2022-11-21 10:27 ` Leon Romanovsky
2022-11-21 11:09 ` Steffen Klassert
2022-11-21 11:15 ` Leon Romanovsky
2022-11-21 11:25 ` Steffen Klassert
2022-11-21 11:34 ` Leon Romanovsky
2022-11-21 12:02 ` Leon Romanovsky
2022-11-21 12:43 ` Steffen Klassert
2022-11-21 13:01 ` Leon Romanovsky
2022-11-22 13:10 ` Steffen Klassert
2022-11-22 13:57 ` Leon Romanovsky
2022-11-23 8:37 ` Steffen Klassert
2022-11-23 9:36 ` Leon Romanovsky
2022-11-23 12:53 ` Leon Romanovsky
2022-11-24 11:07 ` Steffen Klassert
2022-11-25 6:23 ` Leon Romanovsky
2022-11-21 12:10 ` Steffen Klassert
2022-11-21 13:21 ` Leon Romanovsky
2022-11-22 4:29 ` Herbert Xu
2022-11-22 6:27 ` Leon Romanovsky
2022-11-22 13:00 ` Steffen Klassert
2022-11-22 13:54 ` Leon Romanovsky
2022-11-23 8:23 ` Steffen Klassert
2022-11-23 10:25 ` Leon Romanovsky
2022-11-09 12:54 ` [PATCH xfrm-next v7 7/8] xfrm: add support to HW update soft and hard limits Leon Romanovsky
2022-11-17 12:13 ` Steffen Klassert
2022-11-17 12:32 ` Leon Romanovsky
2022-11-09 12:54 ` [PATCH xfrm-next v7 8/8] xfrm: document IPsec packet offload mode Leon Romanovsky
2022-11-17 12:15 ` Steffen Klassert
2022-11-17 12:33 ` Leon Romanovsky
2022-11-15 18:09 ` [PATCH xfrm-next v7 0/8] Extend XFRM core to allow packet offload configuration Leon Romanovsky
2022-11-15 18:30 ` Steffen Klassert
2022-11-15 19:00 ` Leon Romanovsky
2022-11-16 23:07 ` Saeed Mahameed
2022-11-17 12:20 ` Steffen Klassert
2022-11-17 12:24 ` Leon Romanovsky
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=Y3tcl3H/d9tkj/v8@unreal \
--to=leon@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--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 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).