| To: | Artem Bityutskiy <Artem.Bityutskiy@xxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH] always set a/c/mtime through ->setattr |
| From: | Christoph Hellwig <hch@xxxxxx> |
| Date: | Tue, 20 May 2008 08:28:15 +0200 |
| Cc: | Christoph Hellwig <hch@xxxxxx>, viro@xxxxxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx |
| In-reply-to: | <48326D66.8000106@xxxxxxxxx> |
| References: | <20080520060838.GA6436@xxxxxx> <48326D66.8000106@xxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.3.28i |
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. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] always set a/c/mtime through ->setattr, Artem Bityutskiy |
|---|---|
| Next by Date: | Re: [PATCH] sanitize xfs_initialize_vnode, Christoph Hellwig |
| Previous by Thread: | Re: [PATCH] always set a/c/mtime through ->setattr, Artem Bityutskiy |
| Next by Thread: | Re: [PATCH] always set a/c/mtime through ->setattr, Miklos Szeredi |
| Indexes: | [Date] [Thread] [Top] [All Lists] |