From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Chengen Du <chengen.du@canonical.com>, willemdebruijn.kernel@gmail.com
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Chengen Du <chengen.du@canonical.com>
Subject: Re: [PATCH] af_packet: Handle outgoing VLAN packets without hardware offloading
Date: Mon, 20 May 2024 14:35:20 -0400 [thread overview]
Message-ID: <664b97e8abe7a_12b4762946f@willemb.c.googlers.com.notmuch> (raw)
In-Reply-To: <20240520070348.26725-1-chengen.du@canonical.com>
Chengen Du wrote:
> In the outbound packet path, if hardware VLAN offloading is unavailable,
> the VLAN tag is inserted into the payload but then cleared from the
> metadata. Consequently, this could lead to a false negative result when
> checking for the presence of a VLAN tag using skb_vlan_tag_present(),
> causing the packet sniffing outcome to lack VLAN tag information. As a
> result, the packet capturing tool may be unable to parse packets as
> expected.
>
> Signed-off-by: Chengen Du <chengen.du@canonical.com>
This is changing established behavior, which itself may confuse
existing PF_PACKET receivers.
The contract is that the VLAN tag can be observed in the payload or
as tp_vlan_* fields if it is offloaded.
> @@ -2457,7 +2464,8 @@ static int tpacket_rcv(struct sk_buff *skb, struct net_device *dev,
> sll->sll_halen = dev_parse_header(skb, sll->sll_addr);
> sll->sll_family = AF_PACKET;
> sll->sll_hatype = dev->type;
> - sll->sll_protocol = skb->protocol;
> + sll->sll_protocol = eth_type_vlan(skb->protocol) ?
> + vlan_eth_hdr(skb)->h_vlan_encapsulated_proto : skb->protocol;
This is a particularly subtle change of behavior.
> if (skb_vlan_tag_present(skb)) {
> aux.tp_vlan_tci = skb_vlan_tag_get(skb);
> aux.tp_vlan_tpid = ntohs(skb->vlan_proto);
> - aux.tp_status |= TP_STATUS_VLAN_VALID | TP_STATUS_VLAN_TPID_VALID;
> + } else if (eth_type_vlan(skb->protocol)) {
> + aux.tp_vlan_tci = ntohs(vlan_eth_hdr(skb)->h_vlan_TCI);
> + aux.tp_vlan_tpid = ntohs(skb->protocol);
> } else {
> aux.tp_vlan_tci = 0;
> aux.tp_vlan_tpid = 0;
> }
> + if (aux.tp_vlan_tci || aux.tp_vlan_tpid)
> + aux.tp_status |= TP_STATUS_VLAN_VALID | TP_STATUS_VLAN_TPID_VALID;
> put_cmsg(msg, SOL_PACKET, PACKET_AUXDATA, sizeof(aux), &aux);
vlan_tci 0 is valid identifier. That's the reason explicit field
TP_STATUS_VLAN_VALID was added.
next prev parent reply other threads:[~2024-05-20 18:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 7:03 [PATCH] af_packet: Handle outgoing VLAN packets without hardware offloading Chengen Du
2024-05-20 18:35 ` Willem de Bruijn [this message]
2024-05-21 3:31 ` Chengen Du
2024-05-21 8:35 ` Paolo Abeni
2024-05-21 13:28 ` Willem de Bruijn
2024-05-22 14:27 ` Chengen Du
2024-05-22 18:39 ` Willem de Bruijn
2024-05-22 19:54 ` alexandre.ferrieux
2024-05-23 14:17 ` Chengen Du
2024-05-23 14:52 ` Willem de Bruijn
2024-05-23 14:56 ` Willem de Bruijn
2024-05-24 14:04 ` Chengen Du
2024-05-25 15:51 ` Willem de Bruijn
2024-05-25 20:55 ` alexandre.ferrieux
2024-05-26 15:25 ` Willem de Bruijn
2024-05-27 0:18 ` alexandre.ferrieux
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=664b97e8abe7a_12b4762946f@willemb.c.googlers.com.notmuch \
--to=willemdebruijn.kernel@gmail.com \
--cc=chengen.du@canonical.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.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