Linux NFS development
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: "Chuck Lever" <chucklever@gmail.com>,
	"Steve Dickson" <SteveD@redhat.com>,
	linux-nfs@vger.kernel.org
Subject: Re: [PATCH] mount: enable retry for nfs23 to set the correct protocol for mount.
Date: Mon, 21 Jul 2008 12:55:59 +1000	[thread overview]
Message-ID: <18563.64191.468427.481673@notabene.brown> (raw)
In-Reply-To: message from Neil Brown on Monday July 21

On Monday July 21, neilb@suse.de wrote:
> 
> How about this?

BTW, this and two other patches are in my git.

The first is the sm-notify fix, as modified, and with another fix
since Steve's last post.  There was a "return" which should have been
inside and 'if' but was outside it.

The second causes portmap lookup to use connected UDP ports.

The third is the one I just posted.

BTW Steve, it is a small thing, but when you apply patches to git you
often seem to lose the subject line.  This causes the first line of
the description to be using as the one line summary, which sometimes
looks rather strange.

Thanks,
NeilBrown

The following changes since commit ba8dd9533e647b70d6e46beed3dcd8d8036b02af:
  Neil Brown (1):
        If portmap is not listening on UDP (as apparently happens with

are available in the git repository at:

  git://neil.brown.name/nfs-utils/ for-steved

Neil Brown (3):
      sm-notify: perform DNS lookup in the background.
      Use connected socket when probing portmap with UDP.
      Check nfs options (vers/protocol) before trying mount.

 utils/mount/network.c   |   41 +++++++++++++++++++++++++----------------
 utils/mount/network.h   |    2 +-
 utils/mount/nfsmount.c  |    2 +-
 utils/mount/stropts.c   |   18 +++++++-----------
 utils/statd/sm-notify.c |   39 +++++++++++++++++++++++++--------------
 5 files changed, 59 insertions(+), 43 deletions(-)

  reply	other threads:[~2008-07-21  2:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15 12:56 [PATCH] mount: enable retry for nfs23 to set the correct protocol for mount Neil Brown
     [not found] ` <18556.40594.897682.204554-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-07-15 15:11   ` Chuck Lever
     [not found]     ` <76bd70e30807150811p56feb02bo6e4a366d5577b398-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-16 17:12       ` Steve Dickson
2008-07-17  2:25         ` Neil Brown
     [not found]           ` <18558.44430.959865.662592-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-07-17 10:38             ` Steve Dickson
2008-07-17 22:50               ` Neil Brown
2008-07-17 23:15     ` Neil Brown
2008-07-18  0:12       ` Neil Brown
     [not found]         ` <18559.57353.428342.328105-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-07-18  4:54           ` Chuck Lever
2008-08-28 15:35           ` Steve Dickson
     [not found]       ` <18559.53893.95829.499988-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-07-19 16:09         ` Chuck Lever
2008-07-20  6:48           ` Neil Brown
     [not found]             ` <18562.57287.656749.540603-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-07-21  1:28               ` Chuck Lever
2008-07-21  2:49                 ` Neil Brown
2008-07-21  2:55                   ` Neil Brown [this message]
     [not found]                     ` <18563.64191.468427.481673-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-07-21 20:59                       ` Chuck Lever
     [not found]                   ` <18563.63821.501053.402741-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-07-21  4:43                     ` Chuck Lever
2008-07-21  6:06                       ` Neil Brown
     [not found]                         ` <18564.10115.809293.243948-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-07-21 15:32                           ` Chuck Lever
     [not found]                             ` <76bd70e30807210832l188bd3adl92762d5856bbaa5e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-21 17:40                               ` Trond Myklebust
2008-07-21 19:01                                 ` Chuck Lever
2008-07-21 17:23                           ` 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=18563.64191.468427.481673@notabene.brown \
    --to=neilb@suse.de \
    --cc=SteveD@redhat.com \
    --cc=chucklever@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