Thanks for the info. I manually changed those two calls to ecryptfs_lookup_one_lower in inode.c back to lookup_one_len and it fixed the problem. Don't you just love patches that are released for bugs that don't exist any more just in case the patch might be useful sometime in the future? :)
But could this commit have resulted in the data loss that Kalle Valo reported? It seems to be just related to the file name/permissions/ownerships/size information and it made writing to (and reading of) files with encrypted filenames impossible. -- ecryptfs file permissions broken with kernel 2.6.36-rc2 https://bugs.launchpad.net/bugs/623087 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
