From: Andrei Vagin <avagin@openvz.org>
To: David Howells <dhowells@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, Andrei Vagin <avagin@gmail.com>
Subject: [PATCH dhowells/mount-api] fs: fix checking an error code of security_fs_context_parse_param
Date: Wed, 5 Sep 2018 17:10:51 -0700 [thread overview]
Message-ID: <20180906001051.24015-1-avagin@openvz.org> (raw)
From: Andrei Vagin <avagin@gmail.com>
security_fs_context_parse_param() returns 0 if everything is okay.
Signed-off-by: Andrei Vagin <avagin@gmail.com>
---
fs/fs_context.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/fs_context.c b/fs/fs_context.c
index a82679441031..16bf2cb57534 100644
--- a/fs/fs_context.c
+++ b/fs/fs_context.c
@@ -146,7 +146,7 @@ int vfs_parse_fs_param(struct fs_context *fc, struct fs_parameter *param)
return ret;
ret = security_fs_context_parse_param(fc, param);
- if (ret != -ENOPARAM)
+ if (ret)
/* Param belongs to the LSM or is disallowed by the LSM; so
* don't pass to the FS.
*/
--
2.17.1
next reply other threads:[~2018-09-06 4:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 0:10 Andrei Vagin [this message]
2018-09-06 10:16 ` [PATCH dhowells/mount-api] fs: fix checking an error code of security_fs_context_parse_param David Howells
2018-09-06 18:44 ` [PATCH dhowells/mount-api] fs: return -ENOPARAM from security_fs_context_parse_param by default Andrei Vagin
2018-09-06 23:08 ` [PATCH dhowells/mount-api] fs: fix checking an error code of security_fs_context_parse_param Andrei Vagin
2018-09-11 20:15 ` [PATCH dhowells/mount-api] fs: return -ENOPARAM from security_fs_context_parse_param by default David Howells
2018-09-06 10:18 ` [PATCH dhowells/mount-api] fs: fix checking an error code of security_fs_context_parse_param David Howells
2018-09-11 5:12 ` Andrei Vagin
2018-09-11 20:13 ` David Howells
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=20180906001051.24015-1-avagin@openvz.org \
--to=avagin@openvz.org \
--cc=avagin@gmail.com \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@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).