android_kernel_xiaomi_sm8350/fs/ecryptfs
Eric Sandeen 7a3f595cc8 ecryptfs: fix fsx data corruption problems
ecryptfs in 2.6.24-rc3 wasn't surviving fsx for me at all, dying after 4
ops.  Generally, encountering problems with stale data and improperly
zeroed pages.  An extending truncate + write for example would expose stale
data.

With the changes below I got to a million ops and beyond with all mmap ops
disabled - mmap still needs work.  (A version of this patch on a RHEL5
kernel ran for over 110 million fsx ops)

I added a few comments as well, to the best of my understanding
as I read through the code.

Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Acked-by: Michael Halcrow <mhalcrow@us.ibm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-12-17 19:28:17 -08:00
..
crypto.c eCryptfs: release mutex on hash error path 2007-11-05 15:12:33 -08:00
debug.c
dentry.c
ecryptfs_kernel.h
file.c
inode.c ecryptfs: allow lower fs to interpret ATTR_KILL_S*ID 2007-10-18 14:37:21 -07:00
keystore.c ecryptfs: initialize new auth_tokens before teardown 2007-12-17 19:28:15 -08:00
main.c ecryptfs: set s_blocksize from lower fs in sb 2007-12-17 19:28:17 -08:00
Makefile
messaging.c
mmap.c ecryptfs: fix fsx data corruption problems 2007-12-17 19:28:17 -08:00
netlink.c
read_write.c ecryptfs: fix fsx data corruption problems 2007-12-17 19:28:17 -08:00
super.c