public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH 0/4] Transaction aborts in free-space-tree.c
Date: Wed, 30 Apr 2025 18:45:17 +0200	[thread overview]
Message-ID: <cover.1746031378.git.dsterba@suse.com> (raw)

Fix the transaction abort pattern in free-space-tree, it's been there
from the beginning and not conforming to the pattern we use elsewhere.

David Sterba (4):
  btrfs: move transaction aborts to the error site in
    convert_free_space_to_bitmaps()
  btrfs: move transaction aborts to the error site in
    convert_free_space_to_extents()
  btrfs: move transaction aborts to the error site in
    remove_from_free_space_tree()
  btrfs: move transaction aborts to the error site in
    add_to_free_space_tree()

 fs/btrfs/free-space-tree.c | 48 +++++++++++++++++++++++++-------------
 1 file changed, 32 insertions(+), 16 deletions(-)

-- 
2.49.0


             reply	other threads:[~2025-04-30 16:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-30 16:45 David Sterba [this message]
2025-04-30 16:45 ` [PATCH 1/4] btrfs: move transaction aborts to the error site in convert_free_space_to_bitmaps() David Sterba
2025-04-30 16:45 ` [PATCH 2/4] btrfs: move transaction aborts to the error site in convert_free_space_to_extents() David Sterba
2025-04-30 16:45 ` [PATCH 3/4] btrfs: move transaction aborts to the error site in remove_from_free_space_tree() David Sterba
2025-04-30 16:45 ` [PATCH 4/4] btrfs: move transaction aborts to the error site in add_to_free_space_tree() David Sterba
2025-05-02 13:15 ` [PATCH 0/4] Transaction aborts in free-space-tree.c Daniel Vacek
2025-05-02 13:24   ` David Sterba
2025-05-02 13:32     ` Daniel Vacek
2025-05-02 14:31       ` David Sterba
2025-05-02 15:10         ` Daniel Vacek

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=cover.1746031378.git.dsterba@suse.com \
    --to=dsterba@suse.com \
    --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