Revision 3d4b2fcbc980879a1385d5d7d17a4ffd0ee9aa1f authored by Eric Biggers on 19 December 2016, 19:15:48 UTC, committed by Richard Weinberger on 17 January 2017, 13:34:21 UTC
In several places, ubifs checked for an encryption key before creating a file in an encrypted directory. This was redundant with fscrypt_setup_filename() or ubifs_new_inode(), and in the case of ubifs_link() it broke linking to special files. So remove the extra checks. Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Richard Weinberger <richard@nod.at>
1 parent a75467d
| File | Mode | Size |
|---|---|---|
| syscalls | ||
| vdso | ||
| vsyscall | ||
| Makefile | -rw-r--r-- | 461 bytes |
| calling.h | -rw-r--r-- | 6.4 KB |
| common.c | -rw-r--r-- | 11.0 KB |
| entry_32.S | -rw-r--r-- | 29.2 KB |
| entry_64.S | -rw-r--r-- | 42.6 KB |
| entry_64_compat.S | -rw-r--r-- | 11.4 KB |
| syscall_32.c | -rw-r--r-- | 813 bytes |
| syscall_64.c | -rw-r--r-- | 919 bytes |
| thunk_32.S | -rw-r--r-- | 996 bytes |
| thunk_64.S | -rw-r--r-- | 1.6 KB |
Computing file changes ...
