From: Waiman Long <llong@redhat.com>
To: Aditya Dutt <duttaditya18@gmail.com>,
Shuah Khan <shuah@kernel.org>, Tejun Heo <tj@kernel.org>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
"David S . Miller" <davem@davemloft.net>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
linux-kernel-mentees@lists.linuxfoundation.org,
cgroups@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] selftests: make shell scripts POSIX-compliant
Date: Tue, 18 Feb 2025 15:44:47 -0500 [thread overview]
Message-ID: <c7fce1b1-b0f7-42b8-9a1f-fd07e6200924@redhat.com> (raw)
In-Reply-To: <20250216120225.324468-1-duttaditya18@gmail.com>
On 2/16/25 7:02 AM, Aditya Dutt wrote:
> Changes include:
> - Replaced [[ ... ]] with [ ... ]
> - Replaced == with =
> - Replaced printf -v with cur=$(printf ...).
> - Replaced echo -e with printf "%b\n" ...
>
> The above mentioned are Bash/GNU extensions and are not part of POSIX.
> Using shells like dash or non-GNU coreutils may produce errors.
> They have been replaced with POSIX-compatible alternatives.
>
> Signed-off-by: Aditya Dutt <duttaditya18@gmail.com>
> ---
>
> I have made sure to only change the files that specifically have the
> /bin/sh shebang.
> I have referred to https://mywiki.wooledge.org/Bashism for information
> on what is and what isn't POSIX-compliant.
>
> tools/testing/selftests/cgroup/test_cpuset_v1_hp.sh | 10 +++++-----
> tools/testing/selftests/kexec/kexec_common_lib.sh | 2 +-
> tools/testing/selftests/kexec/test_kexec_file_load.sh | 2 +-
> tools/testing/selftests/net/veth.sh | 10 +++++-----
> tools/testing/selftests/powerpc/eeh/eeh-vf-aware.sh | 2 +-
> tools/testing/selftests/zram/zram_lib.sh | 2 +-
> 6 files changed, 14 insertions(+), 14 deletions(-)
>
> diff --git a/tools/testing/selftests/cgroup/test_cpuset_v1_hp.sh b/tools/testing/selftests/cgroup/test_cpuset_v1_hp.sh
> index 3f45512fb512..00416248670f 100755
> --- a/tools/testing/selftests/cgroup/test_cpuset_v1_hp.sh
> +++ b/tools/testing/selftests/cgroup/test_cpuset_v1_hp.sh
> @@ -11,24 +11,24 @@ skip_test() {
> exit 4 # ksft_skip
> }
>
> -[[ $(id -u) -eq 0 ]] || skip_test "Test must be run as root!"
> +[ $(id -u) -eq 0 ] || skip_test "Test must be run as root!"
>
> # Find cpuset v1 mount point
> CPUSET=$(mount -t cgroup | grep cpuset | head -1 | awk -e '{print $3}')
> -[[ -n "$CPUSET" ]] || skip_test "cpuset v1 mount point not found!"
> +[ -n "$CPUSET" ] || skip_test "cpuset v1 mount point not found!"
>
> #
> # Create a test cpuset, put a CPU and a task there and offline that CPU
> #
> TDIR=test$$
> -[[ -d $CPUSET/$TDIR ]] || mkdir $CPUSET/$TDIR
> +[ -d $CPUSET/$TDIR ] || mkdir $CPUSET/$TDIR
> echo 1 > $CPUSET/$TDIR/cpuset.cpus
> echo 0 > $CPUSET/$TDIR/cpuset.mems
> sleep 10&
> TASK=$!
> echo $TASK > $CPUSET/$TDIR/tasks
> NEWCS=$(cat /proc/$TASK/cpuset)
> -[[ $NEWCS != "/$TDIR" ]] && {
> +[ $NEWCS != "/$TDIR" ] && {
> echo "Unexpected cpuset $NEWCS, test FAILED!"
> exit 1
> }
> @@ -38,7 +38,7 @@ sleep 0.5
> echo 1 > /sys/devices/system/cpu/cpu1/online
> NEWCS=$(cat /proc/$TASK/cpuset)
> rmdir $CPUSET/$TDIR
> -[[ $NEWCS != "/" ]] && {
> +[ $NEWCS != "/" ] && {
> echo "cpuset $NEWCS, test FAILED!"
> exit 1
> }
test_cpuset_v1_hp.sh had been changed to use /bin/bash in v6.14 by
commit fd079124112c ("selftests/cgroup: use bash in test_cpuset_v1_hp.sh").
Cheers,
Longman
prev parent reply other threads:[~2025-02-18 20:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-16 12:02 [PATCH] selftests: make shell scripts POSIX-compliant Aditya Dutt
2025-02-16 16:11 ` Tejun Heo
2025-02-17 3:00 ` Hangbin Liu
2025-02-18 20:44 ` Waiman Long [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=c7fce1b1-b0f7-42b8-9a1f-fd07e6200924@redhat.com \
--to=llong@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=duttaditya18@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tj@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