From: Daniel Borkmann <daniel@iogearbox.net>
To: Jakub Kicinski <kuba@kernel.org>, Jakub Sitnicki <jakub@cloudflare.com>
Cc: "David S. Miller" <davem@davemloft.net>,
David Ahern <dsahern@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Martin KaFai Lau <martin.lau@kernel.org>,
netdev@vger.kernel.org, bpf@vger.kernel.org,
kernel-team@cloudflare.com
Subject: Re: [PATCH net] net: Clear skb metadata before LWT xmit
Date: Thu, 14 May 2026 09:18:07 +0200 [thread overview]
Message-ID: <68a1cc81-80b2-4d49-916a-2d3aca4d54a6@iogearbox.net> (raw)
In-Reply-To: <dff89f5d-01ff-4869-bff2-5c5b285cf578@iogearbox.net>
On 5/14/26 9:04 AM, Daniel Borkmann wrote:
> On 5/14/26 2:26 AM, Jakub Kicinski wrote:
>> On Wed, 13 May 2026 11:17:12 +0200 Jakub Sitnicki wrote:
>>> I actually wanted to double-check with you and Daniel - is consuming
>>> metadata from TC egress supposed to be supported?
>>
>> Not AFAIK, let's see if Daniel has a use case in mind.
>
> The only case I can think of would be if someone uses metadata
> within the tc(x) layer, so from either tc ingress then xmit to
> tc egress or vice versa in order to store BPF-related data in> front, but iiuc that should still work with your patch.
Maybe the one case where it could break down is if you would
try to transport data from container-related iface (e.g. tc @
host-facing veth, or netkit) all the way to phys dev when there
is tunnel in between. Not sure if it would survive today,
potentially yes. In such case maybe better to move this further
into lwt related paths?
next prev parent reply other threads:[~2026-05-14 7:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 19:44 [PATCH net] net: Clear skb metadata before LWT xmit Jakub Sitnicki
2026-05-01 0:31 ` Jakub Kicinski
2026-05-13 9:17 ` Jakub Sitnicki
2026-05-14 0:26 ` Jakub Kicinski
2026-05-14 7:04 ` Daniel Borkmann
2026-05-14 7:18 ` Daniel Borkmann [this message]
2026-05-14 10:49 ` Jakub Sitnicki
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=68a1cc81-80b2-4d49-916a-2d3aca4d54a6@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jakub@cloudflare.com \
--cc=kernel-team@cloudflare.com \
--cc=kuba@kernel.org \
--cc=martin.lau@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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