From: Jeff Garzik <jgarzik@pobox.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2/11 Ext2/3 Updates: Extended attributes, ACL, etc.
Date: Sat, 02 Nov 2002 03:57:35 -0500 [thread overview]
Message-ID: <3DC3937F.80504@pobox.com> (raw)
In-Reply-To: 20021101032159.GA12031@think.thunk.org
Theodore Ts'o wrote:
>I'm not sure ext2meta will be sufficient. It's not just a matter of
>modifying the on-disk metadata, as would be needed for defrag, but I
>would also need to modify some of the in-core data structions in the
>ext2/3 filesystem data structures. For example, when you resize the
>filesystem, you need to increase the number of group descriptors,
>which means you need to kmalloc, copy, and then kfree sbi->group_desc
>out from under the mounted filesystem.
>
>No doubt ext2meta could be modified so it could "reach out and touch"
>internal ext2/3 fileststem data structures in core. But the locking
>issues involved get really messy.
>
>
Like Al mentioned... any merge of ext[23]meta would be inside ext[23].o,
so it would be a first class object and not some random module sticking
its fingers in there. I looked at the locking issue too (though
admittedly not in-depth for filesystem resize), and it's not different
at all from existing locking, both in 2.4.x and 2.5.x. It's
intentionally pretty darn compatible with existing locking :)
I'll post a patch in the next couple weeks...
Jeff
next prev parent reply other threads:[~2002-11-02 8:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-29 16:42 [PATCH] 2/11 Ext2/3 Updates: Extended attributes, ACL, etc tytso
2002-10-29 17:22 ` Jeff Garzik
2002-10-31 3:41 ` Theodore Ts'o
2002-11-01 3:22 ` Theodore Ts'o
2002-11-01 3:35 ` Alexander Viro
2002-11-02 8:57 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-31 8:28 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=3DC3937F.80504@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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.