From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: neilb@suse.de, linux-nfs@vger.kernel.org,
Trond Myklebust <Trond.Myklebust@netapp.com>
Subject: Re: [PATCH] NFS: Restore missing hunk in NFS mount option parser
Date: Fri, 5 Sep 2008 17:11:10 -0400 [thread overview]
Message-ID: <20080905211110.GE12947@fieldses.org> (raw)
In-Reply-To: <20080905181339.17103.36231.stgit-07a7zB5ZJzbwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
On Fri, Sep 05, 2008 at 02:16:07PM -0400, Chuck Lever wrote:
> Commit f45663ce5fb30f76a3414ab3ac69f4dd320e760a was missing a hunk that
> prevented the new "sloppy" mount option from having any effect.
I don't think that on its own would justify sending it in for 2.6.27.[1]
>
> Tested against 2.6.27-rc. 2.6.26 is not affected.
But if I understand right, the effect of leaving out this chunk was to
make the *default* behavior "sloppy"? Which seems a drastic change from
the previous behavior. And it's a simple enough patch.
So I'd be inclined to agree and send it in for 2.6.27.... If Trond
doesn't poke his head up by tomorrow, let's go ahead--feel free to send
it to Linus with my
Acked-by: J. Bruce Fields <bfields@citi.umich.edu>
if I fall off the face of the earth tomorrow.
--b.
[1] Linus has been pretty hard on -rc patches lately:
http://marc.info/?l=linux-netdev&m=122048427801318&w=2
"Here's a simple rule of thumb:
- if it's not on the regression list
- if it's not a reported security hole
- if it's not on the reported oopses list
then why are people sending it to me?"
>
> Thanks to Neil Brown for reporting this.
>
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
>
> fs/nfs/super.c | 6 ++++++
> 1 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/fs/nfs/super.c b/fs/nfs/super.c
> index 5b2aa04..e3ac650 100644
> --- a/fs/nfs/super.c
> +++ b/fs/nfs/super.c
> @@ -1279,6 +1279,12 @@ static int nfs_parse_mount_options(char *raw,
> }
> }
>
> + if (errors > 0) {
> + dfprintk(MOUNT, "NFS: parsing encountered %d error%s\n",
> + errors, (errors == 1 ? "" : "s"));
> + if (!sloppy)
> + return 0;
> + }
> return 1;
>
> out_nomem:
>
next prev parent reply other threads:[~2008-09-05 21:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 18:16 [PATCH] NFS: Restore missing hunk in NFS mount option parser Chuck Lever
[not found] ` <20080905181339.17103.36231.stgit-07a7zB5ZJzbwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2008-09-05 21:11 ` J. Bruce Fields [this message]
2008-09-05 21:25 ` Chuck Lever
[not found] ` <76bd70e30809051425y21d1ce1kb06c8d72a83bdb4e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-09-05 21:34 ` J. Bruce Fields
2008-09-05 21:44 ` Chuck Lever
-- strict thread matches above, loose matches on Subject: below --
2008-09-05 22:51 Chuck Lever
2008-09-08 15:58 Chuck Lever
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=20080905211110.GE12947@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.