From: Jakub Kicinski <kuba@kernel.org>
To: Eric Dumazet <edumazet@google.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>, netdev <netdev@vger.kernel.org>,
Coco Li <lixiaoyan@google.com>, Tariq Toukan <tariqt@nvidia.com>,
Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH v4 net-next 12/12] mlx5: support BIG TCP packets
Date: Fri, 6 May 2022 19:37:34 -0700 [thread overview]
Message-ID: <20220506193734.408c2a0d@kernel.org> (raw)
In-Reply-To: <CANn89iKQtn0a-Etk-tBrwafbe6dkBz=d3=bkwd8j8_Ed+kiCPQ@mail.gmail.com>
On Fri, 6 May 2022 19:10:48 -0700 Eric Dumazet wrote:
> On Fri, May 6, 2022 at 6:54 PM Jakub Kicinski <kuba@kernel.org> wrote:
> > Without our patches drivers/net/ethernet/mellanox/mlx5/core/ builds
> > cleanly. Gotta be the new W=1 filed overflow warnings, let's bother
> > Kees.
>
> Note that inline_hdr.start is a 2 byte array.
>
> Obviously mlx5 driver copies more than 2 bytes of inlined headers.
>
> mlx5e_insert_vlan(eseg->inline_hdr.start, skb, attr->ihs)
> is called already with attr->ihs > 2
>
> So it should already complain ?
It's a static checker, I presume it ignores attr->ihs because
it can't prove its value is indeed > 2. Unpleasant :/
> static inline void mlx5e_insert_vlan(void *start, struct sk_buff *skb, u16 ihs)
> {
> struct vlan_ethhdr *vhdr = (struct vlan_ethhdr *)start;
> int cpy1_sz = 2 * ETH_ALEN;
> int cpy2_sz = ihs - cpy1_sz;
>
> memcpy(&vhdr->addrs, skb->data, cpy1_sz);
> vhdr->h_vlan_proto = skb->vlan_proto;
> vhdr->h_vlan_TCI = cpu_to_be16(skb_vlan_tag_get(skb));
> memcpy(&vhdr->h_vlan_encapsulated_proto, skb->data + cpy1_sz,
> cpy2_sz); // Here, more than 2 bytes are copied already
> }
next prev parent reply other threads:[~2022-05-07 2:37 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 15:30 [PATCH v4 net-next 00/12] tcp: BIG TCP implementation Eric Dumazet
2022-05-06 15:30 ` [PATCH v4 net-next 01/12] net: add IFLA_TSO_{MAX_SIZE|SEGS} attributes Eric Dumazet
2022-05-06 15:30 ` [PATCH v4 net-next 02/12] ipv6: add IFLA_GSO_IPV6_MAX_SIZE Eric Dumazet
2022-05-06 20:48 ` Alexander H Duyck
2022-05-06 21:20 ` Eric Dumazet
2022-05-06 21:37 ` Alexander Duyck
2022-05-06 21:50 ` Eric Dumazet
2022-05-06 22:16 ` Alexander Duyck
2022-05-06 22:25 ` Eric Dumazet
2022-05-06 22:26 ` Jakub Kicinski
2022-05-06 22:46 ` Alexander Duyck
2022-05-06 15:30 ` [PATCH v4 net-next 03/12] tcp_cubic: make hystart_ack_delay() aware of BIG TCP Eric Dumazet
2022-05-06 15:30 ` [PATCH v4 net-next 04/12] ipv6: add struct hop_jumbo_hdr definition Eric Dumazet
2022-05-06 15:30 ` [PATCH v4 net-next 05/12] ipv6/gso: remove temporary HBH/jumbo header Eric Dumazet
2022-05-06 15:30 ` [PATCH v4 net-next 06/12] ipv6/gro: insert " Eric Dumazet
2022-05-06 15:30 ` [PATCH v4 net-next 07/12] ipv6: add IFLA_GRO_IPV6_MAX_SIZE Eric Dumazet
2022-05-06 21:06 ` Alexander H Duyck
2022-05-06 21:22 ` Eric Dumazet
2022-05-06 22:01 ` Alexander Duyck
2022-05-06 22:08 ` Eric Dumazet
2022-05-09 18:17 ` [PATCH 0/2] Replacements for patches 2 and 7 in Big TCP series Alexander Duyck
2022-05-09 18:17 ` [PATCH 1/2] net: Allow gso_max_size to exceed 65536 Alexander Duyck
2022-05-09 18:17 ` [PATCH 2/2] net: Allow gro_max_size " Alexander Duyck
2022-05-09 18:54 ` [PATCH 0/2] Replacements for patches 2 and 7 in Big TCP series Eric Dumazet
2022-05-09 20:21 ` Alexander H Duyck
2022-05-09 20:31 ` Eric Dumazet
2022-05-09 21:05 ` Alexander Duyck
2022-05-06 15:30 ` [PATCH v4 net-next 08/12] ipv6: Add hop-by-hop header to jumbograms in ip6_output Eric Dumazet
2022-05-06 15:30 ` [PATCH v4 net-next 09/12] net: loopback: enable BIG TCP packets Eric Dumazet
2022-05-06 15:30 ` [PATCH v4 net-next 10/12] veth: " Eric Dumazet
2022-05-06 22:33 ` Jakub Kicinski
2022-05-06 15:30 ` [PATCH v4 net-next 11/12] mlx4: support " Eric Dumazet
2022-05-06 15:30 ` [PATCH v4 net-next 12/12] mlx5: " Eric Dumazet
2022-05-06 22:34 ` Jakub Kicinski
2022-05-07 0:32 ` Eric Dumazet
2022-05-07 1:54 ` Jakub Kicinski
2022-05-07 1:54 ` Jakub Kicinski
2022-05-07 2:10 ` Eric Dumazet
2022-05-07 2:37 ` Jakub Kicinski [this message]
2022-05-07 2:43 ` Eric Dumazet
2022-05-07 7:16 ` Kees Cook
2022-05-07 7:23 ` Kees Cook
2022-05-07 6:57 ` Kees Cook
2022-05-07 7:46 ` Kees Cook
2022-05-07 11:19 ` Eric Dumazet
2022-05-09 8:05 ` David Laight
2022-05-09 23:20 ` Kees Cook
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=20220506193734.408c2a0d@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=keescook@chromium.org \
--cc=leon@kernel.org \
--cc=lixiaoyan@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.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).