From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH net-next] hv_netvsc: don't make assumptions on struct flow_keys layout Date: Thu, 14 Jan 2016 17:06:25 -0500 (EST) Message-ID: <20160114.170625.332893838261533719.davem@davemloft.net> References: Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: haiyangz@microsoft.com, eric.dumazet@gmail.com, gnomes@lxorguk.ukuu.org.uk, vkuznets@redhat.com, netdev@vger.kernel.org, kys@microsoft.com, devel@linuxdriverproject.org, linux-kernel@vger.kernel.org To: tom@herbertland.com Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org From: Tom Herbert Date: Thu, 14 Jan 2016 13:44:24 -0800 > The fact that we can negatively affect the output of Toeplitz so > predictably is actually a liability and not a benefit. This sort of > thing can be the basis of a DOS attack and is why we kicked out XOR > hash in favor of Jenkins. +1 Toeplitz should not be used for any software calculated flow hash whatsoever.