Re: [PATCH] fsstack: fsstack_copy_inode_size locking

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Christoph Hellwig
Date: Sunday, June 29, 2008 - 12:15 am

On Sun, Jun 29, 2008 at 01:05:09AM +0100, Hugh Dickins wrote:

Btw, I hope fsstack doesn't rely on i_size having any particular
meaning.  As far as the VFS is concerned i_size is field only used by
the filesystem (or library routines like generic_file_*).

--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH] fsstack: fsstack_copy_inode_size locking, Hugh Dickins, (Sat Jun 28, 5:05 pm)
[PATCH] unionfs: fix memory leak, Hugh Dickins, (Sat Jun 28, 5:07 pm)
Re: [PATCH] fsstack: fsstack_copy_inode_size locking, Christoph Hellwig, (Sun Jun 29, 12:15 am)
Re: [PATCH] fsstack: fsstack_copy_inode_size locking, Hugh Dickins, (Sun Jun 29, 4:56 am)
Re: [PATCH] fsstack: fsstack_copy_inode_size locking , Hugh Dickins, (Mon Jun 30, 5:10 am)
Re: [PATCH] unionfs: fix memory leak , Erez Zadok, (Mon Jun 30, 11:11 am)
Re: [PATCH] fsstack: fsstack_copy_inode_size locking , Erez Zadok, (Mon Jun 30, 11:19 am)
Re: [PATCH] fsstack: fsstack_copy_inode_size locking, Michael Halcrow, (Mon Jun 30, 2:49 pm)
Re: [PATCH] fsstack: fsstack_copy_inode_size locking, Christoph Hellwig, (Tue Jul 1, 12:03 am)