From: Jeff Mahoney <jeffm@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: [patch 00/10] btrfs: Error handling/propagation queue
Date: Wed, 04 Nov 2009 14:43:18 -0500 [thread overview]
Message-ID: <4AF1D956.1020407@suse.com> (raw)
In-Reply-To: <20091104190346.971762946@suse.com>
On 11/04/2009 02:03 PM, Jeff Mahoney wrote:
> This patch series fixes a few existing problems and then addresses
> the need for better error handling and propagation in btrfs.
>
> The handling and propagation patch set first finds all locations of
> a particular condition not being checked and annotates them with
> BTRFS_UERROR to designate that there is an error condition that
> is currently unhandled but should be. Then, another patch traverses
> the call path to ensure that errors are properly propogated. When the
> fix for recovering or passing the error is obvious, we do that too.
>
> This set is not complete and I expect there to be more fixes coming. In
> particular, it currently only annotates btrfs_alloc_path failures as
> the call graph for it is quite large. This is in response to Chris asking
> for what I already have instead of waiting for it to be complete.
I should be clear that this is just what I've been working on so far and
hasn't received any testing yet. It was a quick quilt mail in the middle
of working on it. (As you might notice by the fact that it doesn't build.)
-Jeff
--
Jeff Mahoney
SUSE Labs
prev parent reply other threads:[~2009-11-04 19:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 19:03 [patch 00/10] btrfs: Error handling/propagation queue Jeff Mahoney
2009-11-04 19:03 ` [patch 01/10] btrfs: fix btrfs_read_block_groups return value Jeff Mahoney
2009-11-04 19:03 ` [patch 02/10] btrfs: fix memleak in btrfs_init_new_device Jeff Mahoney
2009-11-04 19:03 ` [patch 03/10] btrfs: fix btrfs_read_fs_root* return values Jeff Mahoney
2009-11-04 19:03 ` [patch 04/10] btrfs: btrfs_sync_file should return -EIO not EIO Jeff Mahoney
2009-11-04 19:03 ` [patch 05/10] btrfs: Add BTRFS_UERROR for unhandled errors Jeff Mahoney
2009-11-04 19:03 ` [patch 06/10] btrfs: annotate kmalloc failures Jeff Mahoney
2009-11-04 19:03 ` [patch 07/10] btrfs: handle kmalloc call path failures Jeff Mahoney
2009-11-04 19:03 ` [patch 08/10] btrfs: annotate btrfs_{start,join}_transaction failures Jeff Mahoney
2009-11-04 19:03 ` [patch 09/10] btrfs: handle btrfs_{start,join}_transaction call path failures Jeff Mahoney
2009-11-04 19:03 ` [patch 10/10] btrfs: annotate btrfs_alloc_path failures Jeff Mahoney
2009-11-04 19:43 ` Jeff Mahoney [this message]
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=4AF1D956.1020407@suse.com \
--to=jeffm@suse.com \
--cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox