linux-kernel - Re: [PATCH 2/2] btrfs: reserve new relocation zone after successful relocation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Wed, 15 May 2024 18:01:08 +0000
From: Naohiro Aota <Naohiro.Aota@....com>
To: Johannes Thumshirn <jth@...nel.org>
CC: Chris Mason <clm@...com>, Josef Bacik <josef@...icpanda.com>, David Sterba
	<dsterba@...e.com>, Hans Holmberg <Hans.Holmberg@....com>,
	"linux-btrfs@...r.kernel.org" <linux-btrfs@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Johannes
 Thumshirn <Johannes.Thumshirn@....com>
Subject: Re: [PATCH 2/2] btrfs: reserve new relocation zone after successful
 relocation

On Tue, May 14, 2024 at 11:13:22PM +0200, Johannes Thumshirn wrote:
> From: Johannes Thumshirn <johannes.thumshirn@....com>
> 
> After we've committed a relocation transaction, we know we have just freed
> up space. Set it as hint for the next relocation.
> 
> Signed-off-by: Johannes Thumshirn <johannes.thumshirn@....com>
> ---
>  fs/btrfs/relocation.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/fs/btrfs/relocation.c b/fs/btrfs/relocation.c
> index 8b24bb5a0aa1..d943abf5cb33 100644
> --- a/fs/btrfs/relocation.c
> +++ b/fs/btrfs/relocation.c
> @@ -3808,9 +3808,13 @@ static noinline_for_stack int relocate_block_group(struct reloc_control *rc)
>  		err = PTR_ERR(trans);
>  		goto out_free;
>  	}
> +
>  	ret = btrfs_commit_transaction(trans);
>  	if (ret && !err)
>  		err = ret;
> +
> +	/* We know we have just freed space, set it as hint for the next relocation */
> +	btrfs_reserve_relocation_zone(fs_info);

With "if (!err)"? We definitely bail out fast in an error case.

>  out_free:
>  	ret = clean_dirty_subvols(rc);
>  	if (ret < 0 && !err)
> 
> -- 
> 2.35.3
>