From: Leon Romanovsky <leon@kernel.org>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: Alexandre Cassen <acassen@corp.free.fr>, netdev@vger.kernel.org
Subject: Re: [RFC ipsec-next] xfrm: fix tunnel mode TX datapath in packet offload mode
Date: Mon, 17 Feb 2025 14:27:39 +0200 [thread overview]
Message-ID: <20250217122739.GA69863@unreal> (raw)
In-Reply-To: <Z68OQtAL2jiu/1Sg@gauss3.secunet.de>
On Fri, Feb 14, 2025 at 10:34:58AM +0100, Steffen Klassert wrote:
> On Wed, Feb 05, 2025 at 08:41:02PM +0200, Leon Romanovsky wrote:
> > From: Alexandre Cassen <acassen@corp.free.fr>
> >
> > +static int xfrm_dev_direct_output(struct sock *sk, struct xfrm_state *x,
> > + struct sk_buff *skb)
> > +{
> > + struct dst_entry *dst = skb_dst(skb);
> > + struct net *net = xs_net(x);
> > + int err;
> > +
> > + dst = skb_dst_pop(skb);
> > + if (!dst) {
> > + XFRM_INC_STATS(net, LINUX_MIB_XFRMOUTERROR);
> > + kfree_skb(skb);
> > + return -EHOSTUNREACH;
> > + }
> > + skb_dst_set(skb, dst);
> > + nf_reset_ct(skb);
> > +
> > + err = skb_dst(skb)->ops->local_out(net, sk, skb);
> > + if (unlikely(err != 1)) {
> > + kfree_skb(skb);
> > + return err;
> > + }
> > +
> > + /* In transport mode, network destination is
> > + * directly reachable, while in tunnel mode,
> > + * inner packet network may not be. In packet
> > + * offload type, HW is responsible for hard
> > + * header packet mangling so directly xmit skb
> > + * to netdevice.
> > + */
> > + skb->dev = x->xso.dev;
> > + __skb_push(skb, skb->dev->hard_header_len);
> > + return dev_queue_xmit(skb);
>
> I think this is absolutely the right thing for tunnel mode,
> but on transport mode we might bypass some valid netfilter
> rules.
Thanks for the acknowledge. We will prepare proper patch.
prev parent reply other threads:[~2025-02-17 12:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 18:41 [RFC ipsec-next] xfrm: fix tunnel mode TX datapath in packet offload mode Leon Romanovsky
2025-02-14 9:34 ` Steffen Klassert
2025-02-17 12:27 ` Leon Romanovsky [this message]
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=20250217122739.GA69863@unreal \
--to=leon@kernel.org \
--cc=acassen@corp.free.fr \
--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).