From: David Howells In-Reply-To: <20061114200621.12943.18023.stgit@warthog.cambridge.redhat.com> References: <20061114200621.12943.18023.stgit@warthog.cambridge.redhat.com> To: trond.myklebust@fys.uio.no, torvalds@osdl.org, akpm@osdl.org, sds@tycho.nsa.gov Cc: dhowells@redhat.com, selinux@tycho.nsa.gov, linux-kernel@vger.kernel.org, aviro@redhat.com, steved@redhat.com Subject: [PATCH 23/19] FS-Cache: NFS: Don't invoke FS-Cache from nfs_zap_caches() Date: Wed, 15 Nov 2006 16:42:56 +0000 Message-ID: <29409.1163608976@redhat.com> Sender: owner-selinux@tycho.nsa.gov List-Id: selinux@tycho.nsa.gov Don't invoke FS-Cache from nfs_zap_caches() as that is supposed to be quick whereas FS-Cache may get semaphores and other sleepy things. As it happens, the cache will be zapped upon the next revalidation anyway, and so this is probably unnecessary. Signed-Off-By: David Howells --- fs/nfs/inode.c | 2 -- 1 files changed, 0 insertions(+), 2 deletions(-) diff --git a/fs/nfs/inode.c b/fs/nfs/inode.c index 0d683eb..25376a5 100644 --- a/fs/nfs/inode.c +++ b/fs/nfs/inode.c @@ -130,8 +130,6 @@ void nfs_zap_caches(struct inode *inode) spin_lock(&inode->i_lock); nfs_zap_caches_locked(inode); spin_unlock(&inode->i_lock); - - nfs_fscache_zap_fh_cookie(inode); } void nfs_zap_mapping(struct inode *inode, struct address_space *mapping) -- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with the words "unsubscribe selinux" without quotes as the message.