mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@gmail.com>
To: Neil Brown <neilb@suse.de>
Cc: linux-kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: "svc: unknown version (3)" when CONFIG_NFSD_V4=y
Date: Wed, 10 Jan 2007 22:17:56 +0800	[thread overview]
Message-ID: <368438638.13038@ustc.edu.cn> (raw)
Message-ID: <20070110141756.GA5572@mail.ustc.edu.cn> (raw)
In-Reply-To: <17828.33075.145986.404400@notabene.brown>

On Wed, Jan 10, 2007 at 05:01:23PM +1100, Neil Brown wrote:
> On Friday January 5, fengguang.wu@gmail.com wrote:
> > Hi Neil,
> > 
> > NFS mounting succeeded, but the kernel gives a warning.
> > I'm running 2.6.20-rc2-mm1.
> > 
> > # mount -o vers=3 localhost:/suse /mnt
> > [  689.651606] svc: unknown version (3)
> > # mount | grep suse
> > localhost:/suse on /mnt type nfs (rw,nfsvers=3,addr=127.0.0.1)
> > 
> > Any clues about it?
> 
> Weird.
> 
> Please try this patch.  It should provide more useful information.
> 
> NeilBrown
> 
> Signed-off-by: Neil Brown <neilb@suse.de>
> 
> ### Diffstat output
>  ./net/sunrpc/svc.c |    3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff .prev/net/sunrpc/svc.c ./net/sunrpc/svc.c
> --- .prev/net/sunrpc/svc.c	2007-01-10 16:58:14.000000000 +1100
> +++ ./net/sunrpc/svc.c	2007-01-10 16:59:55.000000000 +1100
> @@ -910,7 +910,8 @@ err_bad_prog:
>  
>  err_bad_vers:
>  #ifdef RPC_PARANOIA
> -	printk("svc: unknown version (%d)\n", vers);
> +	printk("svc: unknown version (%d for prog %d, %s)\n", 
> +	       vers, prog, progp->pg_name);
>  #endif
>  	serv->sv_stats->rpcbadfmt++;
>  	svc_putnl(resv, RPC_PROG_MISMATCH);

root ~# mount localhost:/suse /mnt
[  132.678204] svc: unknown version (3 for prog 100227, nfsd)

I've confirmed that 2.6.20-rc2-mm1, 2.6.20-rc3-mm1, 2.6.19-rc6-mm1 all
have this warning, while 2.6.17-2-amd64 is good.

Thanks,
Wu

  reply	other threads:[~2007-01-10 14:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070105024226.GA6076@mail.ustc.edu.cn>
2007-01-05  2:42 ` Fengguang Wu
2007-01-05 12:25 ` Trond Myklebust
     [not found]   ` <20070105124822.GA7901@mail.ustc.edu.cn>
2007-01-05 12:48     ` Fengguang Wu
2007-01-10  6:01 ` Neil Brown
     [not found]   ` <20070110141756.GA5572@mail.ustc.edu.cn>
2007-01-10 14:17     ` Fengguang Wu [this message]
2007-01-10 15:15       ` Arnaud Giersch
2007-01-11  3:59     ` Neil Brown
     [not found]       ` <20070111145309.GA6226@mail.ustc.edu.cn>
2007-01-11 14:53         ` Fengguang Wu
2007-01-11 22:04         ` Neil Brown
     [not found]           ` <20070112023251.GA6136@mail.ustc.edu.cn>
2007-01-12  2:32             ` Fengguang Wu
2007-01-12 19:43             ` Neil Brown
     [not found]               ` <20070113021320.GA6055@mail.ustc.edu.cn>
2007-01-13  2:13                 ` Fengguang Wu
2007-01-14 22:32                 ` Neil Brown

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=368438638.13038@ustc.edu.cn \
    --to=fengguang.wu@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    /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

Powered by JetHome