From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jamie Lokier <jamie@shareable.org>
Subject: Re: [PATCH 1/2] [RFC] vfs: 'stat light' fstatat flags
Date: Tue, 7 Apr 2009 19:16:10 +0100
Message-ID: <20090407181610.GH31824@shareable.org>
References: <20090407080046.GQ14571@wotan.suse.de> <20090407174229.GD31824@shareable.org> <1D2105EA-A7C8-46C8-8AB9-380F9FCA7730@linuxhacker.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Mark Fasheh <mfasheh@suse.com>, linux-fsdevel@vger.kernel.org,
	Sage Weil <sage@newdream.net>,
	Trond Myklebust <Trond.Myklebust@netapp.com>,
	Andreas Dilger <adilger@sun.com>
To: Oleg Drokin <green@linuxhacker.ru>
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from mail2.shareable.org ([80.68.89.115]:36823 "EHLO
	mail2.shareable.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1754060AbZDGSQM (ORCPT
	<rfc822;linux-fsdevel@vger.kernel.org>);
	Tue, 7 Apr 2009 14:16:12 -0400
Content-Disposition: inline
In-Reply-To: <1D2105EA-A7C8-46C8-8AB9-380F9FCA7730@linuxhacker.ru>
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

Oleg Drokin wrote:
> >>AT_STRICT allows userspace to indicate that it wants the most up to  
> >>date
> >>version of a files status, regardless of performance impact. A  
> >>distributed
> >>file system which has a non-coherent inode cache would know then to  
> >>send a
> >>direct query to it's server.
> >Good idea!  Sort out some NFS pain.
> >If a filesystem doesn't honour AT_STRICT, can we have the function
> >return an error instead of stale values?
> 
> Supposedly the existing stat() is the way to do this?

I don't understand your response.  If an application wants to be sure
it has non-stale attributes, how does stat() help?  Are you saying
stat() does this?  (Afaik it doesn't on NFS).

-- Jamie