Daniel Borkmann 7f19fc5e0b netlink: use jhash as hashfn for rhashtable ... For netlink, we shouldn't be using arch_fast_hash() as a hashing discipline, but rather jhash() instead. Since netlink sockets can be opened by any user, a local attacker would be able to easily create collisions with the DPDK-derived arch_fast_hash(), which trades off performance for security by using crc32 CPU instructions on x86_64. While it might have a legimite use case in other places, it should be avoided in netlink context, though. As rhashtable's API is very flexible, we could later on still decide on other hashing disciplines, if legitimate. Reference: http://thread.gmane.org/gmane.linux.kernel/1844123 Fixes: e341694e3e ("netlink: Convert netlink_lookup() to use RCU protected hash table") Cc: Herbert Xu <herbert@gondor.apana.org.au> Signed-off-by: Daniel Borkmann <dborkman@redhat.com> Acked-by: Thomas Graf <tgraf@suug.ch> Acked-by: Hannes Frederic Sowa <hannes@stressinduktion.org> Signed-off-by: David S. Miller <davem@davemloft.net>		2014-12-10 15:17:45 -05:00
..
af_netlink.c	netlink: use jhash as hashfn for rhashtable	2014-12-10 15:17:45 -05:00
af_netlink.h	netlink: hold nl_sock_hash_lock during diag dump	2014-08-06 19:17:44 -07:00
diag.c	netlink: hold nl_sock_hash_lock during diag dump	2014-08-06 19:17:44 -07:00
genetlink.c
Kconfig
Makefile