netdev - Re: vxlan: Possible regression in vxlan

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Wed, 24 Nov 2021 18:14:21 +0100
From:   Jiri Benc <jbenc@...hat.com>
To:     Fabian Frédérick <fabf@...net.be>
Cc:     davem@...emloft.net, kuba@...nel.org, sbrivio@...hat.com,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: vxlan: Possible regression in vxlan_rcv()

On Tue, 23 Nov 2021 18:13:26 +0100 (CET), Fabian Frédérick wrote:
>    Can someone tell me if the update is really ok or how I could check 
> that code ?
> if VXLAN_F_REMCSUM_RX involves metadata checking I can ask to remove the 
> patch.

I don't think it matters.

I doubt anyone is using remote checksum offloading (RCO). It was based
on a half thought-through idea. Local checksum offloading is superior,
it gives you the same performance for free, with full compatibility with
the base VXLAN standard. And even trying hard, I can't imagine anyone
could be using RCO with metadata dst.

I wouldn't object against removing RCO completely from VXLAN (and
moving the "generic" RCO pieces to net/ipv4/fou.c, which would become
its only user). It would simplify the code and I doubt anyone would
notice. I'm serious. Try googling for remcsumtx or remcsumrx and see
for yourself.

And, in case you still wonder, your patch seems fine to me. It's somehow
pointless, since it optimizes drops for an extension that nobody uses,
but it should not affect the code correctness. Probably. Whatever.

 Jiri