I compared the commits to Jaunty ecryptfs versus 2.6.29-rc7 and found these differences (e.g. ecryptfs commits missing in Jaunty):
fs/Kconfig: move ecryptfs out
add a vfs_fsync helper
inode->i_op is never NULL
CRED: Pass credentials through dentry_open()
CRED: Wrap task credential accesses in the eCryptFS filesystem
The one that caught my eye is 'add a vfs_fsync helper'. Quoting from the commit log, "ecryptfs wasn't calling filemap_fdatawrite / filemap_fdatawait on the lower file". This is commit 4c728ef583b3d82266584da5cb068294c09df31e.
Tyler - would you care to comment on the possibility that the vfs helper function is the root of the errors that Dustin is seeing? The rest of the missing commits are mostly house keeping stuff and should not have any runtime impact.
I compared the commits to Jaunty ecryptfs versus 2.6.29-rc7 and found these differences (e.g. ecryptfs commits missing in Jaunty):
fs/Kconfig: move ecryptfs out
add a vfs_fsync helper
inode->i_op is never NULL
CRED: Pass credentials through dentry_open()
CRED: Wrap task credential accesses in the eCryptFS filesystem
The one that caught my eye is 'add a vfs_fsync helper'. Quoting from the commit log, "ecryptfs wasn't calling filemap_fdatawrite / filemap_fdatawait on the lower file". This is commit 4c728ef583b3d82 266584da5cb0682 94c09df31e.
Tyler - would you care to comment on the possibility that the vfs helper function is the root of the errors that Dustin is seeing? The rest of the missing commits are mostly house keeping stuff and should not have any runtime impact.