From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v3 0/3] btrfs: fix mmap writes for NOCOW files/extents
Date: Wed, 9 Jul 2025 12:45:38 +0100 [thread overview]
Message-ID: <cover.1752061083.git.fdmanana@suse.com> (raw)
In-Reply-To: <cover.1752050704.git.fdmanana@suse.com>
From: Filipe Manana <fdmanana@suse.com>
A bug fix and a couple cleanups. Details in the individual change logs.
V2: Fix a bug in patch 1/3 where if write_bytes < reserved_space we would
exit without unlocking the cow lock, so set only_release_metadata to
true before bailing out in that case.
Added Qu's review tags.
V3: Add missing release of metadata reserved space in case we fall
back to NOCOW mode and we are in a folio that contains i_size
somewhere in its middle
Filipe Manana (3):
btrfs: fix -ENOSPC mmap write failure on NOCOW files/extents
btrfs: use variable for io_tree when clearing range in btrfs_page_mkwrite()
btrfs: use btrfs_inode local variable at btrfs_page_mkwrite()
fs/btrfs/file.c | 93 +++++++++++++++++++++++++++++++++++--------------
1 file changed, 66 insertions(+), 27 deletions(-)
--
2.47.2
next prev parent reply other threads:[~2025-07-09 11:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 8:53 [PATCH 0/3] btrfs: fix mmap writes for NOCOW files/extents fdmanana
2025-07-09 8:53 ` [PATCH 1/3] btrfs: fix -ENOSPC mmap write failure on " fdmanana
2025-07-09 10:02 ` Qu Wenruo
2025-07-09 10:36 ` Filipe Manana
2025-07-09 8:53 ` [PATCH 2/3] btrfs: use variable for io_tree when clearing range in btrfs_page_mkwrite() fdmanana
2025-07-09 10:02 ` Qu Wenruo
2025-07-09 8:53 ` [PATCH 3/3] btrfs: use btrfs_inode local variable at btrfs_page_mkwrite() fdmanana
2025-07-09 10:04 ` Qu Wenruo
2025-07-09 10:39 ` Filipe Manana
2025-07-09 11:13 ` [PATCH v2 0/3] btrfs: fix mmap writes for NOCOW files/extents fdmanana
2025-07-09 11:13 ` [PATCH v2 1/3] btrfs: fix -ENOSPC mmap write failure on " fdmanana
2025-07-09 11:13 ` [PATCH v2 2/3] btrfs: use variable for io_tree when clearing range in btrfs_page_mkwrite() fdmanana
2025-07-09 11:13 ` [PATCH v2 3/3] btrfs: use btrfs_inode local variable at btrfs_page_mkwrite() fdmanana
2025-07-09 11:45 ` fdmanana [this message]
2025-07-09 11:45 ` [PATCH v3 1/3] btrfs: fix -ENOSPC mmap write failure on NOCOW files/extents fdmanana
2025-07-09 11:45 ` [PATCH v3 2/3] btrfs: use variable for io_tree when clearing range in btrfs_page_mkwrite() fdmanana
2025-07-09 11:45 ` [PATCH v3 3/3] btrfs: use btrfs_inode local variable at btrfs_page_mkwrite() fdmanana
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.1752061083.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox