From: Luis Henriques <lhenriques@suse.de>
To: fstests@vger.kernel.org
Subject: [PATCH] generic/581: remove extra escape character from awk line
Date: Wed, 22 Nov 2023 17:03:24 +0000 [thread overview]
Message-ID: <ZV40XOGNJdru13XE@suse.de> (raw)
Checking the keys in /proc/key-users is buggy, as there's an extra '\'
character: in '{print \$4}' the '$4' shouldn't be escaped otherwise the
'awk' command will fail. This has passed unnoticed because the output
is sent to '_user_do' function and the result assigned to a variable.
While there, replace 'awk' by $AWK_PROG.
Signed-off-by: Luis Henriques <lhenriques@suse.de>
---
tests/generic/581 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Hi!
Please note that I'm not an 'awk' expert and I may be wrong! But if I do
see an error if I run something like:
$ awk '/^[[:space:]]*1000:/{print \$4}' /proc/key-users
awk: cmd. line:1: /^[[:space:]]*1000:/{print \$4}
awk: cmd. line:1: ^ backslash not last character on line
But maybe this depends on the awk implementation, although I've tried a few.
diff --git a/tests/generic/581 b/tests/generic/581
index cabc7e1c69ab..1a4b571d40ce 100755
--- a/tests/generic/581
+++ b/tests/generic/581
@@ -92,7 +92,7 @@ while grep -E -q '^[0-9a-f]+ [^ ]*i[^ ]*' /proc/keys; do
done
# Set the user key quota to the fsgqa user's current number of keys plus 5.
-orig_keys=$(_user_do "awk '/^[[:space:]]*$(id -u fsgqa):/{print \$4}' /proc/key-users | cut -d/ -f1")
+orig_keys=$(_user_do "$AWK_PROG '/^[[:space:]]*$(id -u fsgqa):/{print $4}' /proc/key-users | cut -d/ -f1")
: ${orig_keys:=0}
echo "orig_keys=$orig_keys" >> $seqres.full
orig_maxkeys=$(</proc/sys/kernel/keys/maxkeys)
next reply other threads:[~2023-11-22 17:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 17:03 Luis Henriques [this message]
2023-11-22 23:16 ` [PATCH] generic/581: remove extra escape character from awk line Eric Biggers
2023-11-23 11:46 ` Luís Henriques
2023-11-28 14:16 ` Luis Henriques
2023-11-28 17:37 ` Eric Biggers
2023-11-28 18:25 ` Luis Henriques
2023-12-05 17:28 ` Luis Henriques
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=ZV40XOGNJdru13XE@suse.de \
--to=lhenriques@suse.de \
--cc=fstests@vger.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