Linux Security Modules development
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: linux-security-module@vger.kernel.org
Subject: shmem: fix LSM options parsing (fwd)
Date: Fri, 11 Oct 2019 10:00:33 +1100 (AEDT)	[thread overview]
Message-ID: <alpine.LRH.2.21.1910111000260.9215@namei.org> (raw)

---------- Forwarded message ----------
Date: Thu, 10 Oct 2019 15:42:18 +0000
From: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Reply-To: Al Viro <viro@zeniv.linux.org.uk>
To: git-commits-head@vger.kernel.org
Subject: shmem: fix LSM options parsing

Commit:     33f37c648812bdbe1bd1eea75ddab3e799d51e77
Parent:     a3bc18a48e2e678efe62f1f9989902f9cd19e0ff
Refname:    refs/heads/master
Web:        https://git.kernel.org/torvalds/c/33f37c648812bdbe1bd1eea75ddab3e799d51e77
Author:     Al Viro <viro@zeniv.linux.org.uk>
AuthorDate: Wed Oct 9 22:48:01 2019 -0400
Committer:  Al Viro <viro@zeniv.linux.org.uk>
CommitDate: Wed Oct 9 22:48:01 2019 -0400

    shmem: fix LSM options parsing
    
    ->parse_monolithic() there forgets to call security_sb_eat_lsm_opts()
    
    Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
---
 mm/shmem.c | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/mm/shmem.c b/mm/shmem.c
index 0f7fd4a85db6..8dcc8d04cbaf 100644
--- a/mm/shmem.c
+++ b/mm/shmem.c
@@ -3482,6 +3482,12 @@ static int shmem_parse_options(struct fs_context *fc, void *data)
 {
 	char *options = data;
 
+	if (options) {
+		int err = security_sb_eat_lsm_opts(options, &fc->security);
+		if (err)
+			return err;
+	}
+
 	while (options != NULL) {
 		char *this_char = options;
 		for (;;) {

                 reply	other threads:[~2019-10-10 23:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=alpine.LRH.2.21.1910111000260.9215@namei.org \
    --to=jmorris@namei.org \
    --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