From: Nick Piggin Subject: Re: [patch 2/6] fs: no games with DCACHE_UNHASHED Date: Thu, 15 Oct 2009 10:13:43 +0200 Message-ID: <20091015081343.GC4262@wotan.suse.de> References: <20091015044026.319860788@suse.de> <20091015050048.165912589@suse.de> <4AD6D2E3.9050105@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Al Viro , linux-fsdevel@vger.kernel.org, Ian Kent , Linus Torvalds , linux-kernel@vger.kernel.org, Miklos Szeredi To: Eric Dumazet Return-path: Received: from cantor.suse.de ([195.135.220.2]:38361 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1762141AbZJOIOU (ORCPT ); Thu, 15 Oct 2009 04:14:20 -0400 Content-Disposition: inline In-Reply-To: <4AD6D2E3.9050105@gmail.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, Oct 15, 2009 at 09:44:35AM +0200, Eric Dumazet wrote: > npiggin@suse.de a =E9crit : > > (this is in -mm) > >=20 > > Filesystems outside the regular namespace do not have to clear DCAC= HE_UNHASHED > > in order to have a working /proc/$pid/fd/XXX. Nothing in proc preve= nts the > > fd link from being used if its dentry is not in the hash. > >=20 > > Also, it does not get put into the dcache hash if DCACHE_UNHASHED i= s clear; > > that depends on the filesystem calling d_add or d_rehash. > >=20 > > So delete the misleading comments and needless code. > >=20 >=20 > This was added in commit 304e61e6fbadec586dfe002b535f169a04248e49 >=20 > [PATCH] net: don't insert socket dentries into dentry_hashtable > =20 > We currently insert socket dentries into the global dentry hashta= ble. This > is suboptimal because there is currently no way these entries can= be used > for a lookup(). (/proc/xxx/fd/xxx uses a different mechanism). = Inserting > them in dentry hashtable slows dcache lookups. > =20 > To let __dpath() still work correctly (ie not adding a " (deleted= )") after > dentry name, we do : > =20 > - Right after d_alloc(), pretend they are hashed by clearing the > DCACHE_UNHASHED bit. > =20 > - Call d_instantiate() instead of d_add() : dentry is not inserte= d in > hash table. > =20 > __dpath() & friends work as intended during dentry lifetime. > =20 > - At dismantle time, once dput() must clear the dentry, setting a= gain > DCACHE_UNHASHED bit inside the custom d_delete() function provi= ded by > socket code, so that dput() can just kill_it. > =20 > Signed-off-by: Eric Dumazet > Cc: Al Viro > Acked-by: "David S. Miller" > Signed-off-by: Andrew Morton > Signed-off-by: Linus Torvalds >=20 >=20 >=20 > Back in 2006, we had to perform this hack in order to not leak '(dele= ted)' in __d_path() >=20 > if (!IS_ROOT(dentry) && d_unhashed(dentry) && > (prepend(&end, &buflen, " (deleted)", 10) !=3D 0))=20 > goto Elong; >=20 > In current kernel this part became : >=20 > if (d_unlinked(dentry) && > (prepend(&end, &buflen, " (deleted)", 10) !=3D 0)) > goto Elong; >=20 >=20 > So your cleanup seems good, thanks ! >=20 > Acked-by: Eric Dumazet Ahh, hmm d_unlinked() is exactly the same code. OK, so I think this sho= ws why I'm an idiot. I didn't think about the __d_path output. Though the comments are still misleading, in my defence (and my test programs did = not use any anoninode fds)... Now both sockets and pipes define a d_dname so they are OK, but anon_in= odes does not. I think they should probably be made to just provide a d_dnam= e anyway so we can have the familiar format of "pseudofs:[ino]" rather th= an "[pseudofs]" that we have now. That should make this patch work for anon_inodes.c as well. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html