From: Neil Brown <neilb@suse.de>
To: Steve Dickson <SteveD@redhat.com>
Cc: Chuck Lever <chuck.lever@oracle.com>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] umount: fix problems when portmap doesn't listen on UDP.
Date: Thu, 17 Jul 2008 12:44:42 +1000 [thread overview]
Message-ID: <18558.45595.59801.775326@notabene.brown> (raw)
In-Reply-To: message from Steve Dickson on Wednesday July 16
On Wednesday July 16, SteveD@redhat.com wrote:
>
>
> Neil Brown wrote:
> > Another patch that can be pulled from
> > git://neil.brown.name/nfs-utils for-steved
> >
> > This and the next deal with problems with the new 'string based
> > option' code when portmap can only be contacted via TCP.
> >
> > Some people seem to turn of string based options to avoid this
> > problem:
> > https://bugs.launchpad.net/ubuntu/+bug/213444/comments/23
> >
> > This can partly be avoided using mountproto=tcp, but that
> > a/ shouldn't be needed (isn't with the old code)
> > b/ doesn't help the unmount case.
> >
> > This first patch make umount work better if mountproto=tcp was given
> > to mount.
> > The next patch gives mountproto=tcp to mount if it is needed.
> Committed
>
> steved.
Thanks!
Do you have plans for a 1.1.3?
15th of September would be 6 months since 1.1.2 :-)
NeilBrown
next prev parent reply other threads:[~2008-07-17 2:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 12:52 [PATCH] umount: fix problems when portmap doesn't listen on UDP Neil Brown
[not found] ` <18556.40326.764642.102066-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-07-15 15:42 ` Chuck Lever
2008-07-16 18:49 ` Steve Dickson
2008-07-17 2:44 ` Neil Brown [this message]
[not found] ` <18558.45595.59801.775326-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-07-17 10:18 ` 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=18558.45595.59801.775326@notabene.brown \
--to=neilb@suse.de \
--cc=SteveD@redhat.com \
--cc=chuck.lever@oracle.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