From: James Morris <jmorris@namei.org>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: linux-security-module@vger.kernel.org, viro@zeniv.linux.org.uk
Subject: Re: [PATCH] tomoyo: Change pathname calculation for read-only filesystems.
Date: Thu, 28 Feb 2019 07:25:09 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.21.1902280724410.7990@namei.org> (raw)
In-Reply-To: <1551277164-8715-1-git-send-email-penguin-kernel@I-love.SAKURA.ne.jp>
On Wed, 27 Feb 2019, Tetsuo Handa wrote:
> Commit 5625f2e3266319fd ("TOMOYO: Change pathname for non-rename()able
> filesystems.") intended to be applied to filesystems where the content is
> not controllable from the userspace (e.g. proc, sysfs, securityfs), based
> on an assumption that such filesystems do not support rename() operation.
>
> But it turned out that read-only filesystems also do not support rename()
> operation despite the content is controllable from the userspace, and that
> commit is annoying TOMOYO users who want to use e.g. squashfs as the root
> filesystem due to use of local name which does not start with '/'.
>
> Therefore, based on an assumption that filesystems which require the
> device argument upon mount() request is an indication that the content
> is controllable from the userspace, do not use local name if a filesystem
> does not support rename() operation but requires the device argument upon
> mount() request.
I'd definitely like Al's input on this.
>
> Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> ---
> security/tomoyo/realpath.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/security/tomoyo/realpath.c b/security/tomoyo/realpath.c
> index 85e6e31..e7832448 100644
> --- a/security/tomoyo/realpath.c
> +++ b/security/tomoyo/realpath.c
> @@ -295,7 +295,8 @@ char *tomoyo_realpath_from_path(const struct path *path)
> * or dentry without vfsmount.
> */
> if (!path->mnt ||
> - (!inode->i_op->rename))
> + (!inode->i_op->rename &&
> + !(sb->s_type->fs_flags & FS_REQUIRES_DEV)))
> pos = tomoyo_get_local_path(path->dentry, buf,
> buf_len - 1);
> /* Get absolute name for the rest. */
>
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2019-02-27 20:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 14:19 [PATCH] tomoyo: Change pathname calculation for read-only filesystems Tetsuo Handa
2019-02-27 20:25 ` James Morris [this message]
2019-04-12 11:09 ` Tetsuo Handa
2019-04-29 20:07 ` James Morris
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.1902280724410.7990@namei.org \
--to=jmorris@namei.org \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=viro@zeniv.linux.org.uk \
/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