From: Andreas Dilger <adilger@clusterfs.com>
To: Vineet Joglekar <vintya@excite.com>
Cc: linux-kernel@vger.kernel.org, linux-c-programming@vger.kernel.org
Subject: Re: Adding a field to ext2_dir_entry_2
Date: Mon, 4 Apr 2005 17:17:59 -0600 [thread overview]
Message-ID: <20050404231759.GN1753@schnapps.adilger.int> (raw)
In-Reply-To: <20050404225442.52A7AB730@xprdmailfe18.nwk.excite.com>
[-- Attachment #1: Type: text/plain, Size: 846 bytes --]
On Apr 04, 2005 18:54 -0400, Vineet Joglekar wrote:
> I working with linux kernel 2.4.28. I want to add 1 more field to
> ext2_dir_entry_2 - the new version of directory entry for ext2fs.
>
> I did add the __u32 field to the struct ext2_dir_entry_2 defined in
> ext2_fs.h I also modified the EXT2_DIR_REC_LEN macro to:
>
> (((name_len) + 12 + EXT2_DIR_ROUND) & ~EXT2_DIR_ROUND)
>
> (+12 instead of +8) to incorporate newly added 4 bytes field.
>
> I made the similar changes to the mke2fs utility also.
This means your filesystem will not be mountable by any other version of
Linux. What is more important is why you want to do this - there are
other mechanisms that may be more appropriate depending on what you are
doing.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-04-04 23:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 22:54 Adding a field to ext2_dir_entry_2 Vineet Joglekar
2005-04-04 23:17 ` Andreas Dilger [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-05 0:08 Vineet Joglekar
2005-04-04 22:10 ` Christopher Li
2005-04-05 1:12 ` Andreas Dilger
2005-04-05 3:53 ` Theodore Ts'o
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=20050404231759.GN1753@schnapps.adilger.int \
--to=adilger@clusterfs.com \
--cc=linux-c-programming@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vintya@excite.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).