From: Valerie Aurora <vaurora@redhat.com>
To: Andreas Dilger <adilger@sun.com>
Cc: Jan Blunck <jblunck@suse.de>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christoph Hellwig <hch@infradead.org>,
Andy Whitcroft <apw@canonical.com>,
Scott James Remnant <scott@canonical.com>,
Sandu Popa Marius <sandupopamarius@gmail.com>,
Jan Rekorajski <baggins@sith.mimuw.edu.pl>,
"J. R. Okajima" <hooanon05@yahoo.co.jp>,
Arnd Bergmann <arnd@arndb.de>,
Vladimir Dronnikov <dronnikov@gmail.com>,
Felix Fietkau <nbd@openwrt.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Theodore Tso <tytso@mit.edu>,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH 15/41] whiteout: ext2 whiteout support
Date: Mon, 26 Oct 2009 22:14:26 -0400 [thread overview]
Message-ID: <20091027021426.GA14574@shell> (raw)
In-Reply-To: <1983FB3A-C88F-4EF4-A2E1-8B18DF97F0AB@sun.com>
On Wed, Oct 21, 2009 at 03:17:38PM -0600, Andreas Dilger wrote:
> On 2009-10-21, at 13:19, Valerie Aurora wrote:
> >This patch adds whiteout support to EXT2. A whiteout is an empty
> >directory
> >entry (inode == 0) with the file type set to EXT2_FT_WHT. Therefore it
> >allocates space in directories. Due to being implemented as a
> >filetype it is
> >necessary to have the EXT2_FEATURE_INCOMPAT_FILETYPE flag set.
> >
> >diff --git a/include/linux/ext2_fs.h b/include/linux/ext2_fs.h
> >index 121720d..bd10826 100644
> >--- a/include/linux/ext2_fs.h
> >+++ b/include/linux/ext2_fs.h
> >@@ -189,6 +189,7 @@ struct ext2_group_desc
> >+#define EXT2_OPAQUE_FL 0x00040000
>
> Please check in the upstream e2fsprogs ext2_fs.h before defining new
> flag
> values for ext2/3/4. In this case, 0x40000 conflicts with
> EXT4_HUGE_FILE_FL,
> which is of course bad.
>
>
> >@@ -503,10 +504,12 @@ struct ext2_super_block {
> >#define EXT2_FEATURE_INCOMPAT_META_BG 0x0010
> >+#define EXT2_FEATURE_INCOMPAT_WHITEOUT 0x0020
>
> This one doesn't conflict, probably due to luck, because 0x0040-0x0200
> are
> already in use for other features. I'm not sure if 0x0020 was
> reserved for
> some other use, or just skipped to avoid potential conflicts.
Thanks for reviewing! I'll fix that in the next rev.
-VAL
next prev parent reply other threads:[~2009-10-27 2:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1256152779-10054-1-git-send-email-vaurora@redhat.com>
[not found] ` <1256152779-10054-2-git-send-email-vaurora@redhat.com>
[not found] ` <1256152779-10054-3-git-send-email-vaurora@redhat.com>
[not found] ` <1256152779-10054-4-git-send-email-vaurora@redhat.com>
[not found] ` <1256152779-10054-5-git-send-email-vaurora@redhat.com>
[not found] ` <1256152779-10054-6-git-send-email-vaurora@redhat.com>
[not found] ` <1256152779-10054-7-git-send-email-vaurora@redhat.com>
[not found] ` <1256152779-10054-8-git-send-email-vaurora@redhat.com>
[not found] ` <1256152779-10054-9-git-send-email-vaurora@redhat.com>
[not found] ` <1256152779-10054-10-git-send-email-vaurora@redhat.com>
[not found] ` <1256152779-10054-11-git-send-email-vaurora@redhat.com>
[not found] ` <1256152779-10054-12-git-send-email-vaurora@redhat.com>
[not found] ` <1256152779-10054-13-git-send-email-vaurora@redhat.com>
[not found] ` <1256152779-10054-14-git-send-email-vaurora@redhat.com>
2009-10-21 19:19 ` [PATCH 14/41] whiteout: Split of ext2_append_link() from ext2_add_link() Valerie Aurora
2009-10-21 19:19 ` [PATCH 15/41] whiteout: ext2 whiteout support Valerie Aurora
[not found] ` <1256152779-10054-17-git-send-email-vaurora@redhat.com>
[not found] ` <1256152779-10054-18-git-send-email-vaurora@redhat.com>
[not found] ` <1256152779-10054-19-git-send-email-vaurora@redhat.com>
[not found] ` <1256152779-10054-20-git-send-email-vaurora@redhat.com>
[not found] ` <1256152779-10054-21-git-send-email-vaurora@redhat.com>
[not found] ` <1256152779-10054-22-git-send-email-vaurora@redhat.com>
[not found] ` <1256152779-10054-23-git-send-email-vaurora@redhat.com>
[not found] ` <1256152779-10054-24-git-send-email-vaurora@redhat.com>
[not found] ` <1256152779-10054-25-git-send-email-vaurora@redhat.com>
[not found] ` <1256152779-10054-26-git-send-email-vaurora@redhat.com>
[not found] ` <1256152779-10054-27-git-send-email-vaurora@redhat.com>
[not found] ` <1256152779-10054-28-git-send-email-vaurora@redhat.com>
[not found] ` <1256152779-10054-29-git-send-email-vaurora@redhat.com>
[not found] ` <1256152779-10054-30-git-send-email-vaurora@redhat.com>
[not found] ` <1256152779-10054-31-git-send-email-vaurora@redhat.com>
[not found] ` <1256152779-10054-32-git-send-email-vaurora@redhat.com>
2009-10-21 19:19 ` [PATCH 32/41] fallthru: ext2 fallthru support Valerie Aurora
2009-12-01 4:17 ` Erez Zadok
2009-10-21 21:17 ` [PATCH 15/41] whiteout: ext2 whiteout support Andreas Dilger
2009-10-27 2:14 ` Valerie Aurora [this message]
2009-11-30 7:45 ` Erez Zadok
2009-11-30 6:32 ` [PATCH 14/41] whiteout: Split of ext2_append_link() from ext2_add_link() Erez Zadok
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=20091027021426.GA14574@shell \
--to=vaurora@redhat.com \
--cc=adilger@sun.com \
--cc=apw@canonical.com \
--cc=arnd@arndb.de \
--cc=baggins@sith.mimuw.edu.pl \
--cc=dronnikov@gmail.com \
--cc=hch@infradead.org \
--cc=hooanon05@yahoo.co.jp \
--cc=jblunck@suse.de \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbd@openwrt.org \
--cc=sandupopamarius@gmail.com \
--cc=scott@canonical.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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).