From: Anthony PERARD <anthony.perard@citrix.com>
To: George Dunlap <george.dunlap@citrix.com>
Cc: Ross Lagerwall <ross.lagerwall@citrix.com>,
xen-devel@lists.xenproject.org,
Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <ian.jackson@citrix.com>
Subject: Re: [PATCH v2 2/6] test/depriv: Add a tool to check process-level depriv
Date: Mon, 24 Sep 2018 12:14:04 +0100 [thread overview]
Message-ID: <20180924111404.GD2244@perard.uk.xensource.com> (raw)
In-Reply-To: <20180921170428.13771-2-george.dunlap@citrix.com>
On Fri, Sep 21, 2018 at 06:04:24PM +0100, George Dunlap wrote:
> diff --git a/tools/tests/depriv/depriv-process-checker.sh b/tools/tests/depriv/depriv-process-checker.sh
> --- /dev/null
> +++ b/tools/tests/depriv/depriv-process-checker.sh
[...]
> +# Example input:
> +# Uid: 1193 1193 1193 1193
> +input=$(grep Uid /proc/$dmpid/status)
> +if [[ "$input" =~ ^Uid:[[:space:]]*([0-9]+)[[:space:]]*([0-9]+)[[:space:]]*([0-9]+)[[:space:]]*([0-9]+)$ ]] ; then
You should replace all the * by +. Surely you want at least one space
between two numbers.
> + result="PASSED"
> + for i in {1..4}; do
> + if [[ "${BASH_REMATCH[$i]}" != "$tgt_uid" ]] ; then
> + result="FAILED"
> + failed="true"
> + break
> + fi
> + done
> +else
> + result="FAILED"
> + failed="true"
> +fi
> +echo $result
> +
> +# Example input:
> +# Gid: 10020 10020 10020 10020
> +echo -n "Process GID: "
> +input=$(grep Uid /proc/$dmpid/status)
Here grep for "Uid" but ...
> +if [[ "$input" =~ ^Gid:[[:space:]]*([0-9]+)[[:space:]]*([0-9]+)[[:space:]]*([0-9]+)[[:space:]]*([0-9]+)$ ]] ; then
here is "Gid".
> + result="PASSED"
> + for i in {1..4}; do
> + if [[ "${BASH_REMATCH[$i]}" != "$65534" ]] ; then
Is "$65534" supposed to be a variable? Or is "$" a extra character?
--
Anthony PERARD
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-09-24 11:14 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 17:04 [PATCH v2 1/6] docs/qemu-deprivilege: Revise and update with status and future plans George Dunlap
2018-09-21 17:04 ` [PATCH v2 2/6] test/depriv: Add a tool to check process-level depriv George Dunlap
2018-09-24 10:57 ` Ian Jackson
2018-09-24 14:45 ` George Dunlap
2018-09-24 11:14 ` Anthony PERARD [this message]
2018-09-21 17:04 ` [PATCH v2 3/6] tools/dm_restrict: Ask QEMU to chroot George Dunlap
2018-09-24 8:20 ` Paul Durrant
2018-09-24 9:50 ` George Dunlap
2018-09-24 9:52 ` Paul Durrant
2018-09-24 10:31 ` Ian Jackson
2018-09-21 17:04 ` [PATCH v2 4/6] tools/dm_restrict: Unshare mount and IPC namespaces on Linux George Dunlap
2018-09-24 8:24 ` Paul Durrant
2018-09-24 10:40 ` Ian Jackson
2018-09-24 14:22 ` George Dunlap
2018-09-25 10:55 ` Ian Jackson
2018-09-21 17:04 ` [PATCH v2 5/6] tools/dm_depriv: Add first cut RLIMITs George Dunlap
2018-09-24 8:34 ` Paul Durrant
[not found] ` <CAFLBxZanne777R0WfJLuGqTv3dx=A+W0Z5UsW9B0i4MFMWWKXw@mail.gmail.com>
2018-10-05 15:18 ` George Dunlap
2018-09-24 10:48 ` Ian Jackson
2018-09-24 14:41 ` George Dunlap
2018-09-25 11:03 ` Ian Jackson
2018-09-21 17:04 ` [PATCH v2 6/6] RFC: tools/dm_restrict: Enable QEMU sandboxing George Dunlap
2018-09-24 10:49 ` Ian Jackson
2018-09-24 11:16 ` George Dunlap
2018-09-24 13:04 ` Ian Jackson
2018-09-24 13:43 ` George Dunlap
2018-09-25 10:46 ` Ian Jackson
2018-09-24 11:21 ` Ian Jackson
2018-09-24 14:28 ` George Dunlap
2018-09-25 11:02 ` Ian Jackson
2018-09-25 14:24 ` George Dunlap
2018-09-26 10:57 ` Ian Jackson
2018-09-24 8:14 ` [PATCH v2 1/6] docs/qemu-deprivilege: Revise and update with status and future plans Paul Durrant
2018-09-24 10:23 ` Ian Jackson
2018-09-24 13:08 ` George Dunlap
2018-09-25 10:44 ` Ian Jackson
2018-09-25 11:20 ` Anthony PERARD
2018-09-28 11:37 ` George Dunlap
2018-09-28 12:59 ` Anthony PERARD
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=20180924111404.GD2244@perard.uk.xensource.com \
--to=anthony.perard@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=ian.jackson@citrix.com \
--cc=ross.lagerwall@citrix.com \
--cc=sstabellini@kernel.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.