linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Gregory Boyce <gregory.boyce@gmail.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] nfs-utils: Allow users to disable mount option rewriting via norewriteopts mount option
Date: Thu, 07 May 2015 09:48:15 -0400	[thread overview]
Message-ID: <554B6D1F.2040207@RedHat.com> (raw)
In-Reply-To: <CALs61uevioa8FgEbCuTO2JA+74mnH_PCAPUzpLfSzGJ-68729w@mail.gmail.com>



On 05/06/2015 04:28 PM, Gregory Boyce wrote:
> On Wed, May 6, 2015 at 4:14 PM, Steve Dickson <SteveD@redhat.com> wrote:
>>
>>
>> On 04/20/2015 02:18 PM, Gregory Boyce wrote:
>>> Allow users to disable mount option rewriting via norewriteopts mount option.
>>> This was required in our case in order to allow mounting a filer which inappropriately responded via the wrong interface.
>>>
>>> Signed-off-by: Gregory Boyce <gregory.boyce@gmail.com>
>> Again... This is fixing a filer bug, correct?
>>
>> We generally don't do that...
>>
>> steved.
> 
> This is working around a server bug on the client side, yes.
> 
That's tough... We generally don't do that because its becomes
a very slippy slope very quickly.... esp with adding a undocumented
mount flag we are going have to support forever...

This is something I just don't think is the right thing to do
so I'm going to NAK this patch. 

steved.


 

      reply	other threads:[~2015-05-07 13:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20 18:18 [PATCH] nfs-utils: Allow users to disable mount option rewriting via norewriteopts mount option Gregory Boyce
2015-05-06 20:14 ` Steve Dickson
2015-05-06 20:28   ` Gregory Boyce
2015-05-07 13:48     ` Steve Dickson [this message]

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=554B6D1F.2040207@RedHat.com \
    --to=steved@redhat.com \
    --cc=gregory.boyce@gmail.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;
as well as URLs for NNTP newsgroup(s).