From: Boris Burkov <boris@bur.io>
To: fdmanana@kernel.org
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/3] btrfs: a couple fixes for record_root_in_trans()
Date: Fri, 18 Sep 2026 10:38:20 -0700 [thread overview]
Message-ID: <20260918173820.GD2900089@zen.localdomain> (raw)
In-Reply-To: <cover.1789734239.git.fdmanana@suse.com>
On Fri, Sep 18, 2026 at 01:28:08PM +0100, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
>
> Fix a couple issues in record_root_in_trans / btrfs_record_root_in_trans()
> detected by Gemini, plus add a lockdep assertion.
Some simple nits/questions on the patches but this LGTM, please feel free to add
Reviewed-by: Boris Burkov <boris@bur.io>
Thanks,
Boris
>
> Filipe Manana (3):
> btrfs: clear BTRFS_ROOT_IN_TRANS_SETUP on early exit from record_root_in_trans()
> btrfs: fix barrier usage in btrfs_record_root_in_trans()
> btrfs: assert reloc mutex is held in record_root_in_trans()
>
> fs/btrfs/transaction.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> --
> 2.47.2
>
prev parent reply other threads:[~2026-09-18 17:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 12:28 [PATCH 0/3] btrfs: a couple fixes for record_root_in_trans() fdmanana
2026-09-18 12:28 ` [PATCH 1/3] btrfs: clear BTRFS_ROOT_IN_TRANS_SETUP on early exit from record_root_in_trans() fdmanana
2026-09-18 17:19 ` Boris Burkov
2026-09-18 17:32 ` Filipe Manana
2026-09-18 17:48 ` Boris Burkov
2026-09-18 21:46 ` Qu Wenruo
2026-09-18 12:28 ` [PATCH 2/3] btrfs: fix barrier usage in btrfs_record_root_in_trans() fdmanana
2026-09-18 17:36 ` Boris Burkov
2026-09-18 17:43 ` Filipe Manana
2026-09-18 17:47 ` Boris Burkov
2026-09-18 18:05 ` Filipe Manana
2026-09-18 18:58 ` Boris Burkov
2026-09-18 12:28 ` [PATCH 3/3] btrfs: assert reloc mutex is held in record_root_in_trans() fdmanana
2026-09-18 21:47 ` Qu Wenruo
2026-09-18 17:38 ` Boris Burkov [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=20260918173820.GD2900089@zen.localdomain \
--to=boris@bur.io \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox