summaryrefslogtreecommitdiff
path: root/fs/fs_context.c
diff options
context:
space:
mode:
authorMiklos Szeredi <mszeredi@redhat.com>2020-05-14 17:44:25 +0300
committerMiklos Szeredi <mszeredi@redhat.com>2020-05-14 17:44:25 +0300
commitcaaef1ba8c9ee7a54b53dd8bf4bb7e8658185583 (patch)
tree1e103d74e1178ef174c0b3ae800f9103e3ad2598 /fs/fs_context.c
parent9193ae87a8af031ce2fb4116d417fff55c8a0bcc (diff)
downloadlinux-caaef1ba8c9ee7a54b53dd8bf4bb7e8658185583.tar.xz
vfs: don't parse "posixacl" option
Unlike the others, this is _not_ a standard option accepted by mount(8). In fact SB_POSIXACL is an internal flag, and accepting MS_POSIXACL on the mount(2) interface is possibly a bug. The only filesystem that apparently wants to handle the "posixacl" option is 9p, but it has special handling of that option besides setting SB_POSIXACL. Signed-off-by: Miklos Szeredi <mszeredi@redhat.com> Reviewed-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'fs/fs_context.c')
-rw-r--r--fs/fs_context.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/fs/fs_context.c b/fs/fs_context.c
index 07e09bcf256c..82019569d493 100644
--- a/fs/fs_context.c
+++ b/fs/fs_context.c
@@ -42,7 +42,6 @@ static const struct constant_table common_set_sb_flag[] = {
{ "dirsync", SB_DIRSYNC },
{ "lazytime", SB_LAZYTIME },
{ "mand", SB_MANDLOCK },
- { "posixacl", SB_POSIXACL },
{ "ro", SB_RDONLY },
{ "sync", SB_SYNCHRONOUS },
{ },