From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v2 0/2] btrfs-progs: bug fixes exposed during delayed chunk items insertion
Date: Tue, 19 Apr 2022 19:17:40 +0800 [thread overview]
Message-ID: <cover.1650366929.git.wqu@suse.com> (raw)
[CHANGELOG]
v2:
- Update the first patch to delaye memory allocation after all other
checks
There are two bugs in the existing code base of btrfs-progs:
- Memory leak due to wrong error handling in btrfs_start_transaction()
- Empty rw device list due to missing error handling in create_chunk()
Just fix them.
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 | 13 +++++++------
kernel-shared/volumes.c | 15 +++++++++++++++
2 files changed, 22 insertions(+), 6 deletions(-)
--
2.35.1
next reply other threads:[~2022-04-19 11:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 11:17 Qu Wenruo [this message]
2022-04-19 11:17 ` [PATCH v2 1/2] btrfs-progs: fix a memory leak when starting a transaction on fs with error Qu Wenruo
2022-04-19 11:23 ` Johannes Thumshirn
2022-04-19 11:17 ` [PATCH v2 2/2] btrfs-progs: fix an error path which can lead to empty device list Qu Wenruo
2022-04-19 11:24 ` Johannes Thumshirn
2022-04-25 16:56 ` [PATCH v2 0/2] btrfs-progs: bug fixes exposed during delayed chunk items insertion 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.1650366929.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