Comment 3 for bug 331082

On Thu, Mar 5, 2009 at 3:27 PM, Tyler Hicks <email address hidden> wrote:
> I made a quick list of the commit difference between the current jaunty
> and 2.6.29-rc7 git trees.  Unfortunately, several of these patches touch
> quite a bit more than eCryptfs code.
>
> Missing from jaunty kernel:
> ---
> 745ca2475a6ac596e3d8d37c2759c0fbe2586227
> 4c728ef583b3d82266584da5cb068294c09df31e
> acfa4380efe77e290d3a96b11cd4c9f24f4fbb18
> 4eea03539d9a8e3f5056aed690efde1f75535e7b
> 18b6e0414e42d95183f07d8177e3ff0241abd825
> 295c896cb95de18004ef5e1b53f44c2ad001f936
> ---
>
> Added to jaunty kernel (not upstream):
> ---
> c9b68678c51d435e824214926d41e1ab5e9f7b99
> ---

Thanks a lot, Tyler.

> After taking a closer look through these commits, nothing is jumping out
> at me as a fix for the syslog messages Dustin included above.  Dustin,
> are you still seeing these messages?

Yes, absolutely.

My dmesg output has hundreds of these two sets of error messages:

a)
[ 52.956360] ecryptfs_parse_tag_70_packet: max_packet_size is [56];
real packet size is [51]
[ 52.956368] ecryptfs_decode_and_decrypt_filename: Could not parse
tag 70 packet from filename; copying through filename as-is

b)
[ 62.572708] Valid eCryptfs headers not found in file header region
or xattr region
[ 62.572717] Either the lower file is not in a valid eCryptfs
format, or the key could not be retrieved. Plaintext passthrough mode
is not enabled; returning -EIO

I would really like to focus on getting those two issues resolved.
I'll file two separate bugs.

:-Dustin