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]
Message-ID: <CAJZOPZKP3m1V97cKQ6fE0x+7mNXkUFZwxz0YohddxDVCD9O7Gw@mail.gmail.com>
Date:	Wed, 14 May 2014 13:29:34 +0300
From:	Or Gerlitz <or.gerlitz@...il.com>
To:	Tom Herbert <therbert@...gle.com>
Cc:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	David Miller <davem@...emloft.net>
Subject: Re: [PATCH 8/8] vxlan: Add support for zero UDP6 checksums

On Wed, May 14, 2014 at 1:48 AM, David Miller <davem@...emloft.net> wrote:
>
> From: Tom Herbert <therbert@...gle.com>
> Date: Mon, 12 May 2014 09:59:25 -0700 (PDT)
>
> > Added module parameters to specify sending of TX checksums and
> > allow receiving RX checksums. Also added a module parameter and
> > support for using IPv4 checksums on TX (default is off so zero
> > checksums are sent).
>
> Tom, definitely do not do this using module parameters.
> Extend the vxlan configuration to suppose this switch using netlink.
>

Tom,

FWIW, note that the netlink code which relates to vxlan netdevice
creation through rtnl link ops itself doesn't come
into play for the openvswitch vxlan use case, the shared section
between OVS vxlan ports and the rtnl link ops one
vxlan_sock_add() - so you might choose to propagate  the new values
through the ovs channel as a use case.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ