On 2010-07-19, at 11:09, Ryan O'Neill wrote: > I have developed a file system, it is a virtual memory file system > with persistence -- the persistence essentially works by storing the > fs data (from memory) into the slack space > of ext3 files (We are working on CentOS 5.3 -- old I know). The > following details should be sufficient. Sounds like a hacker toolkit. > Is this some type of page cache issue? How can I get around this? Any > input would be greatly appreciated. Thank you. > > I can't really give code slices, but the general idea is > > i_size = i_size_read(inode); > i_size += extended_size; > i_size_write(inode, isize); > mark_inode_dirty(ext3_inode); > wakeup_pdflush(0); <- I realize this is an overkill, but I was just > trying to get it to work before I used aops->commit_write on the > actual page of the inode. Anything you do like this is just begging to corrupt the user's data, since the "temporary" size change may race with real size changes and/or expose your data to normal applications. It's just a bad idea, IMHO. Cheers, Andreas -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
