From: Theodore Tso <tytso@mit.edu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: dhowells@redhat.com,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: - disable-ext4.patch removed from -mm tree
Date: Mon, 4 Feb 2008 15:30:29 -0500 [thread overview]
Message-ID: <20080204203029.GN18392@mit.edu> (raw)
In-Reply-To: <20080204121131.a6e07705.akpm@linux-foundation.org>
On Mon, Feb 04, 2008 at 12:11:31PM -0800, Andrew Morton wrote:
>
> That patch series is kind of logjammed anyway because it breaks isofs.
> Last time I discussed this with David he seemed to find this amusing rather
> than an urgent problem. I'd drop the whole lot if there weren't lots of
> other patches dependent upon them. Mayeb I can do a selective droppage,
> but I hate going out-of-order, and merging untested patch combinations.
>
All of the patches which move from using iget() to iget_unlocked()
should in theory (if they are well written) be standalone and not have
any prerequisites, and a good thing to apply in and of themselves.
So maybe the right thing to do is to push all of them right away, and
then if they all can go in safely w/o breaking filesystems, we can
actually do the deed about removing the iget() interface itself, and
if not, it can wait until 2.6.26. It's not really that big of a deal
to actually nuke the interface itself, as long as we are gradually
reducing our usage of it.... Or is there some patch which David is
trying to push that desperately depends on iget() going away?
- Ted
next prev parent reply other threads:[~2008-02-04 20:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 20:18 - disable-ext4.patch removed from -mm tree akpm
2008-02-03 20:25 ` Andrew Morton
2008-02-04 1:36 ` Theodore Tso
2008-02-04 3:15 ` Andrew Morton
2008-02-04 15:00 ` Theodore Tso
2008-02-04 20:11 ` Andrew Morton
2008-02-04 20:30 ` Theodore Tso [this message]
2008-02-05 9:40 ` David Howells
2008-02-05 21:26 ` Mingming Cao
2008-02-06 1:02 ` Mingming Cao
2008-02-06 1:57 ` Andrew Morton
2008-02-06 2:21 ` Mingming Cao
2008-02-04 20:24 ` merge plans, was " Christoph Hellwig
2008-02-04 22:35 ` Andrew Morton
2008-02-05 9:44 ` Christoph Hellwig
2008-02-05 9:53 ` Andrew Morton
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=20080204203029.GN18392@mit.edu \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.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.