From: Frank Cusack <fcusack@fcusack.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: torvalds@transmeta.com, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] nfs_unlink() again, and trivial nfs_fhget
Date: Sat, 21 Jun 2003 18:56:23 -0700 [thread overview]
Message-ID: <20030621185623.C29657@google.com> (raw)
In-Reply-To: <20030621184623.A29657@google.com>; from fcusack@fcusack.com on Sat, Jun 21, 2003 at 06:46:23PM -0700
On Sat, Jun 21, 2003 at 06:46:23PM -0700, Frank Cusack wrote:
> It's to prevent RENAME of silly-renamed files. Doing so in VFS is a
> one-liner, and I agree that the VFS should be as clean as possible,
> but let's face it, the VFS *must* have specific fs knowledge. eg,
I hate to keep following up myself, but I forgot one point I had in
mind: other code in may_delete() is already fs-specific.
IS_APPEND
IS_IMMUTABLE
check_sticky
These things aren't generic, they require specific support from the fs.
/fc
next prev parent reply other threads:[~2003-06-22 1:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-17 12:14 [PATCH] nfs_unlink() again, and trivial nfs_fhget Frank Cusack
2003-06-17 18:41 ` Trond Myklebust
2003-06-17 23:55 ` Frank Cusack
2003-06-18 0:06 ` Frank Cusack
2003-06-18 23:40 ` Trond Myklebust
2003-06-22 1:46 ` Frank Cusack
2003-06-22 1:56 ` Frank Cusack [this message]
2003-06-22 7:29 ` 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=20030621185623.C29657@google.com \
--to=fcusack@fcusack.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=trond.myklebust@fys.uio.no \
/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