From: Christoph Hellwig <hch@infradead.org>
To: linux-nfs@vger.kernel.org
Subject: NFSv2/3 vs v4 error codes?
Date: Wed, 10 Sep 2014 15:16:50 -0700 [thread overview]
Message-ID: <20140910221650.GD29452@infradead.org> (raw)
As a followup to the fallocate discussion I checked what we map ENODEV
to in nfsd. Turns out we map it to NFSERR_NODEV, which doesn't exist
in eiter NFSv4.0 nor NFSv4.1 despite the comment in
include/uapi/linux/nfs.h claiming otherwise. I also just ran into
another issue where nfserrno translates a large lits of errors into
NFSERR_JUKEBOX, but for v4 we'd really want NFSERR_DELAY instead for
most of them.
Is it time for a version specific errno mapping?
next reply other threads:[~2014-09-10 22:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 22:16 Christoph Hellwig [this message]
2014-09-11 19:03 ` NFSv2/3 vs v4 error codes? J. Bruce Fields
2014-09-11 20:02 ` Christoph Hellwig
2014-09-12 17:55 ` J. Bruce Fields
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=20140910221650.GD29452@infradead.org \
--to=hch@infradead.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;
as well as URLs for NNTP newsgroup(s).