From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH] always set a/c/mtime through ->setattr Date: Tue, 20 May 2008 08:28:15 +0200 Message-ID: <20080520062815.GA8324@lst.de> References: <20080520060838.GA6436@lst.de> <48326D66.8000106@nokia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Christoph Hellwig , viro@ZenIV.linux.org.uk, linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com To: Artem Bityutskiy Return-path: Received: from verein.lst.de ([213.95.11.210]:41571 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754863AbYETG22 (ORCPT ); Tue, 20 May 2008 02:28:28 -0400 Content-Disposition: inline In-Reply-To: <48326D66.8000106@nokia.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Tue, May 20, 2008 at 09:19:18AM +0300, Artem Bityutskiy wrote: > Could we go a further and allow the file-system returning error if it > for some reasons cannot change the time? For example, the FS could > return -EIO or -ENOSPC up and VFS would have to free resources and > propagate this error to user-space. Is this possible? ->setattr and notify_change already return errors, so we just need to propagate them one level further. Feel free to send a patch.