All of lore.kernel.org
 help / color / mirror / Atom feed
From: Su Yue <l@damenly.su>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/4] btrfs-progs: check: add the ability to detect and report mixed inline and regular data extents
Date: Tue, 04 May 2021 21:30:55 +0800	[thread overview]
Message-ID: <8s4upque.fsf@damenly.su> (raw)
In-Reply-To: <20210504062525.152540-1-wqu@suse.com>


On Tue 04 May 2021 at 14:25, Qu Wenruo <wqu@suse.com> wrote:

> Btrfs check original mode can't detect mixed inline and regular 
> data
> extents at all, while lowmem mode reports the problem as hole 
> gap, not
> to the point.
>
> This patchset will add the ability to detect such problem, with 
> a test
> image dumped from subpage branch (with the inline extent disable 
> patch
> reverted).
>
> The patchset is here to detect such problem exposed during 
> subpage
> development, while also acts as the final safenet to catch such 
> mixed
> types bug.
>
> Qu Wenruo (4):
>   btrfs-progs: check/original: add the "0x" prefix for hex error 
>   number
>   btrfs-progs: check/original: detect and report mixed inline 
>   and
>     regular data extents
>   btrfs-progs: check/lowmem: detect and report mixed inline and 
>   regular
>     extents properly
>   btrfs-progs: fsck-tests: add test image for mixed inline and 
>   regular
>     data extents
>
For the series,
Reviewed-by: Su Yue <l@damenly.su>

--
Su
>  check/main.c                                  |   7 +++-
>  check/mode-lowmem.c                           |  31 
>  +++++++++++++++---
>  check/mode-original.h                         |   2 ++
>  .../047-mixed-extent-types/default.img.xz     | Bin 0 -> 2112 
>  bytes
>  .../fsck-tests/047-mixed-extent-types/test.sh |  19 +++++++++++
>  5 files changed, 54 insertions(+), 5 deletions(-)
>  create mode 100644 
>  tests/fsck-tests/047-mixed-extent-types/default.img.xz
>  create mode 100755 
>  tests/fsck-tests/047-mixed-extent-types/test.sh


  parent reply	other threads:[~2021-05-04 13:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-04  6:25 [PATCH 0/4] btrfs-progs: check: add the ability to detect and report mixed inline and regular data extents Qu Wenruo
2021-05-04  6:25 ` [PATCH 1/4] btrfs-progs: check/original: add the "0x" prefix for hex error number Qu Wenruo
2021-05-04  6:25 ` [PATCH 2/4] btrfs-progs: check/original: detect and report mixed inline and regular data extents Qu Wenruo
2021-05-04  6:25 ` [PATCH 3/4] btrfs-progs: check/lowmem: detect and report mixed inline and regular extents properly Qu Wenruo
2021-05-04  6:25 ` [PATCH 4/4] btrfs-progs: fsck-tests: add test image for mixed inline and regular data extents Qu Wenruo
2021-05-04 13:30 ` Su Yue [this message]
2021-05-06 13:02 ` [PATCH 0/4] btrfs-progs: check: add the ability to detect and report " Qu Wenruo

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=8s4upque.fsf@damenly.su \
    --to=l@damenly.su \
    --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 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.