From: Theodore Tso <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: Ext2/3 block remapping tool
Date: Tue, 1 May 2007 18:18:28 -0400 [thread overview]
Message-ID: <20070501221828.GF26093@thunk.org> (raw)
In-Reply-To: <20070501185249.GG5722@schatzie.adilger.int>
On Tue, May 01, 2007 at 12:52:49PM -0600, Andreas Dilger wrote:
> I think "rm -r" does a LOT of this kind of operation, like:
>
> stat(.); stat(foo); chdir(foo); stat(.); unlink(*); chdir(..); stat(.)
>
> I think "find" does the same to avoid security problems with malicious
> path manipulation.
Yep, so if you're doing an rm -rf (or any other recursive descent)
while we're doing an on-line shrink, it's going to fail. I suppose we
could have an in-core inode mapping table that would continue to remap
inode numbers until the next reboot. I'm not sure we would want to
keep the inode remapping indefinitely, although if we don't it could
also end up screwing up NFS as well. Not sure I care, though. :-)
- Ted
prev parent reply other threads:[~2007-05-01 22:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 19:29 Ext2/3 block remapping tool Jan Kara
2007-04-27 18:09 ` Andreas Dilger
2007-04-30 10:12 ` Jan Kara
2007-04-30 12:09 ` Theodore Tso
2007-04-30 12:29 ` Jan Kara
2007-05-01 6:01 ` Andreas Dilger
2007-05-01 15:28 ` Theodore Tso
2007-05-01 18:52 ` Andreas Dilger
2007-05-01 22:18 ` Theodore Tso [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=20070501221828.GF26093@thunk.org \
--to=tytso@mit.edu \
--cc=jack@suse.cz \
--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).