From: David Miller Subject: Re: [RFC, PATCH] dont insert sockets/pipes dentries into dentry_hashtable. Date: Tue, 31 Oct 2006 23:19:54 -0800 (PST) Message-ID: <20061031.231954.23010447.davem@davemloft.net> References: <20061025084726.GE18364@nuim.ie> <20061025.230615.92585270.davem@davemloft.net> <200610311948.48970.dada1@cosmosbay.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org Return-path: Received: from dsl027-180-168.sfo1.dsl.speakeasy.net ([216.27.180.168]:11985 "EHLO sunset.davemloft.net") by vger.kernel.org with ESMTP id S1946654AbWKAHTx (ORCPT ); Wed, 1 Nov 2006 02:19:53 -0500 To: dada1@cosmosbay.com In-Reply-To: <200610311948.48970.dada1@cosmosbay.com> Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org From: Eric Dumazet Date: Tue, 31 Oct 2006 19:48:48 +0100 > We currently insert sockets/pipes dentries into the global dentry > hashtable. This is *useless* because there is currently no way > these entries can be used for a lookup(). (/proc/xxx/fd/xxx uses a > different mechanism) It turns out that while procfs uses a different "mechanism", those procfs symlinks do point to the real socket dentry, so when you readlink() on it you do d_path() on the real socket dentry. If you unhash these things, I'm pretty sure you'll see an ugly "(deleted)" at the end of the symlink string for /proc/$pid/fd/$X files that are sockets or something like that. Al Viro just suggested a way around this to me: 1) Just mark the dentry HASHED by hand in the dentry flags, but don't actually hash it. 2) Create a special dentry->d_deleted method for sockets that returns 0 and clears by hand the HASHED flag bit in the dentry (see what dput() does when this happens). It's an abuse but it will work.