From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Jeff Layton <jlayton@redhat.com>
Cc: Staubach_Peter@emc.com, bfields@fieldses.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] sunrpc: split the vs_hidden flag into TCP and UDP variants
Date: Fri, 25 Jun 2010 10:37:42 -0400 [thread overview]
Message-ID: <1277476662.6141.0.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <20100625103503.011ae577-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
On Fri, 2010-06-25 at 10:35 -0400, Jeff Layton wrote:
> On Fri, 25 Jun 2010 09:14:10 -0400
> Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
>
> > On Fri, 2010-06-25 at 08:58 -0400, Staubach_Peter@emc.com wrote:
> > > Does this mean that the Linux NFS server will no longer respond to NFSv4
> > > requests coming in over UDP? If it will continue to do so, wouldn't it
> > > be more important to solve that correctly?
> >
> > Agreed. Either we keep UDP support on the server and advertise it too,
> > or we should throw it out altogether...
> >
>
> Ok, I'll start working on it. A question though...
>
> When we get a NFSv4 request over UDP, what's the correct response?
> A PROG_MISMATCH RPC error?
>
Yes. A PROG_MISMATCH would be appropriate for that case.
Cheers
Trond
next prev parent reply other threads:[~2010-06-25 14:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 1:33 [PATCH] sunrpc: split the vs_hidden flag into TCP and UDP variants Jeff Layton
2010-06-25 12:58 ` Staubach_Peter
[not found] ` <BF3BB6D12298F54B89C8DCC1E4073D800183CAB2-1Zg0zMUlrbd9m/dOYFj4Yjjd7nCn89gW@public.gmane.org>
2010-06-25 13:14 ` Trond Myklebust
[not found] ` <1277471650.2881.6.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2010-06-25 14:35 ` Jeff Layton
[not found] ` <20100625103503.011ae577-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-06-25 14:37 ` Trond Myklebust [this message]
2010-06-25 13:22 ` Jeff Layton
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=1277476662.6141.0.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=Staubach_Peter@emc.com \
--cc=bfields@fieldses.org \
--cc=jlayton@redhat.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;
as well as URLs for NNTP newsgroup(s).