From: Jeff Garzik <jeff@garzik.org>
To: linux-nfs@vger.kernel.org
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: NFS4ERR_DENIED becomes EIO?
Date: Wed, 18 Feb 2009 16:19:15 -0500 [thread overview]
Message-ID: <499C7B53.5030802@garzik.org> (raw)
I think I may have found a tiny NFSv4 client bug. What I am seeing:
1. On Linux NFS client (2.6.29-rc2), issue chown(1) to change the owner
of the file (causing SETATTR:OWNER to be issued)
2. My userland NFS server returns NFS4ERR_DENIED for the SETATTR op
3. Linux NFS client returns EIO (I/O error) to userland
That was a bit unexpected. I would have guessed EPERM, perhaps.
Jeff
next reply other threads:[~2009-02-18 21:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 21:19 Jeff Garzik [this message]
2009-02-18 21:59 ` NFS4ERR_DENIED becomes EIO? Trond Myklebust
[not found] ` <1234994399.8412.206.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-02-19 1:22 ` Jeff Garzik
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=499C7B53.5030802@garzik.org \
--to=jeff@garzik.org \
--cc=linux-fsdevel@vger.kernel.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