linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
Cc: harry@cs.sunysb.edu, linux-ext4@vger.kernel.org,
	ezk@cs.sunysb.edu, kolya@cs.sunysb.edu
Subject: Re: [Resubmit][PATCH 5/5] Secure Deletion and Trash-Bin Support for Ext4
Date: Sun, 25 Feb 2007 02:33:56 -0800	[thread overview]
Message-ID: <20070225023356.ecd53f65.akpm@linux-foundation.org> (raw)
In-Reply-To: <1170263470.12392.23.camel@kleikamp.austin.ibm.com>

> On Wed, 31 Jan 2007 11:11:10 -0600 Dave Kleikamp <shaggy@linux.vnet.ibm.com> wrote:
> Have you considered putting ALL of the function in the vfs layer?

Yes, I think that's where it should be implemented.

I suspect we'll run into problems with the .trash/<uid> thing.  What directory
do we put .trash in?  The top-level of the mountpoint?   The user might not
be able to access that if he's in a chroot.  And UIDs are now per-nsproxy
things - UIDs are already per-uid-namespace things. So we can have two or more
different users using UID 42.

It all need to be thrashed out with the containerisation and VFS guys.

      parent reply	other threads:[~2007-02-25 10:34 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
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 [this message]

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=20070225023356.ecd53f65.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=ezk@cs.sunysb.edu \
    --cc=harry@cs.sunysb.edu \
    --cc=kolya@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).