All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.12.y] btrfs: fix block group refcount race in btrfs_create_pending_block_groups()
Date: Fri, 18 Jul 2025 09:29:44 -0400	[thread overview]
Message-ID: <1752844937-f98ec06c@stable.kernel.org> (raw)
In-Reply-To: <tencent_C3ACCD708660161A98683D6A583E30255109@qq.com>

[ Sasha's backport helper bot ]

Hi,

✅ All tests passed successfully. No issues detected.
No action required from the submitter.

The upstream commit SHA1 provided is correct: 2d8e5168d48a91e7a802d3003e72afb4304bebfa

WARNING: Author mismatch between patch and upstream commit:
Backport author: <alvalan9@foxmail.com>
Commit author: Boris Burkov <boris@bur.io>

Status in newer kernel trees:
6.15.y | Present (exact SHA1)

Note: The patch differs from the upstream commit:
---
1:  2d8e5168d48a ! 1:  7e8e9017eb32 btrfs: fix block group refcount race in btrfs_create_pending_block_groups()
    @@ Metadata
      ## Commit message ##
         btrfs: fix block group refcount race in btrfs_create_pending_block_groups()
     
    +    [ Upstream commit 2d8e5168d48a91e7a802d3003e72afb4304bebfa ]
    +
         Block group creation is done in two phases, which results in a slightly
         unintuitive property: a block group can be allocated/deallocated from
         after btrfs_make_block_group() adds it to the space_info with
    @@ Commit message
         Reviewed-by: Filipe Manana <fdmanana@suse.com>
         Signed-off-by: Boris Burkov <boris@bur.io>
         Signed-off-by: David Sterba <dsterba@suse.com>
    +    Signed-off-by: Alva Lan <alvalan9@foxmail.com>
     
      ## fs/btrfs/block-group.c ##
     @@ fs/btrfs/block-group.c: void btrfs_create_pending_block_groups(struct btrfs_trans_handle *trans)

---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| origin/linux-6.12.y       | Success     | Success    |

      reply	other threads:[~2025-07-18 13:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-18  2:59 [PATCH 6.12.y] btrfs: fix block group refcount race in btrfs_create_pending_block_groups() alvalan9
2025-07-18 13:29 ` Sasha Levin [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=1752844937-f98ec06c@stable.kernel.org \
    --to=sashal@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 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.