[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1326471346.3826.23.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>
Date: Fri, 13 Jan 2012 17:15:46 +0100
From: Eric Dumazet <eric.dumazet@...il.com>
To: Dimitri Sivanich <sivanich@....com>
Cc: linux-kernel@...r.kernel.org,
Alexander Viro <viro@...iv.linux.org.uk>,
"David S. Miller" <davem@...emloft.net>,
Alexey Kuznetsov <kuznet@....inr.ac.ru>,
James Morris <jmorris@...ei.org>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
Patrick McHardy <kaber@...sh.net>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Paul Gortmaker <paul.gortmaker@...driver.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Jiri Kosina <jkosina@...e.cz>, Avi Kivity <avi@...hat.com>,
linux-fsdevel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH] Fix panic in __d_lookup with high dentry hashtable
counts
Le vendredi 13 janvier 2012 à 09:52 -0600, Dimitri Sivanich a écrit :
> When the number of dentry cache hash table entries gets too high
> (2147483648 entries), use of a signed integer in the initialization
> loop prevents the dentry_hashtable from getting initialized, resulting
> in a panic in __d_lookup. Fixing this in dcache_init and a few other
> spots for consistency.
Well...
nr_dentry being an int, I dont think having a so big hash table is
needed/possible. Its probably a waste of memory ?
Maybe we should limit alloc_large_system_hash() to at most 2^30 slots.
[ And later, convert it to unsigned long *_hash_shift and unsigned long
*_hash_mask ]
--
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