ecryptfs team mailing list archive

[Tyler Hicks <tyhicks@xxxxxxxxxxxxxxxxxx>]

Hi Tim - I agree that the vfs_fsync patch is the only one of much
interest, but it isn't the cause of Dustin's problems.  We have been
working together to determine the problem and figured out that he had
some non-eCryptfs files in his lower mount point.  This is due to a
problem where creates can fail and eCryptfs leaves a zero length file
around instead of cleaning up after the failed create.  The empty file
doesn't have the proper eCryptfs header and the kernel module will
complain and return -EIO.  I've opened a bug up for this:

https://bugs.launchpad.net/ecryptfs/+bug/338826

-- 
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