netdev - Re: [net 05/14] net/mlx5e: Fix features check of IPv6 traffic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAJ3xEMiG=3e4sAxwAKYmw1gHgfW_AmuJNuQYmxiDTOSmzdUYrQ@mail.gmail.com>
Date:   Wed, 20 Dec 2017 09:45:15 +0200
From:   Or Gerlitz <gerlitz.or@...il.com>
To:     Gal Pressman <galp@...lanox.com>
Cc:     "David S. Miller" <davem@...emloft.net>,
        Linux Netdev List <netdev@...r.kernel.org>,
        Saeed Mahameed <saeedm@...lanox.com>
Subject: Re: [net 05/14] net/mlx5e: Fix features check of IPv6 traffic

On Wed, Dec 20, 2017 at 12:24 AM, Saeed Mahameed <saeedm@...lanox.com> wrote:
> From: Gal Pressman <galp@...lanox.com>
>
> The assumption that the next header field contains the transport
> protocol is wrong for IPv6 packets with extension headers.
> Instead, we should look the inner-most next header field in the buffer.
> This will fix TSO offload for tunnels over IPv6 with extension headers.

nice!

I would guess that there is some limitation to how many ipv6 ext
headers / bytes
the HW can deal with for TSO, are we enforcing that somehow (also for
the non-tunnel case)?

Or.