From: "roucaries bastien" <roucaries.bastien@gmail.com>
To: 7eggert@gmx.de
Cc: "Pekka J Enberg" <penberg@cs.helsinki.fi>,
alan@lxorguk.ukuu.org.uk, tytso@mit.edu,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC/PATCH] revoke/frevoke system calls
Date: Thu, 20 Jul 2006 23:01:34 +0000 [thread overview]
Message-ID: <195c7a900607201601m58d078pee808089b8e6b47d@mail.gmail.com> (raw)
In-Reply-To: <E1G3g2H-0001W7-LB@be1.lrz>
On 7/20/06, Bodo Eggert <7eggert@elstempel.de> wrote:
> Pekka J Enberg <penberg@cs.Helsinki.FI> wrote:
> > From: Pekka Enberg <penberg@cs.helsinki.fi>
>
> > This patch implements the revoke(2) and frevoke(2) system calls for all
> > types of files. We revoke files in two passes: first we scan all open
> > files that refer to the inode and substitute the struct file pointer in fd
> > table with NULL causing all subsequent operations on that fd to fail.
> > After we have done that to all file descriptors, we close the files and
> > take down mmaps.
>
> RFC2: Make umount -f work on local fs using this feature.
RFC3: use preliminary work about umount -f in order to get revoke for free.
See for instance
http://developer.osdl.org/dev/fumount/kernel2/patches/2.6.12/1/forced-unmount-2.6.12-1.patch
next prev parent reply other threads:[~2006-07-20 23:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6AFvY-7ZK-15@gated-at.bofh.it>
2006-07-20 21:26 ` [RFC/PATCH] revoke/frevoke system calls Bodo Eggert
2006-07-20 23:01 ` roucaries bastien [this message]
2006-07-22 8:05 Albert Cahalan
2006-08-07 10:45 ` Pekka Enberg
2006-08-07 15:19 ` Albert Cahalan
-- strict thread matches above, loose matches on Subject: below --
2006-07-20 12:07 Pekka J Enberg
2006-07-20 20:02 ` Kari Hurtta
2006-07-20 21:09 ` Björn Steinbrink
2006-07-21 22:16 ` Edgar Toernig
2006-07-22 0:19 ` Andrew Morton
2006-07-22 6:22 ` Pekka J Enberg
2006-07-22 6:59 ` Andrew Morton
2006-07-22 7:41 ` Pekka Enberg
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=195c7a900607201601m58d078pee808089b8e6b47d@mail.gmail.com \
--to=roucaries.bastien@gmail.com \
--cc=7eggert@gmx.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).