From: Jeff Mahoney <jeffm@suse.com>
Cc: ReiserFS Development Mailing List
<reiserfs-devel@vger.kernel.org>,
Vladimir Saveliev <vs@namesys.com>
Subject: Re: [patch 00/11] reiserfs fixups and error handling
Date: Thu, 12 Jul 2007 15:47:59 -0400 [thread overview]
Message-ID: <4696856F.3030406@suse.com> (raw)
In-Reply-To: <20070712193738.112875514@mail.jeffreymahoney.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
jeffm@suse.com wrote:
> This is the first part of a series of patches I've been developing for
> reiserfs. I'm posting them now for review followed by submission to 2.6.23.
>
> The first 4 patches are small fixes:
> * Adding proper lockdep annotation to xattrs
> * Switching to panic() instead of BUG() in reiserfs_panic()
> * Making is_reusable bitmap sanity checking unconditional
> * Using the first zero hint in bitmap iteration
>
> The remaining 7 work to make reiserfs error handling more consistent
> and robust:
> * Use consistent message prefixes for all reiserfs log output
> * Add a reiserfs_info() call for multiline output that doesn't
> masquerade as a warning.
> * Make reiserfs_warning() calls more consistent, requiring an ID, and
> including the device and function where the warning is occuring.
> * Make reiserfs_panic() more consistent in the same manner.
> * Rearrange reiserfs_journal_abort() since it was modelled after jbd's
> call and doesn't need to be. There's several function calls that
> just get optimized out anyway.
>
> * Add a reiserfs_error() call to handle metadata errors by aborting
> the journal and marking the file system read-only.
> * Convert 50 reiserfs_warning(), 2 reiserfs_panic(), and one BUG_ON
> site to use the new reiserfs_error().,
>
> -Jeff
>
Apologies for the double post. I had the wrong to: address in the
headers, but gave the correct address to formail, so they got sent out
but any replies would be thrown into oblivion.
- -Jeff
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFGloVvLPWxlyuTD7IRAllBAJ9Fyn3JpICyNxh49hcPOx55VmM/OwCeOWy/
RWYW8hUaGdKYVOpSjDC9H9c=
=vFGK
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2007-07-12 19:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 19:37 [patch 00/11] reiserfs fixups and error handling jeffm
2007-07-12 19:37 ` [patch 01/11] reiserfs: fix up lockdep warnings jeffm
2007-07-12 19:37 ` [patch 02/11] reiserfs: dont use BUG when panicking jeffm
2007-07-12 19:37 ` [patch 03/11] reiserfs: use is_reusable to catch corruption jeffm
2007-07-12 19:37 ` [patch 04/11] reiserfs: make bitmap use cached first zero bit jeffm
2007-07-12 19:37 ` [patch 05/11] reiserfs: use more consistent printk formatting jeffm
2007-07-12 19:37 ` [patch 06/11] reiserfs: make some warnings informational jeffm
2007-07-12 19:37 ` [patch 07/11] reiserfs: rework reiserfs_warning jeffm
2007-07-12 19:37 ` [patch 08/11] reiserfs: rework reiserfs_panic jeffm
2007-07-12 19:37 ` [patch 09/11] reiserfs: rearrange journal abort jeffm
2007-07-12 19:37 ` [patch 10/11] reiserfs: introduce reiserfs_error() jeffm
2007-07-12 19:37 ` [patch 11/11] reiserfs: use reiserfs_error() jeffm
2007-07-12 19:47 ` 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=4696856F.3030406@suse.com \
--to=jeffm@suse.com \
--cc=reiserfs-devel@vger.kernel.org \
--cc=vs@namesys.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 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.