From: Nikolay Borisov <nborisov@suse.com>
To: fdmanana@kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/3] btrfs: fixes for an error path when creating a subvolume
Date: Mon, 13 Dec 2021 13:22:19 +0200 [thread overview]
Message-ID: <ad13deb8-a5cf-7a4f-9866-046d1413cce7@suse.com> (raw)
In-Reply-To: <cover.1639384875.git.fdmanana@suse.com>
On 13.12.21 г. 10:45, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
>
> The following patches fix an error path when creating a subvolume, exposed
> by generic/475.
>
> Filipe Manana (3):
> btrfs: fix invalid delayed ref after subvolume creation failure
> btrfs: fix warning when freeing leaf after subvolume creation failure
> btrfs: skip transaction commit after failure to create subvolume
>
> fs/btrfs/ctree.c | 17 +++++++++--------
> fs/btrfs/ctree.h | 7 ++++++-
> fs/btrfs/extent-tree.c | 13 +++++++------
> fs/btrfs/free-space-tree.c | 4 ++--
> fs/btrfs/ioctl.c | 18 ++++++++++--------
> fs/btrfs/qgroup.c | 3 ++-
> 6 files changed, 36 insertions(+), 26 deletions(-)
>
For the whole series :
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
next prev parent reply other threads:[~2021-12-13 11:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 8:45 [PATCH 0/3] btrfs: fixes for an error path when creating a subvolume fdmanana
2021-12-13 8:45 ` [PATCH 1/3] btrfs: fix invalid delayed ref after subvolume creation failure fdmanana
2021-12-13 8:45 ` [PATCH 2/3] btrfs: fix warning when freeing leaf " fdmanana
2021-12-13 8:45 ` [PATCH 3/3] btrfs: skip transaction commit after failure to create subvolume fdmanana
2021-12-13 11:22 ` Nikolay Borisov [this message]
2021-12-14 14:39 ` [PATCH 0/3] btrfs: fixes for an error path when creating a subvolume 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=ad13deb8-a5cf-7a4f-9866-046d1413cce7@suse.com \
--to=nborisov@suse.com \
--cc=fdmanana@kernel.org \
--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).