Linux NFS development
 help / color / mirror / Atom feed
From: Ni Wenjuan <niwj@cn.fujitsu.com>
To: linux-nfs@vger.kernel.org
Subject: NFS4ERR_SYMLINK  error
Date: Thu, 05 Mar 2009 17:32:24 +0800	[thread overview]
Message-ID: <49AF9C28.8030603@cn.fujitsu.com> (raw)

the result of newpynfs test case of  LINK4a .  if you link with target directoty
 is a symbole file,it should get NFS4ERR_NOTDIR ,instead got NFS4ERR_SYMLINK.

THE LINK operation  don't list NFS4ERR_SYMLINK as valid errors in the spec. But
NFS4ERR_SYMLINK seems like a reasonable error.  Is this an oversight
in the spec, or something we need to fix?



             reply	other threads:[~2009-03-05  9:33 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-05  9:32 Ni Wenjuan [this message]
2009-03-05 10:09 ` NFS4ERR_SYMLINK error Benny Halevy
2009-03-06 21:32   ` J. Bruce Fields
2009-03-07 18:59     ` Benny Halevy
2009-03-09 18:06       ` J. Bruce Fields
2009-03-09 18:18         ` Trond Myklebust
2009-03-13  8:13         ` Yang Hongyang
2009-03-18 23:06           ` J. Bruce Fields
2009-03-19  6:51             ` [PATCH] NFSD: do not return nfserr_symlink for the LINK operation Benny Halevy
2009-03-19  6:59               ` Yang Hongyang
2009-03-19  7:04                 ` Benny Halevy
2009-03-19  8:18                   ` Yang Hongyang
2009-03-19  9:25                     ` Benny Halevy
2009-03-19  9:30                       ` Yang Hongyang
2009-03-19  9:53                         ` Benny Halevy
2009-03-19  9:34                       ` Yang Hongyang
2009-03-19 10:00                         ` Benny Halevy
2009-03-19  9:46                       ` Yang Hongyang
2009-03-19 20:00                         ` J. Bruce Fields
2009-03-19 20:15                           ` J. Bruce Fields
2009-03-20  6:16                             ` Yang Hongyang
2009-03-20  5:59                           ` Yang Hongyang
2009-03-20  7:05                           ` Yang Hongyang
2009-04-03  5:18                             ` Yang Hongyang

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=49AF9C28.8030603@cn.fujitsu.com \
    --to=niwj@cn.fujitsu.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