From: Jeff Layton <jlayton@kernel.org>
To: Leo Martins <loemra.dev@gmail.com>,
linux-btrfs@vger.kernel.org, kernel-team@fb.com
Cc: Filipe Manana <fdmanana@suse.com>,
David Sterba <dsterba@suse.com>, Boris Burkov <boris@bur.io>
Subject: Re: [PATCH] btrfs: don't propagate EXTENT_FLAG_LOGGING to split extent maps
Date: Tue, 30 Jun 2026 16:58:58 -0400 [thread overview]
Message-ID: <b7e8ecee4deb064e1d9c1b9977aed0c0c26a373b.camel@kernel.org> (raw)
In-Reply-To: <77d71e99f792c80c4841b33ed07530543dca897a.1782849374.git.loemra.dev@gmail.com>
On Tue, 2026-06-30 at 12:58 -0700, Leo Martins wrote:
> When btrfs_drop_extent_map_range() splits an extent map, the new split
> maps inherit the original map's flags through a local 'flags' variable.
> Commit f86f7a75e2fb ("btrfs: use the flags of an extent map to identify
> the compression type") changed the EXTENT_FLAG_LOGGING clearing to
> operate on em->flags instead of that local 'flags' copy, so a split of
> an extent map that is currently being logged wrongly inherits
> EXTENT_FLAG_LOGGING.
>
> The flag is then never cleared on the split, and when it is freed while
> still on the inode's modified_extents list (for example by the extent
> map shrinker) it trips the WARN_ON(!list_empty(&em->list)) in
> btrfs_free_extent_map() and leads to a use-after-free.
>
> Clear EXTENT_FLAG_LOGGING from the local 'flags' copy used for the
> splits and only clear EXTENT_FLAG_PINNED from em->flags, restoring the
> behaviour prior to f86f7a75e2fb.
>
> Fixes: f86f7a75e2fb ("btrfs: use the flags of an extent map to identify the compression type")
> Cc: Jeff Layton <jlayton@kernel.org>
> Cc: Boris Burkov <boris@bur.io>
> Signed-off-by: Leo Martins <loemra.dev@gmail.com>
> ---
> fs/btrfs/extent_map.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/btrfs/extent_map.c b/fs/btrfs/extent_map.c
> index fce9c5cc0122..6ad7b39ae358 100644
> --- a/fs/btrfs/extent_map.c
> +++ b/fs/btrfs/extent_map.c
> @@ -866,13 +866,13 @@ void btrfs_drop_extent_map_range(struct btrfs_inode *inode, u64 start, u64 end,
> goto next;
> }
>
> - flags = em->flags;
> /*
> * In case we split the extent map, we want to preserve the
> * EXTENT_FLAG_LOGGING flag on our extent map, but we don't want
> * it on the new extent maps.
> */
> - em->flags &= ~(EXTENT_FLAG_PINNED | EXTENT_FLAG_LOGGING);
> + flags = em->flags & ~EXTENT_FLAG_LOGGING;
> + em->flags &= ~EXTENT_FLAG_PINNED;
> modified = !list_empty(&em->list);
>
> /*
Reviewed-by: Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2026-06-30 20:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 19:58 [PATCH] btrfs: don't propagate EXTENT_FLAG_LOGGING to split extent maps Leo Martins
2026-06-30 20:58 ` Jeff Layton [this message]
2026-07-01 10:48 ` Filipe Manana
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=b7e8ecee4deb064e1d9c1b9977aed0c0c26a373b.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=boris@bur.io \
--cc=dsterba@suse.com \
--cc=fdmanana@suse.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=loemra.dev@gmail.com \
/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