Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: fdmanana@kernel.org, fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org, Filipe Manana <fdmanana@suse.com>,
	Qu Wenruo <wqu@suse.com>
Subject: Re: [PATCH v2] btrfs: fix _require_btrfs_send_version to detect btrfs-progs support
Date: Sat, 13 Jul 2024 00:14:23 +0800	[thread overview]
Message-ID: <1e6827bd-a57f-4139-846e-64ca20b50b7d@oracle.com> (raw)
In-Reply-To: <f1e109784681df64d6d9fc62aa2b1952ce0bccbe.1720777916.git.fdmanana@suse.com>

On 12/07/2024 17:54, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
> 
> Commit 199d0a992536df3702a0c4843d2a449d54f399c2 ("common/btrfs: introduce
> _require_btrfs_send_version") turned _require_btrfs_send_v2 into a generic
> helper to detect support for any send stream version, however it's only
> working for detecting kernel support, it misses detecting the support from
> btrfs-progs - it always checks only that it supports v2 (the send command
> supports the --compressed-data option).
> 
> Fix that by verifying that btrfs-progs supports the requested version.
> 
> Reviewed-by: Qu Wenruo <wqu@suse.com>
> Signed-off-by: Filipe Manana <fdmanana@suse.com>
> ---
> 
> V2: Don't use -f /dev/null in the send command, just redirect stdout and
>      stderr to /dev/null.
>      Add Qu's review tag.
> 

Reviewed-by: Anand Jain <anand.jain@oracle.com>

Applied.

Thanks, Anand


>   common/btrfs | 20 ++++++++++++++++----
>   1 file changed, 16 insertions(+), 4 deletions(-)
> 
> diff --git a/common/btrfs b/common/btrfs
> index be5948db..c0be7c08 100644
> --- a/common/btrfs
> +++ b/common/btrfs
> @@ -777,17 +777,29 @@ _require_btrfs_corrupt_block()
>   _require_btrfs_send_version()
>   {
>   	local version=$1
> +	local ret
>   
> -	# Check first if btrfs-progs supports the v2 stream.
> -	_require_btrfs_command send --compressed-data
> -
> -	# Now check the kernel support. If send_stream_version does not exists,
> +	# Check the kernel support. If send_stream_version does not exists,
>   	# then it's a kernel that only supports v1.
>   	[ -f /sys/fs/btrfs/features/send_stream_version ] || \
>   		_notrun "kernel does not support send stream $version"
>   
>   	[ $(cat /sys/fs/btrfs/features/send_stream_version) -ge $version ] || \
>   		_notrun "kernel does not support send stream $version"
> +
> +	# Now check that btrfs-progs supports the requested stream version.
> +	_scratch_mkfs &> /dev/null || \
> +		_fail "mkfs failed at _require_btrfs_send_version"
> +	_scratch_mount
> +	$BTRFS_UTIL_PROG subvolume snapshot -r $SCRATCH_MNT \
> +			 $SCRATCH_MNT/snap &> /dev/null
> +	$BTRFS_UTIL_PROG send --proto $version $SCRATCH_MNT/snap &> /dev/null
> +	ret=$?
> +	_scratch_unmount
> +
> +	if [ $ret -ne 0 ]; then
> +		_notrun "btrfs-progs does not support send stream version $version"
> +	fi
>   }
>   
>   # Get the bytenr associated to a file extent item at a given file offset.


      reply	other threads:[~2024-07-12 16:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-12  0:05 [PATCH] btrfs: fix _require_btrfs_send_version to detect btrfs-progs support fdmanana
2024-07-12  0:50 ` Qu Wenruo
2024-07-12  9:54 ` [PATCH v2] " fdmanana
2024-07-12 16:14   ` Anand Jain [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=1e6827bd-a57f-4139-846e-64ca20b50b7d@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=fdmanana@kernel.org \
    --cc=fdmanana@suse.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wqu@suse.com \
    /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