linux/security/integrity/ima
Al Viro 5955102c99 wrappers for ->i_mutex access
parallel to mutex_{lock,unlock,trylock,is_locked,lock_nested},
inode_foo(inode) being mutex_foo(&inode->i_mutex).

Please, use those for access to ->i_mutex; over the coming cycle
->i_mutex will become rwsem, with ->lookup() done with it held
only shared.

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2016-01-22 18:04:28 -05:00
..
Kconfig IMA: allow reading back the current IMA policy 2015-12-15 10:01:43 -05:00
Makefile IMA: create machine owner and blacklist keyrings 2015-12-15 10:01:43 -05:00
ima.h IMA: policy can be updated zero times 2015-12-24 18:56:45 -05:00
ima_api.c
ima_appraise.c
ima_crypto.c mm, page_alloc: rename __GFP_WAIT to __GFP_RECLAIM 2015-11-06 17:50:42 -08:00
ima_fs.c ima: ima_write_policy() limit locking 2016-01-03 13:22:38 -05:00
ima_init.c integrity: define '.evm' as a builtin 'trusted' keyring 2015-11-23 14:30:02 -05:00
ima_main.c wrappers for ->i_mutex access 2016-01-22 18:04:28 -05:00
ima_mok.c security/integrity: make ima/ima_mok.c explicitly non-modular 2015-12-15 10:01:43 -05:00
ima_policy.c IMA: policy can be updated zero times 2015-12-24 18:56:45 -05:00
ima_queue.c
ima_template.c
ima_template_lib.c
ima_template_lib.h