From: Theodore Tso <tytso@mit.edu>
To: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
Cc: Andreas Dilger <adilger@clusterfs.com>,
Mingming Cao <cmm@us.ibm.com>,
Dave Kleikamp <shaggy@linux.external-vnet.ibm.com>,
Nikolai Joukov <kolya@cs.sunysb.edu>,
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: Mon, 5 Feb 2007 22:48:53 -0500 [thread overview]
Message-ID: <20070206034853.GD11018@thunk.org> (raw)
In-Reply-To: <1170382948.18617.30.camel@kleikamp.austin.ibm.com>
On Thu, Feb 01, 2007 at 08:22:28PM -0600, Dave Kleikamp wrote:
> Al Viro will love that one. :-)
>
> Another idea might be to store those attribute flags in the generic
> inode.
Yeah, that's really the right answer. Having a common way of storing
attributes in struct kstat (and notified via struct iattr and
notify_change) is the right way for us to store some of these
filesystem-common flags, and would make a huge amount of sense.
I don't really view ths secure deletion and trash-bin support as
really being an ext4 feature, but really a generic feature which can
enhance multiple filesystems *including* ext4. So it would be really
good idea to give these patches an airing on linux-fsdevel and
linux-kernel.
Regards,
- Ted
next prev parent reply other threads:[~2007-02-06 5:54 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 [this message]
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=20070206034853.GD11018@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@clusterfs.com \
--cc=cmm@us.ibm.com \
--cc=ezk@cs.sunysb.edu \
--cc=harry@cs.sunysb.edu \
--cc=kolya@cs.sunysb.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=shaggy@linux.external-vnet.ibm.com \
--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).