public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Aaron D. Ball" <adb@bdi.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Vladimir Saveliev <vs@namesys.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: knfsd and append-only attribute:  "operation not permitted"
Date: Fri, 21 Jan 2005 11:23:17 -0500	[thread overview]
Message-ID: <41F12C75.5040007@bdi.com> (raw)
In-Reply-To: <1106322787.30627.5.camel@lade.trondhjem.org>

Trond Myklebust wrote:

>fr den 21.01.2005 Klokka 17:44 (+0300) skreiv Vladimir Saveliev:
>  
>
>> fs/nfsd/vfs.c:nfsd_open() refuses to open append only files.
>
>
>Append-only is an unsupported concept in the all existing revisions of
>the NFS protocol. In fact, NFS has no support for append writes at all:
>they have to be emulated by the clients.
>  
>
OK, but that certainly shouldn't preclude read access.  The way it is 
now, you can't even list append-only directories.  It seems like this 
check should treat append-only files as read-only, only failing to open 
them if write access is requested, rather than failing all the time like 
it does now.

In this particular case, I'm not using append-only files, but rather 
using immutable files and append-only directories to create an archival 
space where things can be added but not changed.  Even if the protocol 
can't deal with append-only regular files, isn't it possible to allow 
mkdir but not rmdir?


  reply	other threads:[~2005-01-21 16:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8381054C-6B13-11D9-BFA6-000D933B35AA@bdi.com>
2005-01-21 14:44 ` knfsd and append-only attribute: "operation not permitted" Vladimir Saveliev
2005-01-21 15:53   ` Trond Myklebust
2005-01-21 16:23     ` Aaron D. Ball [this message]
2005-01-21 17:08       ` Trond Myklebust

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=41F12C75.5040007@bdi.com \
    --to=adb@bdi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    --cc=vs@namesys.com \
    /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