Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752516Ab0FWQ6S (ORCPT ); Wed, 23 Jun 2010 12:58:18 -0400 Received: from mx1.redhat.com ([209.132.183.28]:62343 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751372Ab0FWQ6R (ORCPT ); Wed, 23 Jun 2010 12:58:17 -0400 Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: <1277220206-3559-1-git-send-email-sjayaraman@suse.de> References: <1277220206-3559-1-git-send-email-sjayaraman@suse.de> To: Suresh Jayaraman Cc: dhowells@redhat.com, Steve French , linux-cifs@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC][PATCH 05/10] cifs: define superblock-level cache index objects and register them Date: Wed, 23 Jun 2010 17:58:10 +0100 Message-ID: <9720.1277312290@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 781 Lines: 18 Suresh Jayaraman wrote: > Define superblock-level cache index objects (managed by cifsTconInfo > structs). Each superblock object is created in a server-level index object > and in itself an index into which inode-level objects are inserted. > > Currently, the superblock objects are keyed by sharename. Seems reasonable. Is there any way you can check that the share you are looking at on a server is the same as the last time you looked? Can you validate the root directory of the share in some way? David -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/