| 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: <20160804074546.GA996@gondor.apana.org.au> Date: Thu, 4 Aug 2016 15:45:46 +0800 From: Herbert Xu <herbert@...dor.apana.org.au> To: "David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org, Johannes Berg <johannes.berg@...el.com>, linux-wireless@...r.kernel.org Cc: Thomas Graf <tgraf@...g.ch>, tom@...bertland.com Subject: Re: Buggy rhashtable walking On Thu, Aug 04, 2016 at 03:18:46PM +0800, Herbert Xu wrote: > > So the question is can wireless handle seeing an entry multiple > times? In particular, __ieee80211_rx_handle_packet would appear > to process the same packet multiple times if this were to happen. It's worse than I thought. In fact it's not walking the table at all, rather it's doing a hash lookup by hand! This cannot possibly work given that rhashtable makes use of multiple hash tables. In fact this also demonstrates why putting multiple identical objects into the same table is crap. Because there is no sane way of returning all objects corresponding to a single key, given that they may be spread over multiple tables. So I'm going to fix this by consolidating identical objects into a single rhashtable entry which also lets us get rid of the insecure_elasticity setting. So the next time someone comes along and wants to add multiple objects with the same key to one table, please just say no. Thanks, -- 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
Powered by blists - more mailing lists