From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs-progs: bug fixes exposed during delayed chunk items insertion
Date: Mon, 18 Apr 2022 21:10:06 +0800 [thread overview]
Message-ID: <cover.1650287150.git.wqu@suse.com> (raw)
I'm recently working on a prototype on seed device sprout at mkfs time,
and one core feature for it is delayed chunk item insertion.
Currently the delayed chunk item insertion is done, and mkfs sprout
prototype is pretty close to finish.
But during the development, I exposed some bugs in error handling path,
especially the 2nd one is exposed during testing, and it's there for a
while, affecting existing code base.
Currently my delayed chunk item insertion can survive all mkfs and fsck
tests, so I don't expect more bugs exposed, thus it's time for the pure
bug fixes first.
Qu Wenruo (2):
btrfs-progs: fix a memory leak when starting a transaction on fs with
error
btrfs-progs: fix an error path which can lead to empty device list
kernel-shared/transaction.c | 6 ++++--
kernel-shared/volumes.c | 15 +++++++++++++++
2 files changed, 19 insertions(+), 2 deletions(-)
--
2.35.1
next reply other threads:[~2022-04-18 14:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 13:10 Qu Wenruo [this message]
2022-04-18 13:10 ` [PATCH 1/2] btrfs-progs: fix a memory leak when starting a transaction on fs with error Qu Wenruo
2022-04-18 15:26 ` Josef Bacik
2022-04-19 5:09 ` Andrei Borzenkov
2022-04-19 6:42 ` Qu Wenruo
2022-04-18 13:10 ` [PATCH 2/2] btrfs-progs: fix an error path which can lead to empty device list Qu Wenruo
2022-04-18 15:28 ` Josef Bacik
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.1650287150.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