All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Staubach <staubach@redhat.com>
To: Olaf Kirch <okir@suse.de>
Cc: nfs@lists.sourceforge.net
Subject: Re: [PATCH nfsd] ignore chmod calls on symlinks
Date: Mon, 11 Jul 2005 09:05:58 -0400	[thread overview]
Message-ID: <42D26EB6.3090301@redhat.com> (raw)
In-Reply-To: <20050711125918.GT27163@suse.de>

Olaf Kirch wrote:

>On Mon, Jul 11, 2005 at 08:46:55AM -0400, Peter Staubach wrote:
>  
>
>>>I submitted this before - this is a somewhat cosmetic fix to
>>>keep the SpecFS validation test from complaining.
>>>
>>>      
>>>
>>It seems to me that this test could/should considered to be broken and 
>>hence,
>>fixed, as opposed to cluttering up file system dependent code with checks
>>like this that the upper layers are responsible for catching.
>>    
>>
>
>An NFS client is allowed to send a chmod on a symlink. It just happens
>to be an illegal operation on most file systems.
>

So, the nfsd layer is not doing what the vfs layer on the system is already
for callers into the file systems?

    Thanx...

       ps


-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP, 
AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2005-07-11 13:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-11 11:06 [PATCH nfsd] ignore chmod calls on symlinks Olaf Kirch
2005-07-11 12:46 ` Peter Staubach
2005-07-11 12:59   ` Olaf Kirch
2005-07-11 13:05     ` Peter Staubach [this message]
2005-07-12  8:52       ` Olaf Kirch

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=42D26EB6.3090301@redhat.com \
    --to=staubach@redhat.com \
    --cc=nfs@lists.sourceforge.net \
    --cc=okir@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.