diff options
author | Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> | 2019-02-27 23:19:24 +0900 |
---|---|---|
committer | James Morris <jamorris@linux.microsoft.com> | 2019-05-10 14:58:30 -0700 |
commit | 27df4b4a1b5fe2bef54ebc49d64bf5b39125f26a (patch) | |
tree | ad953659dd61c1baaeb6815e18c98a0e00893781 /security/tomoyo/Kconfig | |
parent | e6193f78bb689f3f424559bb45f4a091c8b314df (diff) | |
download | linux-27df4b4a1b5fe2bef54ebc49d64bf5b39125f26a.tar.bz2 |
tomoyo: Change pathname calculation for read-only filesystems.
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.
Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Signed-off-by: James Morris <jamorris@linux.microsoft.com>
Diffstat (limited to 'security/tomoyo/Kconfig')
0 files changed, 0 insertions, 0 deletions