[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <C8A6796DE7C66C4ABCBC18106CB6C1CC164B83BE11@ESESSCMS0356.eemea.ericsson.se>
Date: Tue, 15 May 2012 07:57:22 +0200
From: Hans Schillström <hans.schillstrom@...csson.com>
To: Eric Dumazet <eric.dumazet@...il.com>,
Pablo Neira Ayuso <pablo@...filter.org>
CC: Jozsef Kadlecsik <kadlec@...ckhole.kfki.hu>,
Jan Engelhardt <jengelh@...i.de>,
"kaber@...sh.net" <kaber@...sh.net>,
"jengelh@...ozas.de" <jengelh@...ozas.de>,
"netfilter-devel@...r.kernel.org" <netfilter-devel@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"dan.carpenter@...cle.com" <dan.carpenter@...cle.com>,
"hans@...illstrom.com" <hans@...illstrom.com>
Subject: RE: [PATCH] netfilter: xt_HMARK: endian bugs
>On Mon, 2012-05-14 at 21:02 +0200, Pablo Neira Ayuso wrote:
>
>> IIRC, Hans wants that, in case you have a cluster composed of system
>> with different endianess, the hash mark calculated will be the same
>> in both systems. To ensure that the distribution is consistent with
>> independency of the endianess.
>
>Then jhash() must be audited to make sure its output is OK with this
>requirement.
Have done that, and made tests on a mips 32 running debian
It was as expected jhash3_words is endian safe, while jhash() is not
--
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