android_kernel_xiaomi_sm8350/fs/fuse
Miklos Szeredi 9c8ef5614d [PATCH] fuse: scramble lock owner ID
VFS uses current->files pointer as lock owner ID, and it wouldn't be
prudent to expose this value to userspace.  So scramble it with XTEA using
a per connection random key, known only to the kernel.  Only one direction
needs to be implemented, since the ID is never sent in the reverse
direction.

The XTEA algorithm is implemented inline since it's simple enough to do so,
and this adds less complexity than if the crypto API were used.

Thanks to Jesper Juhl for the idea.

Signed-off-by: Miklos Szeredi <miklos@szeredi.hu>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-06-25 10:01:20 -07:00
..
control.c [PATCH] fuse: add control filesystem 2006-06-25 10:01:19 -07:00
dev.c [PATCH] fuse: add request interruption 2006-06-25 10:01:19 -07:00
dir.c [PATCH] fuse: no backgrounding on interrupt 2006-06-25 10:01:19 -07:00
file.c [PATCH] fuse: scramble lock owner ID 2006-06-25 10:01:20 -07:00
fuse_i.h [PATCH] fuse: scramble lock owner ID 2006-06-25 10:01:20 -07:00
inode.c [PATCH] fuse: scramble lock owner ID 2006-06-25 10:01:20 -07:00
Makefile [PATCH] fuse: add control filesystem 2006-06-25 10:01:19 -07:00