From: Nathan Scott <nscott@aconex.com>
To: David Chinner <dgc@sgi.com>
Cc: Josef Sipek <jsipek@fsl.cs.sunysb.edu>,
Nikolai Joukov <kolya@cs.sunysb.edu>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [RFC][PATCH] Secure Deletion and Trash-Bin Support for Ext4
Date: Thu, 07 Dec 2006 16:45:52 +1100 [thread overview]
Message-ID: <1165470352.30459.14.camel@edge> (raw)
In-Reply-To: <20061207014426.GL44411608@melbourne.sgi.com>
On Thu, 2006-12-07 at 12:44 +1100, David Chinner wrote:
> Maybe we should be using EAs for this sort of thing instead of flags
> on the inode? If we keep adding inode flags for generic features
> then we are going to force more than just XFS into inode format
> changes eventually....
You do need to be judicious in what you add, but we got up to here
(well over 10 years) with 16 bits worth of space - increasing to 32
bits is going to last a fairly long time... I wouldn't switch to a
different scheme until that point (which is also the point where the
system calls are going to have to change anyway).
cheers.
--
Nathan
next prev parent reply other threads:[~2006-12-07 5:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 18:33 [RFC][PATCH] Secure Deletion and Trash-Bin Support for Ext4 Nikolai Joukov
2006-12-04 23:50 ` David Chinner
2006-12-05 16:41 ` Nikolai Joukov
2006-12-06 9:11 ` David Chinner
2006-12-06 22:16 ` Nathan Scott
2006-12-07 0:56 ` Josef Sipek
2006-12-07 1:44 ` David Chinner
2006-12-07 2:35 ` Josef Sipek
2006-12-07 2:49 ` David Chinner
2006-12-07 3:14 ` Nicholas Miell
2006-12-07 5:35 ` Josef Sipek
2006-12-07 5:45 ` Nathan Scott [this message]
2006-12-09 1:44 ` Nikolai Joukov
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=1165470352.30459.14.camel@edge \
--to=nscott@aconex.com \
--cc=dgc@sgi.com \
--cc=jsipek@fsl.cs.sunysb.edu \
--cc=kolya@cs.sunysb.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
/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).