linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: chucklever@gmail.com
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	"Randy.Dunlap" <rdunlap@xenotime.net>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	kernel-testers@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: inux-next: Tree for July 1
Date: Wed, 02 Jul 2008 13:15:11 -0400	[thread overview]
Message-ID: <1215018911.9783.1.camel@localhost> (raw)
In-Reply-To: <76bd70e30807020734g3db408dcqea2a61622c83004d@mail.gmail.com>

On Wed, 2008-07-02 at 10:34 -0400, Chuck Lever wrote:
> On Tue, Jul 1, 2008 at 8:49 PM, Trond Myklebust
> <Trond.Myklebust@netapp.com> wrote:
> > On Tue, 2008-07-01 at 22:36 +0200, Rafael J. Wysocki wrote:
> >> I can't mount NFS shares with this kernel.  I get something of this sort in
> >> dmesg and it seems to be 100% reproducible:
> >>
> >> [  314.058858] RPC: Registered udp transport module.
> >> [  314.058863] RPC: Registered tcp transport module.
> >> [  314.490970] RPC: transport (0) not supported
> >> [  319.246987] __ratelimit: 23 messages suppressed
> >
> > Does this patch fix the problem for you?
> > -----------------------------------------------------------------------------------
> > From: Trond Myklebust <Trond.Myklebust@netapp.com>
> > NFS: Fix the mount protocol defaults for binary mounts
> >
> > Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
> > ---
> >
> >  fs/nfs/super.c |    1 +
> >  1 files changed, 1 insertions(+), 0 deletions(-)
> >
> > diff --git a/fs/nfs/super.c b/fs/nfs/super.c
> > index e09b1c2..85fbb98 100644
> > --- a/fs/nfs/super.c
> > +++ b/fs/nfs/super.c
> > @@ -1575,6 +1575,7 @@ static int nfs_validate_mount_data(void *options,
> >
> >                if (!(data->flags & NFS_MOUNT_TCP))
> >                        args->nfs_server.protocol = XPRT_TRANSPORT_UDP;
> > +               nfs_set_transport_defaults(args);
> 
> nfs_set_transport_defaults() is overkill for the legacy mount path.
> The bug is that the logic here assumes that nfs_server.protocol
> already has the default value of XPRT_TRANSPORT_TCP, but commit
> 8b59ea3c removed that default.  The correct fix is to add
> 
>             args->nfs_server.protocol = XPRT_TRANSPORT_TCP;
> 
> just before the 'if' statement.  We should fold that into 8b59ea3c to
> preserve bisectability.

NACK. You still need to set the appropriate retrans and timeo defaults.

-- 
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust@netapp.com
www.netapp.com

  parent reply	other threads:[~2008-07-02 17:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01 15:14 inux-next: Tree for July 1 Stephen Rothwell
2008-07-01 20:36 ` Rafael J. Wysocki
     [not found]   ` <200807012236.19400.rjw-KKrjLPT3xs0@public.gmane.org>
2008-07-01 20:41     ` Randy.Dunlap
2008-07-01 20:49     ` Chuck Lever
2008-07-01 21:05       ` Rafael J. Wysocki
2008-07-02  0:49   ` Trond Myklebust
2008-07-02  3:32     ` Randy Dunlap
2008-07-02 10:51       ` Rafael J. Wysocki
     [not found]     ` <76bd70e30807020734g3db408dcqea2a61622c83004d@mail.gmail.com>
2008-07-02 17:15       ` Trond Myklebust [this message]
     [not found]         ` <76bd70e30807021043x72f3aa46o8d07f2039d2ed455@mail.gmail.com>
     [not found]           ` <76bd70e30807021043x72f3aa46o8d07f2039d2ed455-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-02 19:02             ` Trond Myklebust
2008-07-02 23:14               ` Chuck Lever
2008-07-02  3:11 ` inux-next 0701 mv643xx_eth powerpc build failure Joseph Fannin
2008-07-02  4:10   ` Stephen Rothwell
2008-07-02  8:21   ` Lennert Buytenhek
2008-07-03 12:38     ` Joseph Fannin
2008-07-02  3:15 ` inux-next: Tree for July 1 Randy Dunlap
2008-07-02  3:27   ` Stephen Rothwell
2008-07-03  4:53 ` Andrew Morton
2008-07-03  4:58   ` Andrew Morton
2008-07-03  5:11     ` Andrew Morton
2008-07-03 15:36       ` Heiko Carstens

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=1215018911.9783.1.camel@localhost \
    --to=trond.myklebust@netapp.com \
    --cc=chucklever@gmail.com \
    --cc=kernel-testers@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=rjw@sisk.pl \
    --cc=sfr@canb.auug.org.au \
    /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).