As reported a coupl eof times on lkml since the 2.6.22 window opened, XFS is not updating the file size corectly in all cases. This is a result of the null files fix not updating the file size when t
I've had this (well, the first version you sent to Jeremy) for a few days on a testing machine without any obvious ill effects. Once people are happy with this it should be checked to see if it needs
Trying to understand how the initialisers prior to the loop are used during the loop. It looks like the initial "type" isn't used now with this change as we always assign to it near to where we acce
Yes. Because it's good practise - it's not obvious that it gets initialised in all cases within the loop, so lets make sure that it is.... ..... There is no difference in behaviour.... Yes. It's not
Looks pretty good to me - xfs_convert_page has been overlooked, I think - attached patch fixes that. You also initialise iomap_valid twice inside xfs_page_state_convert now ... I reverted that to jus
I thought about that, then tried to trip the problem and was not successful. AFAICT, if we have multiple pages dirty and in the same state (i.e. pwrite 0 32769 to dirty 3 pages, then sync, then pwrit
.... Patch below, Nathan. It's passed my point tests and XFSQA... Cheers, Dave. -- Dave Chinner Principal Engineer SGI Australian Software Group -- fs/xfs/linux-2.6/xfs_aops.c | 26 +++++++++++++++++-
As reported a coupl eof times on lkml since the 2.6.22 window opened, XFS is not updating the file size corectly in all cases. This is a result of the null files fix not updating the file size when t
I've had this (well, the first version you sent to Jeremy) for a few days on a testing machine without any obvious ill effects. Once people are happy with this it should be checked to see if it needs
Trying to understand how the initialisers prior to the loop are used during the loop. It looks like the initial "type" isn't used now with this change as we always assign to it near to where we acce
Yes. Because it's good practise - it's not obvious that it gets initialised in all cases within the loop, so lets make sure that it is.... ..... There is no difference in behaviour.... Yes. It's not
Looks pretty good to me - xfs_convert_page has been overlooked, I think - attached patch fixes that. You also initialise iomap_valid twice inside xfs_page_state_convert now ... I reverted that to jus
I thought about that, then tried to trip the problem and was not successful. AFAICT, if we have multiple pages dirty and in the same state (i.e. pwrite 0 32769 to dirty 3 pages, then sync, then pwrit