linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Steve Dickson <SteveD@redhat.com>
Cc: NeilBrown <neilb@suse.de>,
	Prem Karat <prem.karat@linux.vnet.ibm.com>,
	linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/1] nfs-utils: Don't hard code source and destination args
Date: Thu, 30 Jun 2011 13:40:05 -0400	[thread overview]
Message-ID: <20110630174005.GA18713@fieldses.org> (raw)
In-Reply-To: <4E0C5BB0.5030004@RedHat.com>

On Thu, Jun 30, 2011 at 07:19:12AM -0400, Steve Dickson wrote:
> 
> 
> On 06/30/2011 07:10 AM, NeilBrown wrote:
> > On Thu, 30 Jun 2011 06:58:04 -0400 Steve Dickson <SteveD@redhat.com> wrote:
> > 
> >>
> >>
> >> On 06/29/2011 07:09 PM, NeilBrown wrote:
> >>> On Wed, 29 Jun 2011 10:28:23 -0400 Steve Dickson <SteveD@redhat.com> wrote:
> >>>
> >>>>
> >>>>
> >>>> On 06/28/2011 06:41 AM, Prem Karat wrote:
> >>>>>
> >>>>> Currently souce and destination parameters should be passed as first and 
> >>>>> second paramter while using mount.nfs. This patch allows them to be passed 
> >>>>> anywhere while mounting.
> >>>>>
> >>>>> Current functionality is
> >>>>> 	mount.nfs source destn -o <options>
> >>>>> This patch will allow to do this
> >>>>> 	mount.nfs -o <options> source destn
> >>>>> 		or
> >>>>> 	mount.nfs -o <options> source -o <options> destn
> >>>>>
> >>>>> Signed-off-by: Prem Karat <prem.karat@linux.vnet.ibm.com>
> >>>> Committed...
> >>>
> >>> Uhmm... that's unfortunate because the patch is badly broken.
> >>>
> >>> With the patch in place, argv[2] gets destroyed.
> >>> i.e. mount cannot possibly work correctly now.
> >>>
> >>> And that is just the start of the problems.
> >>>
> >>> This patch has clearly never been tested.
> >> Hmm... well this is not true... I have 1.2.4 running
> >> on a number of machines and without a problem...
> > 
> > I'm guessing you used --enable-libmount-mount which causes the patched code
> > to not be compiled.  So while you did test nfs-utils, I don't think you
> > tested the patch :-(
> Thats exactly what happen... With your latest patch I never even compiled
> the code... darn!
> 
> hmm... I wonder if its time to throw the enable-libmount-mount-on-by-default 
> switch... 

Dumb question, as I haven't been following the libmount stuff, but: how
soon before we can throw out the non-libmount code?

Looks like patching and maintaining both is a pain.

Could we get away with saying "if you want a non-libmount-based mount,
feel free to go checkout 1.2.4 or earlier, and backport security fixes
to it yourself if you want", and just rip it out now?

--b.

  reply	other threads:[~2011-06-30 17:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-28 10:41 [PATCH 1/1] nfs-utils: Don't hard code source and destination args Prem Karat
2011-06-28 16:02 ` Chuck Lever
2011-06-28 16:59   ` Prem Karat
2011-06-28 17:29     ` Steve Dickson
2011-06-28 17:49     ` Chuck Lever
2011-06-28 17:59       ` Luk Claes
2011-06-28 18:33         ` Chuck Lever
2011-06-29 14:28 ` Steve Dickson
2011-06-29 23:09   ` NeilBrown
2011-06-30 10:58     ` Steve Dickson
2011-06-30 11:10       ` NeilBrown
2011-06-30 11:19         ` Steve Dickson
2011-06-30 17:40           ` J. Bruce Fields [this message]
2011-07-01 20:04             ` Steve Dickson
2011-07-01 20:56               ` J. Bruce Fields

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=20110630174005.GA18713@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=SteveD@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=prem.karat@linux.vnet.ibm.com \
    /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).