netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Bharat Bhushan <bbhushan2@marvell.com>
Cc: Steffen Klassert <steffen.klassert@secunet.com>,
	"herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Setting security path with IPsec packet offload mode
Date: Thu, 22 Jun 2023 11:35:00 +0300	[thread overview]
Message-ID: <20230622083500.GA234767@unreal> (raw)
In-Reply-To: <DM5PR1801MB18831A63ED0689236ED2506FE322A@DM5PR1801MB1883.namprd18.prod.outlook.com>

On Thu, Jun 22, 2023 at 06:58:06AM +0000, Bharat Bhushan wrote:
> Hi All,
> 
> Have a query related to security patch (secpath_set()) with packet offload mode on egress side. Working to enable ipsec packet offload while Crypto offload is working.
> For packet offload xfrm_offload(*skb) returns false in driver. While looking in xfrm framework, cannot find where security patch (secpath_set()) is set with packet offload mode on egress side.

The idea of packet offload is to take plain text packets and perform all needed magic
in HW without need from driver and stack to make anything.

We don't set secpath in TX path as such packets exit from XFRM as "plain" ones toward HW.
It is different in RX, we set there, as XFRM core still needs to perform some code on
the arrived packets, before forwarding them to stack.

Thanks

> 
> For sure I might be missing something here and looking for help to understand same. Meantime just tried below hack:
> 
> diff --git a/net/xfrm/xfrm_output.c b/net/xfrm/xfrm_output.c
> index ff114d68cc43..8499c0e74a5a 100644
> --- a/net/xfrm/xfrm_output.c
> +++ b/net/xfrm/xfrm_output.c
> @@ -718,12 +718,24 @@ int xfrm_output(struct sock *sk, struct sk_buff *skb)
>         }
>  
>         if (x->xso.type == XFRM_DEV_OFFLOAD_PACKET) {
> +               struct sec_path *sp;
>                 if (!xfrm_dev_offload_ok(skb, x)) {
>                         XFRM_INC_STATS(net, LINUX_MIB_XFRMOUTERROR);
>                         kfree_skb(skb);
>                         return -EHOSTUNREACH;
>                 }
>  
> +               sp = secpath_set(skb);
> +               if (!sp) {
> +                       XFRM_INC_STATS(net, LINUX_MIB_XFRMOUTERROR);
> +                       kfree_skb(skb);
> +                       return -ENOMEM;
> +               }
> +
> +               sp->olen++;
> +               sp->xvec[sp->len++] = x;
> +               xfrm_state_hold(x);
> +
>                 return xfrm_output_resume(sk, skb, 0);
>         }
>  
> 
> Thanks in advance,
> -Bharat
> 

  reply	other threads:[~2023-06-22  8:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-22  6:58 Setting security path with IPsec packet offload mode Bharat Bhushan
2023-06-22  8:35 ` Leon Romanovsky [this message]
2023-06-23  6:48   ` [EXT] " Bharat Bhushan
2023-06-23  7:01     ` Bharat Bhushan
2023-06-25  7:27     ` 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=20230622083500.GA234767@unreal \
    --to=leon@kernel.org \
    --cc=bbhushan2@marvell.com \
    --cc=davem@davemloft.net \
    --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 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).