public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/2] btrfs-progs: check: Detect overlapping csum item
Date: Mon, 25 May 2020 15:49:55 +0200	[thread overview]
Message-ID: <20200525134955.GU18421@twin.jikos.cz> (raw)
In-Reply-To: <20200304072701.38403-1-wqu@suse.com>

On Wed, Mar 04, 2020 at 03:26:59PM +0800, Qu Wenruo wrote:
> There is one report about tree-checker rejecting overlapping csum item.

Do you have link of the report?

I think the bug has been fixed by "btrfs: fix corrupt log due to
concurrent fsync of inodes with shared extents".

> I haven't yet seen another report, thus the problem doesn't look
> widespread, thus maybe some regression in older kernels.
> 
> At least let btrfs check to detect such problem.
> If we had another report, I'll spending extra time for the repair
> functionality (it's not that simple, as it involves a lot of csum item
> operation, and unexpected overlapping range).
> 
> Qu Wenruo (2):
>   btrfs-progs: check: Detect overlap csum items
>   btrfs-progs: fsck-tests: Add test image for overlapping csum item

Added to devel.

      parent reply	other threads:[~2020-05-25 13:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-04  7:26 [PATCH 0/2] btrfs-progs: check: Detect overlapping csum item Qu Wenruo
2020-03-04  7:27 ` [PATCH 1/2] btrfs-progs: check: Detect overlap csum items Qu Wenruo
2020-03-04  7:27 ` [PATCH 2/2] btrfs-progs: fsck-tests: Add test image for overlapping csum item Qu Wenruo
2020-05-25 13:49 ` David Sterba [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=20200525134955.GU18421@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wqu@suse.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