summaryrefslogtreecommitdiff
path: root/cmd
diff options
context:
space:
mode:
authorRasmus Villemoes <[email protected]>2026-03-30 16:01:06 +0200
committerTom Rini <[email protected]>2026-04-02 16:00:29 -0600
commitf7e7c55e53e80100c327b9cb0512c069acf80ab5 (patch)
tree76026da1264f12757d7bee3a0cb46ae48a0b278e /cmd
parentd1cd6733917fa67c262fbad2520da93d788e17f7 (diff)
cmd: test: add bug-compatibility special case for 'test -n'
It turns out that there is lots of code in the wild, including in the U-Boot tree itself, which used to rely on test -n $somevar to yield false when $somevar is not defined or empty. See for example all the occurrences of 'test -n $fdtfile'. That was really only a quirk of the implementation that refused calls with argc < 3, and not because it was interpreted as test -n "$somevar" which is how this should be spelled. While not exactly conforming to POSIX, we can accomodate such scripts by special-casing a single argument "-n" to be interpreted as if it comes from code as above with empty $somevar. Since we only just added the ability to test a string for emptiness using the single-argument form, it is very unlikely that there is code doing test "$str" which would now fail if $str happens to be exactly "-n"; such a test should really always be spelled test -n "$str" Fixes: 8b0619579b2 ("cmd: test: fix handling of single-argument form of test") Reported-by: Franz Schnyder <[email protected]> Signed-off-by: Rasmus Villemoes <[email protected]> Reviewed-by: Simon Glass <[email protected]>
Diffstat (limited to 'cmd')
-rw-r--r--cmd/test.c15
1 files changed, 14 insertions, 1 deletions
diff --git a/cmd/test.c b/cmd/test.c
index 0d0f090386c..c76ebf800ee 100644
--- a/cmd/test.c
+++ b/cmd/test.c
@@ -75,12 +75,25 @@ static int do_test(struct cmd_tbl *cmdtp, int flag, int argc,
* Per POSIX, 'test' with 0 arguments should return 1, while
* 'test <arg>' should be equivalent to 'test -n <arg>',
* i.e. true if and only if <arg> is not empty.
+ *
+ * However, due to previous versions of U-Boot unconditionally
+ * returning false when 'test' was given less than two
+ * arguments, there are existing scripts that do
+ *
+ * test -n $somevar
+ *
+ * (i.e. without properly quoting $somevar) and expecting that
+ * to return false when $somevar expands to nothing. It is
+ * quite unlikely that anyone would use the single-argument
+ * form to test a string for being empty and a possible
+ * non-empty value for that string to be exactly "-n". So we
+ * interpret 'test -n' as if it was 'test -n ""'.
*/
if (argc < 2)
return 1;
if (argc == 2)
- return !strcmp(argv[1], "");
+ return !strcmp(argv[1], "") || !strcmp(argv[1], "-n");
#ifdef DEBUG
{