From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v2 0/4] btrfs: some minor fixes around extent maps
Date: Wed, 13 Mar 2024 17:28:18 +0000 [thread overview]
Message-ID: <cover.1710350741.git.fdmanana@suse.com> (raw)
In-Reply-To: <cover.1710335452.git.fdmanana@suse.com>
From: Filipe Manana <fdmanana@suse.com>
Some minor fixes around extent maps for unexpected error cases.
More details in the change logs.
V2: Added patch 4/4.
Filipe Manana (4):
btrfs: fix extent map leak in unexpected scenario at unpin_extent_cache()
btrfs: fix warning messages not printing interval at unpin_extent_range()
btrfs: fix message not properly printing interval when adding extent map
btrfs: use btrfs_warn() to log message at btrfs_add_extent_mapping()
fs/btrfs/extent_map.c | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
--
2.43.0
next prev parent reply other threads:[~2024-03-13 17:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 13:20 [PATCH 0/3] btrfs: some minor fixes around extent maps fdmanana
2024-03-13 13:20 ` [PATCH 1/3] btrfs: fix extent map leak in unexpected scenario at unpin_extent_cache() fdmanana
2024-03-13 13:20 ` [PATCH 2/3] btrfs: fix warning messages not printing interval at unpin_extent_range() fdmanana
2024-03-13 13:20 ` [PATCH 3/3] btrfs: fix message not properly printing interval when adding extent map fdmanana
2024-03-13 17:28 ` fdmanana [this message]
2024-03-13 17:28 ` [PATCH v2 1/4] btrfs: fix extent map leak in unexpected scenario at unpin_extent_cache() fdmanana
2024-03-14 12:59 ` Anand Jain
2024-03-13 17:28 ` [PATCH v2 2/4] btrfs: fix warning messages not printing interval at unpin_extent_range() fdmanana
2024-03-13 17:28 ` [PATCH v2 3/4] btrfs: fix message not properly printing interval when adding extent map fdmanana
2024-03-13 17:28 ` [PATCH v2 4/4] btrfs: use btrfs_warn() to log message at btrfs_add_extent_mapping() fdmanana
2024-03-13 19:22 ` [PATCH v2 0/4] btrfs: some minor fixes around extent maps Qu Wenruo
2024-03-14 13:06 ` Anand Jain
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.1710350741.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