From: "J. Bruce Fields" <bfields@fieldses.org>
To: Wendy Cheng <s.wendy.cheng@gmail.com>
Cc: Jongman Heo <jongman.heo@samsung.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: Re: Regression caused by commit 4bdc33ed ("NFSDv4.2: Add NFS v4.2 support to the NFS server")
Date: Tue, 1 Oct 2013 10:47:16 -0400 [thread overview]
Message-ID: <20131001144716.GK26382@fieldses.org> (raw)
In-Reply-To: <CABgxfbHyE04V_7YH2Zcqm+TAgCjT73kKWVGmKD30YxsriT+FMw@mail.gmail.com>
On Thu, Sep 26, 2013 at 11:35:46AM -0700, Wendy Cheng wrote:
> On Thu, Sep 26, 2013 at 10:47 AM, J. Bruce Fields <bfields@fieldses.org> wrote:
>
> > (BTW, out of curiosity: what kind of client is this that only supports
> > NFSv2 and NFSv3? Even for an embedded system that's a bit surprising.)
> >
>
> There are few floating around - at least I'm working on one at this moment.
>
> Look to me the upgrade issue is with user space packages (e.g. where
> "mount" lives). Embedded systems can take their user space packages
> from certain "distribution"s that are not necessarily sync well with
> individual linux upstream tool distribution, even the kernel itself is
> reasonably updated.
>
> And don't shoot a messenger :) .. I'm just describing the practices I
> have been observed.
OK. I'm not sure what standard to hold this sort of change to. I'm
inclined to use the same "it's OK if and only if nobody notices"
standard as for normal kernel interfaces. Which means we've already got
enough evidence to put off dropping NFSv2 support for a few more years,
at least on the server side....
--b.
next prev parent reply other threads:[~2013-10-01 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <42.19.15034.896B3425@epcpsbgx2.samsung.com>
2013-09-26 17:47 ` Re: Regression caused by commit 4bdc33ed ("NFSDv4.2: Add NFS v4.2 support to the NFS server") J. Bruce Fields
2013-09-26 18:35 ` Wendy Cheng
2013-10-01 14:47 ` J. Bruce Fields [this message]
2013-09-26 4:27 Jongman Heo
-- strict thread matches above, loose matches on Subject: below --
2013-09-26 4:22 Jongman Heo
2013-09-26 4:22 Jongman Heo
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=20131001144716.GK26382@fieldses.org \
--to=bfields@fieldses.org \
--cc=jongman.heo@samsung.com \
--cc=linux-nfs@vger.kernel.org \
--cc=s.wendy.cheng@gmail.com \
/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).