From: Steve Dickson <SteveD@RedHat.com>
To: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] mount: parse default values correctly
Date: Thu, 7 Jan 2021 11:03:06 -0500 [thread overview]
Message-ID: <3b8cecf2-3f15-a05d-13f0-2cc5b2d50c79@RedHat.com> (raw)
In-Reply-To: <20210106184028.150925-1-steved@redhat.com>
On 1/6/21 1:40 PM, Steve Dickson wrote:
> Commit 88c22f92 converted the configfile.c routines
> to use the parse_opt interfaces which broke how
> default values from nfsmount.conf are managed.
>
> Default values can not be added to the mount string
> handed to the kernel. They must be interpreted into
> the correct mount options then passed to the kernel.
>
> Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1912877
>
> Signed-off-by: Steve Dickson <steved@redhat.com>
Committed... (tag: nfs-utils-2-5-3-rc4)
steved.
> ---
> utils/mount/configfile.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/utils/mount/configfile.c b/utils/mount/configfile.c
> index 7934f4f..e865998 100644
> --- a/utils/mount/configfile.c
> +++ b/utils/mount/configfile.c
> @@ -277,8 +277,10 @@ conf_parse_mntopts(char *section, char *arg, struct mount_options *options)
> }
> if (buf[0] == '\0')
> continue;
> + if (default_value(buf))
> + continue;
> +
> po_append(options, buf);
> - default_value(buf);
> }
> conf_free_list(list);
> }
>
next prev parent reply other threads:[~2021-01-07 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 18:40 [PATCH] mount: parse default values correctly Steve Dickson
2021-01-07 16:03 ` Steve Dickson [this message]
2021-01-28 23:39 ` NeilBrown
2021-01-28 23:40 ` [PATCH nfs-utils] mount: fix parsing of default options NeilBrown
2021-02-01 5:00 ` [PATCH nfs-utils v2] " NeilBrown
2021-02-02 17:00 ` Steve Dickson
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=3b8cecf2-3f15-a05d-13f0-2cc5b2d50c79@RedHat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.org \
/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