Re: [PATCH 05/13] vfs: don't parse "silent" option
From: Ian Kent <raven@themaw.net>
Date: 2019-06-20 04:40:36
Also in:
linux-fsdevel, lkml
On Wed, 2019-06-19 at 14:30 +0200, Miklos Szeredi wrote:
While this is a standard option as documented in mount(8), it is ignored by most filesystems. So reject, unless filesystem explicitly wants to handle it. The exception is unconverted filesystems, where it is unknown if the filesystem handles this or not. Any implementation, such as mount(8) that needs to parse this option without failing should simply ignore the return value from fsconfig().
In theory this is fine but every time someone has attempted to change the handling of this in the past autofs has had problems so I'm a bit wary of the change. It was originally meant to tell the file system to ignore invalid options such as could be found in automount maps that are used with multiple OS implementations that have differences in their options. That was, IIRC, primarily NFS although NFS should handle most (if not all of those) cases these days. Nevertheless I'm a bit nervous about it, ;)
quoted hunk ↗ jump to hunk
Signed-off-by: Miklos Szeredi <redacted> --- fs/fs_context.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)diff --git a/fs/fs_context.c b/fs/fs_context.c index 49636e541293..c26b353aa858 100644 --- a/fs/fs_context.c +++ b/fs/fs_context.c@@ -51,7 +51,6 @@ static const struct constant_table common_clear_sb_flag[] ={ { "nolazytime", SB_LAZYTIME }, { "nomand", SB_MANDLOCK }, { "rw", SB_RDONLY }, - { "silent", SB_SILENT }, }; /*@@ -535,6 +534,9 @@ static int legacy_parse_param(struct fs_context *fc,struct fs_parameter *param) if (ret != -ENOPARAM) return ret; + if (strcmp(param->key, "silent") == 0) + fc->sb_flags |= SB_SILENT; + if (strcmp(param->key, "source") == 0) { if (param->type != fs_value_is_string) return invalf(fc, "VFS: Legacy: Non-string source");