From: Eryu Guan <guaneryu@gmail.com>
To: Eric Biggers <ebiggers@google.com>
Cc: fstests@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH] common/config: support f2fs-tools v1.9 and later
Date: Sat, 7 Apr 2018 23:29:52 +0800 [thread overview]
Message-ID: <20180407152952.GP30836@localhost.localdomain> (raw)
In-Reply-To: <20180405221901.41861-1-ebiggers@google.com>
On Thu, Apr 05, 2018 at 03:19:01PM -0700, Eric Biggers wrote:
> Pass the -f option to mkfs.f2fs when it appears to support it. This is
> required by f2fs-tools v1.9 and later in order to format the filesystem
> even when an existing filesystem is detected. But earlier versions did
> not accept this option.
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
Looks fine to me, but I'd like an ACK from f2fs developers.
> ---
> common/config | 11 ++++++-----
> 1 file changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/common/config b/common/config
> index 20f0e5f3..7c046a78 100644
> --- a/common/config
> +++ b/common/config
> @@ -94,10 +94,11 @@ set_prog_path()
> type -P $1
> }
>
> -# Handle mkfs.btrfs which does (or does not) require -f to overwrite
> -set_btrfs_mkfs_prog_path_with_opts()
> +# Handle mkfs.$fstyp which does (or does not) require -f to overwrite
> +set_mkfs_prog_path_with_opts()
> {
> - p=`set_prog_path mkfs.btrfs`
> + local fstyp=$1
> + local p=`set_prog_path mkfs.$fstyp`
> if [ "$p" != "" ] && grep -q 'force overwrite' $p; then
Also grep the "$p -h" output instead of the binary file?
Thanks,
Eryu
> echo "$p -f"
> else
> @@ -223,8 +224,8 @@ case "$HOSTOS" in
> export MKFS_XFS_PROG="`set_prog_path mkfs.xfs`"
> export MKFS_EXT4_PROG="`set_prog_path mkfs.ext4`"
> export MKFS_UDF_PROG="`set_prog_path mkudffs`"
> - export MKFS_BTRFS_PROG="`set_btrfs_mkfs_prog_path_with_opts`"
> - export MKFS_F2FS_PROG="`set_prog_path mkfs.f2fs`"
> + export MKFS_BTRFS_PROG="`set_mkfs_prog_path_with_opts btrfs`"
> + export MKFS_F2FS_PROG="`set_mkfs_prog_path_with_opts f2fs`"
> export DUMP_F2FS_PROG="`set_prog_path dump.f2fs`"
> export BTRFS_UTIL_PROG="`set_prog_path btrfs`"
> export BTRFS_SHOW_SUPER_PROG="`set_prog_path btrfs-show-super`"
> --
> 2.17.0.484.g0c8726318c-goog
>
> --
> To unsubscribe from this list: send the line "unsubscribe fstests" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
next prev parent reply other threads:[~2018-04-07 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 22:19 [PATCH] common/config: support f2fs-tools v1.9 and later Eric Biggers via Linux-f2fs-devel
2018-04-07 15:29 ` Eryu Guan [this message]
2018-04-09 2:33 ` Chao Yu
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=20180407152952.GP30836@localhost.localdomain \
--to=guaneryu@gmail.com \
--cc=ebiggers@google.com \
--cc=fstests@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).