public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Boris Burkov <boris@bur.io>
To: fdmanana@kernel.org
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/5] btrfs: fixes and cleanups for ordered extent allocation
Date: Thu, 8 May 2025 09:20:36 -0700	[thread overview]
Message-ID: <20250508162036.GD3935696@zen.localdomain> (raw)
In-Reply-To: <cover.1746638347.git.fdmanana@suse.com>

On Wed, May 07, 2025 at 06:23:12PM +0100, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
> 
> Some fixes and cleanups around ordered extent allocation. Details in the
> change logs.

Now that we discussed the first patch in detail,
Reviewed-by: Boris Burkov <boris@bur.io>

> 
> Filipe Manana (5):
>   btrfs: fix qgroup reservation leak on failure to allocate ordered extent
>   btrfs: check we grabbed inode reference when allocating an ordered extent
>   btrfs: fold error checks when allocating ordered extent and update comments
>   btrfs: use boolean for delalloc argument to btrfs_free_reserved_bytes()
>   btrfs: use boolean for delalloc argument to btrfs_free_reserved_extent()
> 
>  fs/btrfs/block-group.c  | 10 ++++----
>  fs/btrfs/block-group.h  |  2 +-
>  fs/btrfs/direct-io.c    |  3 +--
>  fs/btrfs/extent-tree.c  |  8 +++----
>  fs/btrfs/extent-tree.h  |  2 +-
>  fs/btrfs/inode.c        | 10 ++++----
>  fs/btrfs/ordered-data.c | 51 ++++++++++++++++++++++++++---------------
>  7 files changed, 50 insertions(+), 36 deletions(-)
> 
> -- 
> 2.47.2
> 

      parent reply	other threads:[~2025-05-08 16:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-07 17:23 [PATCH 0/5] btrfs: fixes and cleanups for ordered extent allocation fdmanana
2025-05-07 17:23 ` [PATCH 1/5] btrfs: fix qgroup reservation leak on failure to allocate ordered extent fdmanana
2025-05-07 22:33   ` Boris Burkov
2025-05-07 23:11     ` Qu Wenruo
2025-05-07 23:39       ` Boris Burkov
2025-05-08  0:08         ` Boris Burkov
2025-05-08 13:43       ` Filipe Manana
2025-05-08 16:07         ` Boris Burkov
2025-05-08 21:57         ` Qu Wenruo
2025-05-08 13:40     ` Filipe Manana
2025-05-08 16:19       ` Boris Burkov
2025-05-07 17:23 ` [PATCH 2/5] btrfs: check we grabbed inode reference when allocating an " fdmanana
2025-05-07 17:23 ` [PATCH 3/5] btrfs: fold error checks when allocating ordered extent and update comments fdmanana
2025-05-07 17:23 ` [PATCH 4/5] btrfs: use boolean for delalloc argument to btrfs_free_reserved_bytes() fdmanana
2025-05-07 17:23 ` [PATCH 5/5] btrfs: use boolean for delalloc argument to btrfs_free_reserved_extent() fdmanana
2025-05-08 16:20 ` 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=20250508162036.GD3935696@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