From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: [PATCH 10/14] sysfs: Rework sysfs_drop_dentry Date: Tue, 31 Jul 2007 20:17:57 +0900 Message-ID: <46AF1A65.9010304@suse.de> References: <1182446577.8138.29.camel@localhost> <46ADEE35.8000109@sw.ru> <46ADF003.3010100@suse.de> <46AEAF79.6080404@suse.de> <46AEBA87.6000400@suse.de> <46AEEF75.2030101@suse.de> <46AEEFA6.4000901@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: "Eric W. Biederman" Cc: Linux Containers , Greg KH , Greg KH , Dave Hansen List-Id: containers.vger.kernel.org Eric W. Biederman wrote: > This modifies sysfs_drop_dentry so it no longers needs the > sysfs_assoc_lock and it's assorted challenges. > > The principal idea is that __sysfs_get_dentry when not creating dentry > will return a dentry for the sysfs_dirent if there is one in the > dcache. If we do get a dentry we can drop it and force it out > of the cache. > > For good measure I am also calling shrink_dcache_parent which will > force all of the child dentries out of the dcache as well if it > is a directory. I don't think we need this as we drop all sd's recursively anyway. Can we drop it? Other than that, looks good. -- tejun