From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] btrfs: a couple bug fixes around reflinks and fallocate
Date: Mon, 6 Jun 2022 10:41:16 +0100 [thread overview]
Message-ID: <cover.1654508104.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
This patchset fixes a couple of bugs, the first one exclusive for reflink
operations while the second one applies to reflink, fallocate and hole
punching operations. Finally the third patch just removes some BUG_ON()s
that are really not needed.
All the patches are independent of each other, they could have been sent
out as individual patches.
Filipe Manana (3):
btrfs: fix race between reflinking and ordered extent completion
btrfs: add missing inode updates on each iteration when replacing
extents
btrfs: do not BUG_ON() on failure to migrate space when replacing
extents
fs/btrfs/ctree.h | 2 ++
fs/btrfs/file.c | 25 +++++++++++++++++++++++--
fs/btrfs/inode.c | 1 +
fs/btrfs/reflink.c | 16 ++++++++++++----
4 files changed, 38 insertions(+), 6 deletions(-)
--
2.35.1
next reply other threads:[~2022-06-06 9:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 9:41 fdmanana [this message]
2022-06-06 9:41 ` [PATCH 1/3] btrfs: fix race between reflinking and ordered extent completion fdmanana
2022-06-06 21:36 ` Boris Burkov
2022-06-06 9:41 ` [PATCH 2/3] btrfs: add missing inode updates on each iteration when replacing extents fdmanana
2022-06-06 22:11 ` Boris Burkov
2022-06-07 9:31 ` Filipe Manana
2022-06-07 16:41 ` Boris Burkov
2022-06-06 9:41 ` [PATCH 3/3] btrfs: do not BUG_ON() on failure to migrate space " fdmanana
2022-06-07 16:44 ` Boris Burkov
2022-06-06 20:45 ` [PATCH 0/3] btrfs: a couple bug fixes around reflinks and fallocate 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.1654508104.git.fdmanana@suse.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.