From: Michael Rubin <mrubin@google.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Xiang Wang <xiangw@google.com>,
linux-ext4@vger.kernel.org, aneesh.kumar@linux.vnet.ibm.com,
Curt Wohlgemuth <curtw@google.com>,
Chad Talbott <ctalbott@google.com>,
Frank Mayhar <fmayhar@google.com>
Subject: Re: fsck errors encountered when applying patch "ext4: fix BUG when calling ext4_error with locked block group"
Date: Fri, 20 Feb 2009 17:37:35 -0800 [thread overview]
Message-ID: <532480950902201737j5162125teea57eedbd01873f@mail.gmail.com> (raw)
In-Reply-To: <20090221012908.GC12966@mini-me.lan>
On Fri, Feb 20, 2009 at 5:29 PM, Theodore Tso <tytso@mit.edu> wrote:
> One of the downsides of trying to backport a lot of changes to a
> kernel version as old as 2.6.26 is that you miss changes like this.
> You might want to think about leapfrogging to a newer kernel at some
> point....
We know. Our qualifying process is not the most light weight and the
kernel moves fast. Normally we take a snapshot and qualify it, trying
to take upstream patches when we can and then also publishing bugs we
find. The problem is that with ext4 still undergoing active dev we
want to be able to keep our ext4 portion of the tree as up to date as
possible.
I admit it's a bit of a balancing act.
Hopefully we won't be causing a lot of undue burden on this list.
Thanks for this.
Michael Rubin
next prev parent reply other threads:[~2009-02-21 1:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 23:31 fsck errors encountered when applying patch "ext4: fix BUG when calling ext4_error with locked block group" Xiang Wang
2009-02-21 1:29 ` Theodore Tso
2009-02-21 1:37 ` Michael Rubin [this message]
2009-02-21 1:50 ` Theodore Tso
2009-02-25 18:33 ` Xiang Wang
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=532480950902201737j5162125teea57eedbd01873f@mail.gmail.com \
--to=mrubin@google.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=ctalbott@google.com \
--cc=curtw@google.com \
--cc=fmayhar@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=xiangw@google.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).