ecryptfs team mailing list archive

[Tim Gardner <tim.gardner@xxxxxxxxxxxxx>]

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.

-- 
please sync jaunty ecryptfs kernel module with linus' git tree
https://bugs.launchpad.net/bugs/331082
You received this bug notification because you are a member of eCryptfs,
which is subscribed to ecryptfs-utils in ubuntu.

Status in “ecryptfs-utils” source package in Ubuntu: Triaged
Status in “linux” source package in Ubuntu: Confirmed

Bug description:
Tim-

Please sync Jaunty's ecryptfs kernel module with Linus' upstream git tree.

There are some errors in dmesg that Tyler believes are fixed with the upstream code.  The messages on my system look like this:
[   46.330479] ecryptfs_parse_tag_70_packet: max_packet_size is [56]; real packet size is [51]
[   46.330486] ecryptfs_decode_and_decrypt_filename: Could not parse tag 70 packet from filename; copying through filename as-is

I'm attaching a patch from Tyler.

This is for spot-check review only!  I think it will be in our best interest for you to do the sync via git merging mechanisms.

Thanks,
:-Dustin