From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-ext4@vger.kernel.org
Subject: e4defrag and immutable files
Date: Fri, 28 May 2010 13:14:31 -0700 [thread overview]
Message-ID: <4C002427.3010706@zytor.com> (raw)
Hi all,
I have looked a bit at e4defrag, and it does not appear to prevent the
relocation of files marked immutable. This is a problem for boot
loaders, which may need to have a block pointer to a specific file in
order to bootstrap themselves.
Would it be possible to either:
a) prevent e4defrag and/or EXT4_IOC_MOVE_EXT from relocating an
immutable file, or
b) add a new attribute with the above property (in case there is
legitimate need to move around immutable files)?
-hpa
next reply other threads:[~2010-05-28 20:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 20:14 H. Peter Anvin [this message]
2010-05-28 21:21 ` e4defrag and immutable files Greg Freemyer
2010-05-28 22:06 ` H. Peter Anvin
2010-06-01 19:12 ` Eric Sandeen
2010-06-01 19:32 ` Sunil Mushran
2010-06-01 19:49 ` tytso
2010-06-01 20:14 ` Greg Freemyer
2010-06-01 21:00 ` Eric Sandeen
2010-06-01 21:28 ` Sunil Mushran
2010-06-01 22:26 ` tytso
2010-06-01 22:51 ` Sunil Mushran
2010-06-02 7:28 ` H. Peter Anvin
2010-06-02 18:02 ` Sunil Mushran
2010-06-08 22:12 ` H. Peter Anvin
2010-06-09 1:10 ` Joel Becker
2010-06-09 1:44 ` tytso
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=4C002427.3010706@zytor.com \
--to=hpa@zytor.com \
--cc=linux-ext4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.