From: David Sterba <dsterba@suse.cz>
To: Mark Harmstone <mark@harmstone.com>
Cc: linux-btrfs@vger.kernel.org, boris@bur.io, Chris Mason <clm@fb.com>
Subject: Re: [PATCH] btrfs: read key again after incrementing slot in move_existing_remaps()
Date: Fri, 27 Feb 2026 01:02:54 +0100 [thread overview]
Message-ID: <20260227000254.GI26902@twin.jikos.cz> (raw)
In-Reply-To: <20260225103610.18494-1-mark@harmstone.com>
On Wed, Feb 25, 2026 at 10:36:06AM +0000, Mark Harmstone wrote:
> Fix move_existing_remaps() so that if we increment the slot because the
> key we encounter isn't a REMAP_BACKREF, we don't reuse the objectid and
> offset of the old item.
>
> Link: https://lore.kernel.org/linux-btrfs/20260125123908.2096548-1-clm@meta.com/
> Reported-by: Chris Mason <clm@fb.com>
> Fixes: bbea42dfb91f ("btrfs: move existing remaps before relocating block group")
> Signed-off-by: Mark Harmstone <mark@harmstone.com>
Added to for-next, thanks.
prev parent reply other threads:[~2026-02-27 0:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 10:36 [PATCH] btrfs: read key again after incrementing slot in move_existing_remaps() Mark Harmstone
2026-02-25 11:32 ` Johannes Thumshirn
2026-02-27 0:02 ` David Sterba [this message]
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=20260227000254.GI26902@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=boris@bur.io \
--cc=clm@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mark@harmstone.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