lkml.org 
[lkml]   [2018]   [Nov]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 4.14 100/100] ima: re-initialize iint->atomic_flags
    Date
    4.14-stable review patch.  If anyone has any objections, please let me know.

    ------------------

    From: Mimi Zohar <zohar@linux.vnet.ibm.com>

    commit e2598077dc6a26c9644393e5c21f22a90dbdccdb upstream.

    Intermittently security.ima is not being written for new files. This
    patch re-initializes the new slab iint->atomic_flags field before
    freeing it.

    Fixes: commit 0d73a55208e9 ("ima: re-introduce own integrity cache lock")
    Signed-off-by: Mimi Zohar <zohar@linux.vnet.ibm.com>
    Signed-off-by: James Morris <jmorris@namei.org>
    Cc: Aditya Kali <adityakali@google.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

    ---
    security/integrity/iint.c | 1 +
    1 file changed, 1 insertion(+)

    --- a/security/integrity/iint.c
    +++ b/security/integrity/iint.c
    @@ -74,6 +74,7 @@ static void iint_free(struct integrity_i
    iint->ima_hash = NULL;
    iint->version = 0;
    iint->flags = 0UL;
    + iint->atomic_flags = 0UL;
    iint->ima_file_status = INTEGRITY_UNKNOWN;
    iint->ima_mmap_status = INTEGRITY_UNKNOWN;
    iint->ima_bprm_status = INTEGRITY_UNKNOWN;

    \
     
     \ /
      Last update: 2018-11-29 15:42    [W:2.277 / U:0.280 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site