From: Andrew Morton <akpm@linux-foundation.org>
To: Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com>
Cc: linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org,
tytso@mit.edu, adilger@sun.com, jack@suse.cz, sandeen@redhat.com
Subject: Re: status of the ext3/jbd error handling enhancement patches
Date: Sun, 19 Oct 2008 22:13:31 -0700 [thread overview]
Message-ID: <20081019221331.ddf6b8c2.akpm@linux-foundation.org> (raw)
In-Reply-To: <48FC081D.60306@hitachi.com>
On Mon, 20 Oct 2008 13:25:01 +0900 Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com> wrote:
> Hi Andrew,
>
> Thank you for pushing my ext3/jbd to Linus. But some of patches
> in -mm (following three patches) haven't been sent to Linus.
>
> #jbd-fix-error-handling-for-checkpoint-io.patch: double-check this
> jbd-fix-error-handling-for-checkpoint-io.patch
> ext3-add-checks-for-errors-from-jbd.patch
> jbd-test-bh_write_eio-to-detect-errors-on-metadata-buffers.patch
>
> They improve filesystem corruption problem and it is needed by
> mission critical systems.
>
> Could you tell me what is your concern (you commented, "double-check
> this") ? Are there something that I can help? For example, I can
> provide some SystemTap scripts to help tests.
I forget my reasons for that - would need to go back and review the
discussions when the patch was first merged.
One of the above patches (I forget which) breaks the build because it
expects the presence of Al Viro's VFS tree, and that hasn't been merged
yet. I need to wait and see if that merge will be happening (seems
unlikely) and if not, rework the patch against mainline.
Quie a few patches (5%?) tend to get delayed like this due to missing
dependencies.
next prev parent reply other threads:[~2008-10-20 5:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 4:25 status of the ext3/jbd error handling enhancement patches Hidehiro Kawai
2008-10-20 5:13 ` Andrew Morton [this message]
2008-10-20 12:41 ` Theodore Tso
2008-10-21 6:24 ` Hidehiro Kawai
2008-10-21 6:37 ` Andrew Morton
2008-10-20 17:17 ` Simon Kirby
2008-10-22 4:54 ` Hidehiro Kawai
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=20081019221331.ddf6b8c2.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adilger@sun.com \
--cc=hidehiro.kawai.ez@hitachi.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.com \
--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.