/openbmc/linux/fs/jfs/ |
H A D | jfs_inode.h | diff aa38572954ade525817fe88c54faebf85e5a61c0 Fri May 27 05:53:02 CDT 2011 Christoph Hellwig <hch@infradead.org> fs: pass exact type of data dirties to ->dirty_inode
Tell the filesystem if we just updated timestamp (I_DIRTY_SYNC) or anything else, so that the filesystem can track internally if it needs to push out a transaction for fdatasync or not.
This is just the prototype change with no user for it yet. I plan to push large XFS changes for the next merge window, and getting this trivial infrastructure in this window would help a lot to avoid tree interdependencies.
Also remove incorrect comments that ->dirty_inode can't block. That has been changed a long time ago, and many implementations rely on it.
Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|
H A D | inode.c | diff aa38572954ade525817fe88c54faebf85e5a61c0 Fri May 27 05:53:02 CDT 2011 Christoph Hellwig <hch@infradead.org> fs: pass exact type of data dirties to ->dirty_inode
Tell the filesystem if we just updated timestamp (I_DIRTY_SYNC) or anything else, so that the filesystem can track internally if it needs to push out a transaction for fdatasync or not.
This is just the prototype change with no user for it yet. I plan to push large XFS changes for the next merge window, and getting this trivial infrastructure in this window would help a lot to avoid tree interdependencies.
Also remove incorrect comments that ->dirty_inode can't block. That has been changed a long time ago, and many implementations rely on it.
Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|
/openbmc/linux/fs/jffs2/ |
H A D | os-linux.h | diff aa38572954ade525817fe88c54faebf85e5a61c0 Fri May 27 05:53:02 CDT 2011 Christoph Hellwig <hch@infradead.org> fs: pass exact type of data dirties to ->dirty_inode
Tell the filesystem if we just updated timestamp (I_DIRTY_SYNC) or anything else, so that the filesystem can track internally if it needs to push out a transaction for fdatasync or not.
This is just the prototype change with no user for it yet. I plan to push large XFS changes for the next merge window, and getting this trivial infrastructure in this window would help a lot to avoid tree interdependencies.
Also remove incorrect comments that ->dirty_inode can't block. That has been changed a long time ago, and many implementations rely on it.
Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|
H A D | fs.c | diff aa38572954ade525817fe88c54faebf85e5a61c0 Fri May 27 05:53:02 CDT 2011 Christoph Hellwig <hch@infradead.org> fs: pass exact type of data dirties to ->dirty_inode
Tell the filesystem if we just updated timestamp (I_DIRTY_SYNC) or anything else, so that the filesystem can track internally if it needs to push out a transaction for fdatasync or not.
This is just the prototype change with no user for it yet. I plan to push large XFS changes for the next merge window, and getting this trivial infrastructure in this window would help a lot to avoid tree interdependencies.
Also remove incorrect comments that ->dirty_inode can't block. That has been changed a long time ago, and many implementations rely on it.
Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|
/openbmc/linux/fs/nilfs2/ |
H A D | nilfs.h | diff aa38572954ade525817fe88c54faebf85e5a61c0 Fri May 27 05:53:02 CDT 2011 Christoph Hellwig <hch@infradead.org> fs: pass exact type of data dirties to ->dirty_inode
Tell the filesystem if we just updated timestamp (I_DIRTY_SYNC) or anything else, so that the filesystem can track internally if it needs to push out a transaction for fdatasync or not.
This is just the prototype change with no user for it yet. I plan to push large XFS changes for the next merge window, and getting this trivial infrastructure in this window would help a lot to avoid tree interdependencies.
Also remove incorrect comments that ->dirty_inode can't block. That has been changed a long time ago, and many implementations rely on it.
Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|
H A D | inode.c | diff aa38572954ade525817fe88c54faebf85e5a61c0 Fri May 27 05:53:02 CDT 2011 Christoph Hellwig <hch@infradead.org> fs: pass exact type of data dirties to ->dirty_inode
Tell the filesystem if we just updated timestamp (I_DIRTY_SYNC) or anything else, so that the filesystem can track internally if it needs to push out a transaction for fdatasync or not.
This is just the prototype change with no user for it yet. I plan to push large XFS changes for the next merge window, and getting this trivial infrastructure in this window would help a lot to avoid tree interdependencies.
Also remove incorrect comments that ->dirty_inode can't block. That has been changed a long time ago, and many implementations rely on it.
Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|
/openbmc/linux/fs/reiserfs/ |
H A D | super.c | diff aa38572954ade525817fe88c54faebf85e5a61c0 Fri May 27 05:53:02 CDT 2011 Christoph Hellwig <hch@infradead.org> fs: pass exact type of data dirties to ->dirty_inode
Tell the filesystem if we just updated timestamp (I_DIRTY_SYNC) or anything else, so that the filesystem can track internally if it needs to push out a transaction for fdatasync or not.
This is just the prototype change with no user for it yet. I plan to push large XFS changes for the next merge window, and getting this trivial infrastructure in this window would help a lot to avoid tree interdependencies.
Also remove incorrect comments that ->dirty_inode can't block. That has been changed a long time ago, and many implementations rely on it.
Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|
/openbmc/linux/fs/ubifs/ |
H A D | super.c | diff aa38572954ade525817fe88c54faebf85e5a61c0 Fri May 27 05:53:02 CDT 2011 Christoph Hellwig <hch@infradead.org> fs: pass exact type of data dirties to ->dirty_inode
Tell the filesystem if we just updated timestamp (I_DIRTY_SYNC) or anything else, so that the filesystem can track internally if it needs to push out a transaction for fdatasync or not.
This is just the prototype change with no user for it yet. I plan to push large XFS changes for the next merge window, and getting this trivial infrastructure in this window would help a lot to avoid tree interdependencies.
Also remove incorrect comments that ->dirty_inode can't block. That has been changed a long time ago, and many implementations rely on it.
Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|
/openbmc/linux/fs/ |
H A D | fs-writeback.c | diff aa38572954ade525817fe88c54faebf85e5a61c0 Fri May 27 05:53:02 CDT 2011 Christoph Hellwig <hch@infradead.org> fs: pass exact type of data dirties to ->dirty_inode
Tell the filesystem if we just updated timestamp (I_DIRTY_SYNC) or anything else, so that the filesystem can track internally if it needs to push out a transaction for fdatasync or not.
This is just the prototype change with no user for it yet. I plan to push large XFS changes for the next merge window, and getting this trivial infrastructure in this window would help a lot to avoid tree interdependencies.
Also remove incorrect comments that ->dirty_inode can't block. That has been changed a long time ago, and many implementations rely on it.
Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|
/openbmc/linux/fs/ext4/ |
H A D | ext4.h | diff aa38572954ade525817fe88c54faebf85e5a61c0 Fri May 27 05:53:02 CDT 2011 Christoph Hellwig <hch@infradead.org> fs: pass exact type of data dirties to ->dirty_inode
Tell the filesystem if we just updated timestamp (I_DIRTY_SYNC) or anything else, so that the filesystem can track internally if it needs to push out a transaction for fdatasync or not.
This is just the prototype change with no user for it yet. I plan to push large XFS changes for the next merge window, and getting this trivial infrastructure in this window would help a lot to avoid tree interdependencies.
Also remove incorrect comments that ->dirty_inode can't block. That has been changed a long time ago, and many implementations rely on it.
Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|
H A D | inode.c | diff aa38572954ade525817fe88c54faebf85e5a61c0 Fri May 27 05:53:02 CDT 2011 Christoph Hellwig <hch@infradead.org> fs: pass exact type of data dirties to ->dirty_inode
Tell the filesystem if we just updated timestamp (I_DIRTY_SYNC) or anything else, so that the filesystem can track internally if it needs to push out a transaction for fdatasync or not.
This is just the prototype change with no user for it yet. I plan to push large XFS changes for the next merge window, and getting this trivial infrastructure in this window would help a lot to avoid tree interdependencies.
Also remove incorrect comments that ->dirty_inode can't block. That has been changed a long time ago, and many implementations rely on it.
Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|
/openbmc/linux/fs/btrfs/ |
H A D | ctree.h | diff aa38572954ade525817fe88c54faebf85e5a61c0 Fri May 27 05:53:02 CDT 2011 Christoph Hellwig <hch@infradead.org> fs: pass exact type of data dirties to ->dirty_inode
Tell the filesystem if we just updated timestamp (I_DIRTY_SYNC) or anything else, so that the filesystem can track internally if it needs to push out a transaction for fdatasync or not.
This is just the prototype change with no user for it yet. I plan to push large XFS changes for the next merge window, and getting this trivial infrastructure in this window would help a lot to avoid tree interdependencies.
Also remove incorrect comments that ->dirty_inode can't block. That has been changed a long time ago, and many implementations rely on it.
Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|
H A D | inode.c | diff aa38572954ade525817fe88c54faebf85e5a61c0 Fri May 27 05:53:02 CDT 2011 Christoph Hellwig <hch@infradead.org> fs: pass exact type of data dirties to ->dirty_inode
Tell the filesystem if we just updated timestamp (I_DIRTY_SYNC) or anything else, so that the filesystem can track internally if it needs to push out a transaction for fdatasync or not.
This is just the prototype change with no user for it yet. I plan to push large XFS changes for the next merge window, and getting this trivial infrastructure in this window would help a lot to avoid tree interdependencies.
Also remove incorrect comments that ->dirty_inode can't block. That has been changed a long time ago, and many implementations rely on it.
Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|
/openbmc/linux/include/linux/ |
H A D | fs.h | diff aa38572954ade525817fe88c54faebf85e5a61c0 Fri May 27 05:53:02 CDT 2011 Christoph Hellwig <hch@infradead.org> fs: pass exact type of data dirties to ->dirty_inode
Tell the filesystem if we just updated timestamp (I_DIRTY_SYNC) or anything else, so that the filesystem can track internally if it needs to push out a transaction for fdatasync or not.
This is just the prototype change with no user for it yet. I plan to push large XFS changes for the next merge window, and getting this trivial infrastructure in this window would help a lot to avoid tree interdependencies.
Also remove incorrect comments that ->dirty_inode can't block. That has been changed a long time ago, and many implementations rely on it.
Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|