Revision aa1918f9491442a007a0cbe41a31539233209777 authored by Al Viro on 18 December 2019, 01:09:08 UTC, committed by Al Viro on 07 February 2020, 19:48:30 UTC
Its behaviour is identical to that of fs_value_is_filename. It makes no sense, anyway - LOOKUP_EMPTY affects nothing whatsoever once the pathname has been imported from userland. And both fs_value_is_filename and fs_value_is_filename_empty carry an already imported pathname. Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
1 parent 34264ae
| File | Mode | Size |
|---|---|---|
| apparmor | ||
| integrity | ||
| keys | ||
| loadpin | ||
| lockdown | ||
| safesetid | ||
| selinux | ||
| smack | ||
| tomoyo | ||
| yama | ||
| Kconfig | -rw-r--r-- | 10.7 KB |
| Kconfig.hardening | -rw-r--r-- | 7.9 KB |
| Makefile | -rw-r--r-- | 1.2 KB |
| commoncap.c | -rw-r--r-- | 38.9 KB |
| device_cgroup.c | -rw-r--r-- | 20.8 KB |
| inode.c | -rw-r--r-- | 10.6 KB |
| lsm_audit.c | -rw-r--r-- | 10.6 KB |
| min_addr.c | -rw-r--r-- | 1.3 KB |
| security.c | -rw-r--r-- | 59.7 KB |
Computing file changes ...
