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 |
|---|---|---|
| evm | ||
| ima | ||
| platform_certs | ||
| Kconfig | -rw-r--r-- | 3.3 KB |
| Makefile | -rw-r--r-- | 895 bytes |
| digsig.c | -rw-r--r-- | 4.5 KB |
| digsig_asymmetric.c | -rw-r--r-- | 3.5 KB |
| iint.c | -rw-r--r-- | 5.3 KB |
| integrity.h | -rw-r--r-- | 6.9 KB |
| integrity_audit.c | -rw-r--r-- | 1.6 KB |
Computing file changes ...
