From: Nikolai Joukov <kolya@cs.sunysb.edu>
To: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
Cc: Harry Papaxenopoulos <harry@cs.sunysb.edu>,
linux-ext4@vger.kernel.org, ezk@cs.sunysb.edu
Subject: Re: [Resubmit][PATCH 5/5] Secure Deletion and Trash-Bin Support for Ext4
Date: Thu, 1 Feb 2007 12:17:58 -0500 (EST) [thread overview]
Message-ID: <Pine.GSO.4.53.0702011200340.9072@compserv1> (raw)
In-Reply-To: <1170263470.12392.23.camel@kleikamp.austin.ibm.com>
> Right now I've only really looked at the jfs patch, since that's what
> I'm the most familiar with. I'll try to take a look at the rest of them
> later.
Thank you!
> I don't have a strong opinion for or against the function and your
> design. The only potential problem I see in the approach is that
> the .trash directory may conflict with some other use of the same name.
> Since this is primarily vfs function, you'll probably get a wider
> audience on linux-fsdevel.
Well, I guess lost+found has the same problem but it is not a problem at
all to pick some other (longer) name.
> Have you considered putting ALL of the function in the vfs layer? It
> looks like this could be done without touching any code in the
> individual file systems.
Unfortunately, we need some file system-specific code to access per-file
secure deletion and per-file trash bit attributes. These attributes are
supported only by some file systems and in different ways. We need no
file system-specific code to support trash-bin deletion for whole file
systems.
Nikolai.
next prev parent reply other threads:[~2007-02-01 17:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 14:55 [Resubmit][PATCH 5/5] Secure Deletion and Trash-Bin Support for Ext4 Harry Papaxenopoulos
2007-01-31 17:11 ` Dave Kleikamp
2007-02-01 11:05 ` Harry Papaxenopoulos
2007-02-01 13:19 ` Dave Kleikamp
2007-02-01 17:17 ` Nikolai Joukov [this message]
2007-02-01 19:32 ` Dave Kleikamp
2007-02-01 20:41 ` Mingming Cao
2007-02-02 1:40 ` Andreas Dilger
2007-02-02 2:22 ` Dave Kleikamp
2007-02-06 3:48 ` Theodore Tso
2007-02-25 10:33 ` Andrew Morton
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=Pine.GSO.4.53.0702011200340.9072@compserv1 \
--to=kolya@cs.sunysb.edu \
--cc=ezk@cs.sunysb.edu \
--cc=harry@cs.sunysb.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=shaggy@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).