| 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
| ||
|
Message-ID: <CA+mtBx9TCtHgW=TegUgjZ6Se=mP+0CNiNHYmbYHPd1cJJGYoBQ@mail.gmail.com> Date: Wed, 29 Oct 2014 07:59:59 -0700 From: Tom Herbert <therbert@...gle.com> To: Or Gerlitz <ogerlitz@...lanox.com> Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org> Subject: Re: some failures with vxlan offloads.. On Tue, Oct 28, 2014 at 10:50 PM, Or Gerlitz <ogerlitz@...lanox.com> wrote: > On 10/28/2014 5:36 PM, Tom Herbert wrote: >>> >>> I wonder if we have another bug somewhere... when both sides were >>> offloaded, >>> >it works even with the mlx4 bug, canyou explain that?is it possible that >>> > the >>> >GRO stack somehow covers on the bug when both sides are offloaded and >>> >GRO/VXLAN comes into play? >>> >> Look at the receive side. As I mentioned, if the device is returning >> checksum-unnecessary and setting csum_level to 1 (inner checksum was >> validated) then stack won't try to verify the outer checksum. So in >> this case if outer checksum is incorrect nobody complains about it. > > > OK, I'll look there. Anything that should worries us at that stack trace I > sent in my initial email of this thread, or you think this is related to the > mlx4 driver checksum bug? > The trace doesn't seem like it would be related to a checksum bug. Do you only see this with offload enabled? > Or. > >> > -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists