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 --- 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? -- 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 _______________________________________________ Mailing list: https://launchpad.net/~ecryptfs Post to : [email protected] Unsubscribe : https://launchpad.net/~ecryptfs More help : https://help.launchpad.net/ListHelp
