diff options
| author | 2014-06-27 18:04:27 +0300 | |
|---|---|---|
| committer | 2014-09-08 17:38:57 -0400 | |
| commit | b151d6b00bbb798c58f2f21305e7d43fa763f34f (patch) | |
| tree | 3a10265d73d01f900860aa9e7e1faa5c4eab4f4d /lib/memory-notifier-error-inject.c | |
| parent | evm: prevent passing integrity check if xattr read fails (diff) | |
| download | wireguard-linux-b151d6b00bbb798c58f2f21305e7d43fa763f34f.tar.xz wireguard-linux-b151d6b00bbb798c58f2f21305e7d43fa763f34f.zip | |
ima: provide flag to identify new empty files
On ima_file_free(), newly created empty files are not labeled with
an initial security.ima value, because the iversion did not change.
Commit dff6efc "fs: fix iversion handling" introduced a change in
iversion behavior. To verify this change use the shell command:
$ (exec >foo)
$ getfattr -h -e hex -d -m security foo
This patch defines the IMA_NEW_FILE flag. The flag is initially
set, when IMA detects that a new file is created, and subsequently
checked on the ima_file_free() hook to set the initial security.ima
value.
Signed-off-by: Dmitry Kasatkin <d.kasatkin@samsung.com>
Signed-off-by: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: <stable@vger.kernel.org> 3.14+
Diffstat (limited to 'lib/memory-notifier-error-inject.c')
0 files changed, 0 insertions, 0 deletions
