From: "J. Bruce Fields" <bfields@fieldses.org>
To: linux-nfs@vger.kernel.org
Subject: server 4.1 issues list
Date: Thu, 7 Oct 2010 11:53:06 -0400 [thread overview]
Message-ID: <20101007155306.GA28053@fieldses.org> (raw)
Based on conversation at the bakeathon yesterday, I've updated
http://wiki.linux-nfs.org/wiki/index.php/Server_4.0_and_4.1_issues
Changes:
- Mark deferral fixes done.
- Update in-progress status at
http://wiki.linux-nfs.org/wiki/index.php/Server_4.0_and_4.1_issues#4.1
- Add callback error handling.
- Various minor clarifications.
Some sort of difficulty or time-required rating was also requested, but
I haven't attempted that.
Someone asked whether we error out as we should on
mandatory-not-to-implement 4.1 operations; from a quick check of the
code it appears that we do, so I haven't added that.
Someone also asked whether we've fixed the backchannel attribute
checking. We haven't, but that should be fairly quick--I'll take a look
at it now.
--b.
next reply other threads:[~2010-10-07 15:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 15:53 J. Bruce Fields [this message]
2010-10-07 17:54 ` server 4.1 issues list J. Bruce Fields
2010-10-07 18:10 ` Benny Halevy
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=20101007155306.GA28053@fieldses.org \
--to=bfields@fieldses.org \
--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