Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Guanghui Yang <3497809730@qq.com>
Cc: linux-btrfs@vger.kernel.org, Chris Mason <clm@fb.com>,
	David Sterba <dsterba@suse.com>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] btrfs: drop recovered reloc root refs on recovery failure
Date: Mon, 20 Jul 2026 13:19:13 +0200	[thread overview]
Message-ID: <20260720111913.GE10684@twin.jikos.cz> (raw)
In-Reply-To: <tencent_73CA9825AA069E0BC5194FA9102FB7618807@qq.com>

On Sun, Jul 12, 2026 at 04:22:32AM +0000, Guanghui Yang wrote:
> During relocation recovery, each fs root gets a reference to its relocation
> root. If loading or adding a later root fails, or if the first transaction
> commit fails, btrfs_recover_relocation() jumps to out_unset before
> merge_reloc_roots() and clean_dirty_subvols().
> 
> put_reloc_control() drops the list-owned relocation root references, but it
> does not clear fs_root->reloc_root or drop the references owned by those
> pointers. Mount cleanup only drops them when BTRFS_FS_ERROR is set, so an
> error such as -ENOMEM while processing a later root can leave references
> behind.
> 
> Keep temporary references to the fs roots associated during recovery. On
> failure, clear their reloc_root pointers and drop the corresponding
> references. Once the first transaction commit succeeds, drop only the
> temporary fs root references and let the normal merge and cleanup paths
> handle the relocation roots.
> 
> Fault injection on a pending-relocation image confirmed the cleanup gap.
> With an injected first-commit failure, 25 fs roots had reloc_root set with
> fs_error=0. With this fix, the same failure path drops that count to 0
> before mount fails.
> 
> Fixes: f44deb7442ed ("btrfs: hold a ref on the root->reloc_root")
> Cc: stable@vger.kernel.org
> Signed-off-by: Guanghui Yang <3497809730@qq.com>

Added to for-next, thanks.

      reply	other threads:[~2026-07-20 11:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-12  4:22 [PATCH] btrfs: drop recovered reloc root refs on recovery failure Guanghui Yang
2026-07-20 11:19 ` 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=20260720111913.GE10684@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=3497809730@qq.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@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