From: Chris Mason <chris.mason@oracle.com>
To: TARUISI Hiroaki <taruishi.hiroak@jp.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: bug fixes
Date: Fri, 2 Oct 2009 15:09:57 -0400 [thread overview]
Message-ID: <20091002190957.GL2881@think> (raw)
In-Reply-To: <4AC59118.6030707@jp.fujitsu.com>
On Fri, Oct 02, 2009 at 02:35:20PM +0900, TARUISI Hiroaki wrote:
> Hi,
>
> I have tested btrfsck in some error case, such as item missing
> case or CRC error case or so. In this test session I found some
> bugs in btrfsck.c and disk-io.c in btrfs-progs.
> 1. The last pair of ptrs and items are not checked at 2 place
> of check_node/leaf.
> 2. Csum printed CRC error message is not correct.
> 3. In CRC error, btrfsck fails in segmentation fault.
>
> I'll post three tiny patches to fix these bugs.
Thank you for spending time in the btrfsck code. I'll test these out
and get them pushed into the btrfs-progs repository.
-chris
prev parent reply other threads:[~2009-10-02 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 5:35 [PATCH] btrfs-progs: bug fixes TARUISI Hiroaki
2009-10-02 5:39 ` [PATCH] btrfsck: Fix Check limit in check_node/leaf TARUISI Hiroaki
2009-10-02 5:52 ` [PATCH] btrfs-progs: CRC on disk printed correctly in CRC error message TARUISI Hiroaki
2009-10-02 5:52 ` [PATCH] btrfsck: CRC error case handling TARUISI Hiroaki
2009-10-02 19:09 ` 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=20091002190957.GL2881@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=taruishi.hiroak@jp.fujitsu.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