From: Chris Mason <chris.mason@oracle.com>
To: Stefan Behrens <sbehrens@giantdisaster.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/4] Btrfs: runtime integrity check tool
Date: Wed, 9 Nov 2011 12:50:10 -0500 [thread overview]
Message-ID: <20111109175010.GQ9368@shiny> (raw)
In-Reply-To: <cover.1320849129.git.sbehrens@giantdisaster.de>
On Wed, Nov 09, 2011 at 04:17:57PM +0100, Stefan Behrens wrote:
> This patch series adds a new module to the btrfs kernel mode
> code. This new module can be used to catch cases when the
> btrfs kernel code executes write requests to the disk that
> bring the file system in an inconsistent state. In such a
> state, a power-loss or kernel panic event would cause that
> the data on disk is lost or at least damaged.
>
> Code is added that examines all block write requests during
> runtime (including writes of the super block). Three rules
> are verified and an error is printed on violation of the
> rules:
This patch is clearly useful because it has already found two big bugs.
I'll definitely review it in detail and somehow or another I'd love to
include this functionality in 3.3.
Thanks again!
-chris
prev parent reply other threads:[~2011-11-09 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 15:17 [PATCH 0/4] Btrfs: runtime integrity check tool Stefan Behrens
2011-11-09 15:17 ` [PATCH 1/4] Btrfs: add optional integrity check code Stefan Behrens
2011-11-09 15:17 ` [PATCH 2/4] Btrfs: add config option to enable btrfs integrity check Stefan Behrens
2011-11-09 15:18 ` [PATCH 3/4] Btrfs: Makefile changes to optionally include " Stefan Behrens
2011-11-09 15:18 ` [PATCH 4/4] Btrfs: integrate integrity check module into btrfs Stefan Behrens
2011-11-09 17:50 ` Chris Mason [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=20111109175010.GQ9368@shiny \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sbehrens@giantdisaster.de \
/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