From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: An Long <lan@suse.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH v2 1/2] common/rc: add _parse_size_string
Date: Thu, 16 Jun 2022 11:25:09 -0400 [thread overview]
Message-ID: <874k0ky6ju.fsf@collabora.com> (raw)
In-Reply-To: <20220616043845.14320-2-lan@suse.com> (An Long's message of "Thu, 16 Jun 2022 12:38:44 +0800")
An Long <lan@suse.com> writes:
> + if [[ $str =~ ^[0-9]+[a-zA-Z]$ ]] ; then
> + size=${str:: -1}
> + endchar=${str: -1}
> + case $endchar in
> + e|E)
> + mult=$((mult * 1024))
> + ;&
> + p|P)
> + mult=$((mult * 1024))
> + ;&
> + t|T)
> + mult=$((mult * 1024))
> + ;&
> + g|G)
> + mult=$((mult * 1024))
> + ;&
> + m|M)
> + mult=$((mult * 1024))
> + ;&
> + k|K)
> + mult=$((mult * 1024))
> + ;&
> + b|B)
> + ;;
> + *)
> + echo "unknown size descriptor $endchar"
> + exit 1
> + esac
> + elif [[ $str =~ ^[0-9]+$ ]] ; then
> + size=$str
> + else
> + echo "size value $str is invalid"
> + exit 1
> + fi
> +
> + size=$((size * mult))
> + echo $size
> +}
Hi An,
Coreutils has numfmt(1) to do this kind of conversion. I wonder if we
could use it here, unless it is not available all the platforms that
matters for xfstests, though:
$ echo 1K | numfmt --from=iec
1024
> +
> # Create fs of certain size on scratch device
> # _scratch_mkfs_sized <size in bytes> [optional blocksize]
> _scratch_mkfs_sized()
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2022-06-16 15:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 4:38 [PATCH v2 0/2] Fix input value to _scratch_mkfs_sized An Long
2022-06-16 4:38 ` [PATCH v2 1/2] common/rc: add _parse_size_string An Long
2022-06-16 15:25 ` Gabriel Krisman Bertazi [this message]
2022-06-17 6:45 ` Long An
2022-06-16 4:38 ` [PATCH v2 2/2] common/rc: fix input value to _scratch_mkfs_sized An Long
2022-06-17 3:58 ` [PATCH v2 0/2] Fix " Dave Chinner
2022-06-17 7:03 ` Long An
2022-06-17 17:52 ` Zorro Lang
2022-06-17 22:24 ` Dave Chinner
2022-06-18 3:14 ` Zorro Lang
2022-06-20 23:12 ` Dave Chinner
2022-06-21 4:05 ` Zorro Lang
2022-06-21 4:25 ` Long An
2022-06-21 4:40 ` Zorro Lang
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=874k0ky6ju.fsf@collabora.com \
--to=krisman@collabora.com \
--cc=fstests@vger.kernel.org \
--cc=lan@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