[lkml]   [2002]   [Sep]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.4.20pre5aa1
On Thu, Sep 05, 2002 at 01:44:14PM +0100, Christoph Hellwig wrote:
> > Only in 2.4.20pre5aa1: 00_prepare-write-fixes-3-1
> >
> > Also check the i_size is in sync with the last block we allocated in
> > the metadata, it won't be updated in the commit_write if prepare_write
> > is failing.
> When testing -aa + my xfs update without the 9* series. this gave an compile
> error. Any chance you could move it after 96_inode_read_write-atomic-4?

correct, thanks.

btw, even if xfs is applied before the inode_read_write-atomic, please
make sure xfs will learn using the i_size_read when out of the semaphore
and i_size_write too. I know the locking is different there but I doubt
you're just managing the i_size without races. So it's up to you, either
move xfs patches after inode_read_Write-atomic, or make a separate
race-fix against the xfs codebase at the 70 level. It's not urgent btw,
the inode_read_write doesn't break anything yet (or I couldn't deal with
the flood of errors in every i_size read/write in all the fs out there),
so you won't notice it, but it gives you a chance to fix the races in
the "important" production filesystems. The pagecache/vfs layer should
be safe now, so most fs should be just safe with it. If the fixes will
came later as an incremental patch to apply at the end after a first xfs
update, that's fine with me.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:28    [W:0.082 / U:0.188 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site