public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Making it easier for end users to use ext4
Date: Mon, 14 Jul 2008 16:27:31 -0500	[thread overview]
Message-ID: <487BC4C3.9020400@redhat.com> (raw)
In-Reply-To: <20080714195526.GA3382@mit.edu>

Theodore Tso wrote:
> On Mon, Jul 14, 2008 at 02:35:07PM -0500, Eric Sandeen wrote:
>>> Eric, when you have a chance, could you take a quick peek at the Fedora
>>> Core section of that page and update it appropriately.  
>> Sure, first I'll remove "core" since that terminology doesn't exist
>> anymore ;)
> 
> Is "FC" acronym as in "FC9" going away as well?  :-)

the "fc9" you see in rpms now stands for "Fedora Collection" - becase,
well, rpm got confused otherwise ;)

I probably forget this from time to time as well ;)

> 
>> I think very soon just saying "run the latest kernel + e2fsprogs from F9
>> updates-testing" will be a good start.  It won't have delalloc yet,
>> though.  Do we want to try to make that more widely available to people
>> who can't/don't build their own kernels?  I'm slightly hesitant I guess
>> both for the extra work of maintaining the repo & complete kernel
>> builds, as well as providing too much rope to people who may not know
>> just how much rope they've got ...
> 
> Well, there are two reasons why I was thinking it might be nice to
> synch up the ext4 code base.  One was the "more testers good"
> argument.  The other was is that while *most* of the various races and
> bug fixes that have gone in since 2.6.26 were delalloc related, some
> are real bugs that might bite 2.6.25 users if they start using the
> ext4 code in a more demanding workload.  That would result in perhaps
> preventable data loss, plus which we could end up spending time
> debugging a problem which had already been solved.

Sounds reasonable.  Should said fixes also go into the 2.6.2[56].x
stable trees for the same reasons, do you think?  And, well, if they
did, Fedora would also get them rather quickly.  :)

> If Fedora is going to be putting out another test kernel shortly, any
> chance we can get the 2.6.26-ext4-1 or 2.6.26-ext4-2 (with mingming's
> latest patch, to be released shortly) included in that test kernel?
> Again, the goal is to make it as easy as possible for people to test
> the latest version of ext4, so we can get those bugs fixed.

I've gone back and forth about how bleeding-edge to make the Fedora ext4
code, especially for F9.  Putting it all into rawhide would be fine,
that's what it's for.  But for F9 I'd like to stay on that fine line
between "fix the bugs & add the features quickly" and "don't push
unstable or barely-stable code into the release too soon and cause new
problems."

I don't mind pushing the stable patches into F9 on the early side, and
for rawhide we can push as much as is desired.

Thanks,
-Eric

> Regards,
> 
> 						- Ted


  reply	other threads:[~2008-07-14 21:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 19:24 Making it easier for end users to use ext4 Theodore Ts'o
2008-07-14 19:35 ` Eric Sandeen
2008-07-14 19:55   ` Theodore Tso
2008-07-14 21:27     ` Eric Sandeen [this message]
     [not found]     ` <1216172323.8292.23.camel@mingming-laptop>
     [not found]       ` <20080716023532.GO8185@mit.edu>
     [not found]         ` <1216227720.6424.7.camel@mingming-laptop>
2008-07-16 17:52           ` [PATCH, RFC] Add more intelligent handling of the mke2fs.conf installation process Theodore Tso
2008-07-16 18:24             ` Mingming Cao
2008-07-16 21:29             ` Andreas Dilger
2008-07-16 23:08               ` Theodore Tso
2008-07-15  5:22 ` Making it easier for end users to use ext4 Goswin von Brederlow

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=487BC4C3.9020400@redhat.com \
    --to=sandeen@redhat.com \
    --cc=linux-ext4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox