From: Nikolay Borisov <nborisov@suse.com>
Date: Tue, 11 Dec 2018 08:31:40 +0000 (+0200)
Subject: ima: Use inode_is_open_for_write
X-Git-Tag: v5.0-rc1~67^2~1^2
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=eed9de3b4f47114f440980203ca27c5fab70f529;p=thirdparty%2Fkernel%2Flinux.git

ima: Use inode_is_open_for_write

Use the aptly named function rather than open coding the check. No
functional changes.

Signed-off-by: Nikolay Borisov <nborisov@suse.com>
Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>
---

diff --git a/security/integrity/ima/ima_main.c b/security/integrity/ima/ima_main.c
index df0b2ee49fa25..bd9bd5f882062 100644
--- a/security/integrity/ima/ima_main.c
+++ b/security/integrity/ima/ima_main.c
@@ -103,7 +103,7 @@ static void ima_rdwr_violation_check(struct file *file,
 	} else {
 		if (must_measure)
 			set_bit(IMA_MUST_MEASURE, &iint->atomic_flags);
-		if ((atomic_read(&inode->i_writecount) > 0) && must_measure)
+		if (inode_is_open_for_write(inode) && must_measure)
 			send_writers = true;
 	}