| 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: <20141115155108.GA21998@gondor.apana.org.au> Date: Sat, 15 Nov 2014 23:51:08 +0800 From: Herbert Xu <herbert@...dor.apana.org.au> To: Thomas Graf <tgraf@...g.ch> Cc: netdev@...r.kernel.org, eric.dumazet@...il.com, paulmck@...ux.vnet.ibm.com, josh@...htriplett.org, "David S. Miller" <davem@...emloft.net> Subject: Re: [PATCH 4/4] rhashtable: Add parent argument to mutex_is_held On Sat, Nov 15, 2014 at 07:23:13PM +0800, Herbert Xu wrote: > > This is I think a show-stopper because for anything that can be > influenced by remote parties we have to reseed and therefore > be able to cope with hashes changing on the fly. Since most > hash tables in the network stack can be influenced by remote > entities (including the xfrm policy bydst hash that I am currently > working on), this is something rhashtable must be able to support > if it is to be used throughout the network stack. So I noticed that you got rid of the rehash when you converted netlink over to rthashtable. Was this aspect of the conversion discussed anywhere? In particular, how do you protect against a malicious user that's trying to attack the netlink hash table? Cheers, -- Email: Herbert Xu <herbert@...dor.apana.org.au> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- 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