Linux NFS development
 help / color / mirror / Atom feed
From: "Aaron D. Ball" <adb@bdi.com>
To: nfs@lists.sourceforge.net
Subject: append-only attribute support
Date: Fri, 21 Jan 2005 12:56:15 -0500	[thread overview]
Message-ID: <41F1423F.3080800@bdi.com> (raw)
In-Reply-To: <1106327280.9849.32.camel@lade.trondhjem.org>

knfsd as of Linux 2.6.10 refuses to have anything to do with files or 
directories with the append-only attribute set:  not even read 
operations are allowed.  While I understand that NFS doesn't support the 
idea of appending to files, it seems like there should at least be read 
and mkdir support for append-only files and directories, and that this 
could be implemented with a couple small changes to the logic of 
fs/nfsd/vfs.c.

Does that seem reasonable?  Is it likely to happen soon?  Should I try 
to work up a patch?

Though I haven't tested this, it looks like a one-line fix at first glance:

--- vfs.c~      2004-12-24 16:34:31.000000000 -0500
+++ vfs.c       2005-01-21 12:52:14.000000000 -0500
@@ -658,7 +658,7 @@
         * with mandatory locking enabled
         */
        err = nfserr_perm;
-       if (IS_APPEND(inode) || IS_ISMNDLK(inode))
+       if ((IS_APPEND(inode) || (access & MAY_WRITE)) || 
IS_ISMNDLK(inode))
                goto out;
        if (!inode->i_fop)
                goto out;



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

       reply	other threads:[~2005-01-21 17:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8381054C-6B13-11D9-BFA6-000D933B35AA@bdi.com>
     [not found] ` <1106318654.3200.38.camel@tribesman.namesys.com>
     [not found]   ` <1106322787.30627.5.camel@lade.trondhjem.org>
     [not found]     ` <41F12C75.5040007@bdi.com>
     [not found]       ` <1106327280.9849.32.camel@lade.trondhjem.org>
2005-01-21 17:56         ` Aaron D. Ball [this message]
2005-01-21 18:02           ` append-only attribute support Trond Myklebust
2005-01-21 18:12             ` Aaron D. Ball
2005-01-24  4:27               ` Neil Brown

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=41F1423F.3080800@bdi.com \
    --to=adb@bdi.com \
    --cc=nfs@lists.sourceforge.net \
    /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