From: Christoph Hellwig <hch@infradead.org>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: David Howells <dhowells@redhat.com>,
linux-integrity <linux-integrity@vger.kernel.org>,
linux-security-module <linux-security-module@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] vfs: fix mounting a filesystem with i_version
Date: Sun, 8 Oct 2017 01:58:40 -0700 [thread overview]
Message-ID: <20171008085840.GA6825@infradead.org> (raw)
In-Reply-To: <1507436901.5841.4.camel@linux.vnet.ibm.com>
On Sun, Oct 08, 2017 at 12:28:21AM -0400, Mimi Zohar wrote:
> The mount i_version flag is not enabled in the new sb_flags. This patch
> adds the missing SB_I_VERSION flag.
>
> Fixes: e462ec5 "VFS: Differentiate mount flags (MS_*) from internal
> superblock flags"
> Signed-off-by: Mimi Zohar <zohar@linux.vnet.ibm.com>
> ---
> fs/namespace.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/fs/namespace.c b/fs/namespace.c
> index 3b601f115b6c..d18deb4c410b 100644
> --- a/fs/namespace.c
> +++ b/fs/namespace.c
> @@ -2825,7 +2825,8 @@ long do_mount(const char *dev_name, const char __user *dir_name,
> SB_MANDLOCK |
> SB_DIRSYNC |
> SB_SILENT |
> - SB_POSIXACL);
> + SB_POSIXACL |
> + SB_I_VERSION);
The problem is that the whole masking there is a piece of crap.
It assumes that MS_* and SB_* flags have the same numeric values,
which is bound to create a major problem rather sooner than later.
What we need is a separate __bitwise type for SB_*, translated them
here and treat them as a separate namespaces.
WARNING: multiple messages have this Message-ID (diff)
From: hch@infradead.org (Christoph Hellwig)
To: linux-security-module@vger.kernel.org
Subject: [PATCH] vfs: fix mounting a filesystem with i_version
Date: Sun, 8 Oct 2017 01:58:40 -0700 [thread overview]
Message-ID: <20171008085840.GA6825@infradead.org> (raw)
In-Reply-To: <1507436901.5841.4.camel@linux.vnet.ibm.com>
On Sun, Oct 08, 2017 at 12:28:21AM -0400, Mimi Zohar wrote:
> The mount i_version flag is not enabled in the new sb_flags. This patch
> adds the missing SB_I_VERSION flag.
>
> Fixes: e462ec5 "VFS: Differentiate mount flags (MS_*) from internal
> superblock flags"
> Signed-off-by: Mimi Zohar <zohar@linux.vnet.ibm.com>
> ---
> fs/namespace.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/fs/namespace.c b/fs/namespace.c
> index 3b601f115b6c..d18deb4c410b 100644
> --- a/fs/namespace.c
> +++ b/fs/namespace.c
> @@ -2825,7 +2825,8 @@ long do_mount(const char *dev_name, const char __user *dir_name,
> SB_MANDLOCK |
> SB_DIRSYNC |
> SB_SILENT |
> - SB_POSIXACL);
> + SB_POSIXACL |
> + SB_I_VERSION);
The problem is that the whole masking there is a piece of crap.
It assumes that MS_* and SB_* flags have the same numeric values,
which is bound to create a major problem rather sooner than later.
What we need is a separate __bitwise type for SB_*, translated them
here and treat them as a separate namespaces.
--
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 prev parent reply other threads:[~2017-10-08 8:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-08 4:28 [PATCH] vfs: fix mounting a filesystem with i_version Mimi Zohar
2017-10-08 4:28 ` Mimi Zohar
2017-10-08 8:58 ` Christoph Hellwig [this message]
2017-10-08 8:58 ` Christoph Hellwig
2017-10-08 12:54 ` Mimi Zohar
2017-10-08 12:54 ` Mimi Zohar
2017-10-08 12:54 ` Mimi Zohar
2017-10-08 22:24 ` James Morris
2017-10-08 22:24 ` James Morris
2017-10-11 12:28 ` Mimi Zohar
2017-10-11 12:28 ` Mimi Zohar
2017-10-11 12:28 ` 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=20171008085840.GA6825@infradead.org \
--to=hch@infradead.org \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=zohar@linux.vnet.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.