Eric Richter 9a11a18902 ima: fix memory leak in ima_release_policy ... When the "policy" securityfs file is opened for read, it is opened as a sequential file. However, when it is eventually released, there is no cleanup for the sequential file, therefore some memory is leaked. This patch adds a call to seq_release() in ima_release_policy() to clean up the memory when the file is opened for read. Fixes: 80eae209d6 IMA: allow reading back the current policy Reported-by: Colin Ian King <colin.king@canonical.com> Signed-off-by: Eric Richter <erichte@linux.vnet.ibm.com> Tested-by: Colin Ian King <colin.king@canonical.com> Signed-off-by: Mimi Zohar <zohar@linux.vnet.ibm.com>		2016-11-13 22:50:08 -05:00
..
ima_api.c	ima: change integrity cache to store measured pcr	2016-06-30 01:14:22 -04:00
ima_appraise.c	Merge branch 'work.xattr' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs	2016-10-10 17:11:50 -07:00
ima_crypto.c	ima: calculate the hash of a buffer using aynchronous hash(ahash)	2016-02-18 17:14:44 -05:00
ima_fs.c	ima: fix memory leak in ima_release_policy	2016-11-13 22:50:08 -05:00
ima_init.c	ima: include pcr for each measurement log entry	2016-06-30 01:14:21 -04:00
ima_main.c	ima: use file_dentry()	2016-09-16 12:44:20 +02:00
ima_mok.c	IMA: Use the the system trusted keyrings instead of .ima_mok	2016-04-11 22:49:15 +01:00
ima_policy.c	ima: extend ima_get_action() to return the policy pcr	2016-06-30 01:14:20 -04:00
ima_queue.c	ima: extend the measurement entry specific pcr	2016-06-30 01:14:22 -04:00
ima_template_lib.c	ima: separate 'security.ima' reading functionality from collect	2016-02-18 17:13:32 -05:00
ima_template_lib.h	ima: wrap event related data to the new ima_event_data structure	2015-05-21 13:59:28 -04:00
ima_template.c	ima: separate 'security.ima' reading functionality from collect	2016-02-18 17:13:32 -05:00
ima.h	ima: include pcr for each measurement log entry	2016-06-30 01:14:21 -04:00
Kconfig	IMA: Use the the system trusted keyrings instead of .ima_mok	2016-04-11 22:49:15 +01:00
Makefile	IMA: Use the the system trusted keyrings instead of .ima_mok	2016-04-11 22:49:15 +01:00