From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-security-module@vger.kernel.org
Subject: [PATCH] integrity: silence warning when CONFIG_SECURITYFS is not enabled
Date: Mon, 4 Jun 2018 15:05:21 +0100 [thread overview]
Message-ID: <1528121121-3959-1-git-send-email-sudeep.holla@arm.com> (raw)
When CONFIG_SECURITYFS is not enabled, securityfs_create_dir returns
-ENODEV which throws the following error:
"Unable to create integrity sysfs dir: -19"
However, if the feature is disabled, it can't be warning and hence
we need to silence the error.
Cc: James Morris <jmorris@namei.org>
Cc: "Serge E. Hallyn" <serge@hallyn.com>
Cc: Matthew Garrett <mjg59@google.com>
Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
---
security/integrity/iint.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/security/integrity/iint.c b/security/integrity/iint.c
index 149faa81f6f0..8082491876f9 100644
--- a/security/integrity/iint.c
+++ b/security/integrity/iint.c
@@ -218,7 +218,7 @@ void __init integrity_load_keys(void)
static int __init integrity_fs_init(void)
{
integrity_dir = securityfs_create_dir("integrity", NULL);
- if (IS_ERR(integrity_dir)) {
+ if (IS_ENABLED(CONFIG_SECURITYFS) && IS_ERR(integrity_dir)) {
pr_err("Unable to create integrity sysfs dir: %ld\n",
PTR_ERR(integrity_dir));
integrity_dir = NULL;
--
2.7.4
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-06-04 14:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 14:05 Sudeep Holla [this message]
2018-06-04 17:44 ` [PATCH] integrity: silence warning when CONFIG_SECURITYFS is not enabled Matthew Garrett
2018-06-05 10:25 ` [PATCH v2] " Sudeep Holla
2018-06-05 14:49 ` Mimi Zohar
2018-06-06 9:23 ` Sudeep Holla
2018-06-06 13:24 ` Mimi Zohar
2018-06-06 21:07 ` Matthew Garrett
2018-06-13 15:00 ` [PATCH v3] " Sudeep Holla
2018-06-13 22:13 ` Mimi Zohar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1528121121-3959-1-git-send-email-sudeep.holla@arm.com \
--to=sudeep.holla@arm.com \
--cc=linux-security-module@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).