linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs-progs: add new precaution check for incoming subpage support
Date: Mon,  9 Nov 2020 13:39:50 +0800	[thread overview]
Message-ID: <20201109053952.490678-1-wqu@suse.com> (raw)

For the incoming subpage support, we need to ensure no tree block could
cross 64K page boundary.

Currently both kernel and btrfs-progs won't create such tree blocks, but
still add such check as non-critical warning to catch any ancient btrfs
in the wild.

Also enhance the existing test cases to catch the warning message just
in case we miss something.

Qu Wenruo (2):
  btrfs-progs: check: detect and warn about tree blocks cross 64K page
    boundary
  btrfs-progs: tests: check the result log for critical warnings

 check/main.c           |  2 ++
 check/mode-common.h    | 18 ++++++++++++++++++
 check/mode-lowmem.c    |  2 ++
 tests/common           | 12 ++++++++++++
 tests/convert-tests.sh |  1 +
 tests/fsck-tests.sh    |  1 +
 tests/misc-tests.sh    |  1 +
 tests/mkfs-tests.sh    |  1 +
 8 files changed, 38 insertions(+)

-- 
2.29.2


             reply	other threads:[~2020-11-09  5:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-09  5:39 Qu Wenruo [this message]
2020-11-09  5:39 ` [PATCH 1/2] btrfs-progs: check: detect and warn about tree blocks cross 64K page boundary Qu Wenruo
2021-03-02  8:48   ` Wang Yugui
2021-03-02 10:14     ` Qu Wenruo
2021-03-02 10:36       ` Wang Yugui
2021-03-06  0:33         ` Qu Wenruo
2020-11-09  5:39 ` [PATCH 2/2] btrfs-progs: tests: check the result log for critical warnings Qu Wenruo
2021-02-19 14:12   ` David Sterba

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=20201109053952.490678-1-wqu@suse.com \
    --to=wqu@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).