Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v2 0/4] btrfs-progs: small bug fixes
Date: Wed,  5 Jun 2024 09:13:40 +0930	[thread overview]
Message-ID: <cover.1717544015.git.wqu@suse.com> (raw)

3 fixes for 3 github issues.

Meanwhile the last one fix a test failure which always fails on my VM
(cause by one bug inside the test case), but it never fails on the
github CI (as the kernel commits two transactions, causing slot change).

[Pull request]
https://github.com/kdave/btrfs-progs/pull/807

[Changelog]
v2:
- Concentrate all small fixes into a patchset
- Update the last patch to handle multiple transactions

Qu Wenruo (4):
  btrfs-progs: corrupt-block: fix memory leak in debug_corrupt_sector()
  btrfs-progs: print-tree: do sanity checks for dir items
  btrfs-progs: error out immediately if an unknown backref type is hit
  btrfs-progs: fix misc/038 test cases

 btrfs-corrupt-block.c                            |  7 ++++---
 kernel-shared/backref.c                          |  3 ++-
 kernel-shared/print-tree.c                       |  5 +++++
 .../038-backup-root-corruption/test.sh           | 16 ++++++++++++----
 4 files changed, 23 insertions(+), 8 deletions(-)

--
2.45.2


             reply	other threads:[~2024-06-04 23:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04 23:43 Qu Wenruo [this message]
2024-06-04 23:43 ` [PATCH v2 1/4] btrfs-progs: corrupt-block: fix memory leak in debug_corrupt_sector() Qu Wenruo
2024-06-04 23:43 ` [PATCH v2 2/4] btrfs-progs: print-tree: do sanity checks for dir items Qu Wenruo
2024-06-04 23:43 ` [PATCH v2 3/4] btrfs-progs: error out immediately if an unknown backref type is hit Qu Wenruo
2024-06-04 23:43 ` [PATCH v2 4/4] btrfs-progs: fix misc/038 test cases Qu Wenruo
2024-06-05 17:57 ` [PATCH v2 0/4] btrfs-progs: small bug fixes 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=cover.1717544015.git.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