From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] btrfs: some fixes related to the extent map shrinker
Date: Sun, 16 Feb 2025 13:16:02 +0000 [thread overview]
Message-ID: <cover.1739710434.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
A few fixes and improvements for the extent map shrinker. The first is a
use-after-free that is likely hard to hit and the other two fixes make
things more efficient by avoiding grabbing and dropping (iput) inodes
which don't have extent maps loaded as well as eleminating the need to
do delayed iputs, as that's not needed anymore.
These are related to a recent report from Ivan Shapovalov where the
cleaner kthread was using over 50% of CPU doing a lot of delayed iputs:
https://lore.kernel.org/linux-btrfs/0414d690ac5680d0d77dfc930606cdc36e42e12f.camel@intelfx.name/
More details in the change logs.
Filipe Manana (3):
btrfs: fix use-after-free on inode when scanning root during em shrinking
btrfs: skip inodes without loaded extent maps when shrinking extent maps
btrfs: do regular iput instead of delayed iput during extent map shrinking
fs/btrfs/extent_map.c | 82 ++++++++++++++++++++++++++++++-------------
1 file changed, 58 insertions(+), 24 deletions(-)
--
2.45.2
next reply other threads:[~2025-02-16 13:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-16 13:16 fdmanana [this message]
2025-02-16 13:16 ` [PATCH 1/3] btrfs: fix use-after-free on inode when scanning root during em shrinking fdmanana
2025-02-17 17:47 ` Johannes Thumshirn
2025-02-16 13:16 ` [PATCH 2/3] btrfs: skip inodes without loaded extent maps when shrinking extent maps fdmanana
2025-02-18 6:18 ` Johannes Thumshirn
2025-02-18 10:19 ` Filipe Manana
2025-02-16 13:16 ` [PATCH 3/3] btrfs: do regular iput instead of delayed iput during extent map shrinking fdmanana
2025-02-18 6:18 ` Johannes Thumshirn
2025-02-17 21:56 ` [PATCH 0/3] btrfs: some fixes related to the extent map shrinker 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.1739710434.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.