From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v2 0/2] btrfs: reflink updates
Date: Fri, 9 Jan 2026 12:29:49 +0000 [thread overview]
Message-ID: <cover.1767960735.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
Fix a bug where concurrent buffered reads with reflinks may return
unexpected zeroes when using large folios, and update a comment about
why we need to flush delalloc and wait for ordered extents before
attempting to invalidate the page cache.
V2: Updated patch 1/2 change logs and a stale comment.
Added patch 2/2.
Filipe Manana (2):
btrfs: invalidate pages instead of truncate after reflinking
btrfs: update comment for delalloc flush and oe wait in btrfs_clone_files()
fs/btrfs/reflink.c | 30 +++++++++++++++++++-----------
1 file changed, 19 insertions(+), 11 deletions(-)
--
2.47.2
next reply other threads:[~2026-01-09 12:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 12:29 fdmanana [this message]
2026-01-09 12:29 ` [PATCH v2 1/2] btrfs: invalidate pages instead of truncate after reflinking fdmanana
2026-01-11 4:11 ` Qu Wenruo
2026-01-09 12:29 ` [PATCH v2 2/2] btrfs: update comment for delalloc flush and oe wait in btrfs_clone_files() fdmanana
2026-01-09 18:07 ` Boris Burkov
2026-01-09 22:37 ` Qu Wenruo
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.1767960735.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.