From: Fam Zheng <famz@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/5] docker: Use unconfined security profile
Date: Fri, 5 May 2017 17:12:40 +0800 [thread overview]
Message-ID: <20170505091240.GF21435@lemon.lan> (raw)
In-Reply-To: <8737cjogio.fsf@linaro.org>
On Fri, 05/05 09:27, Alex Bennée wrote:
>
> Fam Zheng <famz@redhat.com> writes:
>
> > Some by default blocked syscalls are required to run tests for example
> > userfaultfd.
>
> Is there any way the tests could DoS the host? I guess you could achieve
> the same running the iotests directly from make but it does seem we
> should confine the docker guest as much as possible.
I don't know the answer to the security question, but if a confined docker
environment is full of pitfalls and unpleasant to work with, it won't grow that
much.
Patchew runs this in a VM, so it's not a big problem to me.
>
> >
> > Signed-off-by: Fam Zheng <famz@redhat.com>
> > ---
> > tests/docker/Makefile.include | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/tests/docker/Makefile.include b/tests/docker/Makefile.include
> > index 0ed8c3d..09d157c 100644
> > --- a/tests/docker/Makefile.include
> > +++ b/tests/docker/Makefile.include
> > @@ -127,6 +127,7 @@ docker-run: docker-qemu-src
> > $(call quiet-command, \
> > $(SRC_PATH)/tests/docker/docker.py run \
> > $(if $(NOUSER),,-u $(shell id -u)) -t \
> > + --security-opt seccomp=unconfined \
> > $(if $V,,--rm) \
> > $(if $(DEBUG),-i,--net=none) \
> > -e TARGET_LIST=$(TARGET_LIST) \
>
>
> --
> Alex Bennée
next prev parent reply other threads:[~2017-05-05 9:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 3:23 [Qemu-devel] [PATCH 0/5] docker: Add test-block Fam Zheng
2017-05-05 3:23 ` [Qemu-devel] [PATCH 1/5] docker: Run tests with current user Fam Zheng
2017-05-05 8:25 ` Alex Bennée
2017-05-06 16:25 ` Philippe Mathieu-Daudé
2017-05-05 3:23 ` [Qemu-devel] [PATCH 2/5] docker: Add bzip2 and hostname to fedora image Fam Zheng
2017-05-05 8:25 ` Alex Bennée
2017-05-06 16:34 ` Philippe Mathieu-Daudé
2017-05-05 3:23 ` [Qemu-devel] [PATCH 3/5] docker: Use unconfined security profile Fam Zheng
2017-05-05 8:27 ` Alex Bennée
2017-05-05 9:12 ` Fam Zheng [this message]
2017-05-06 16:33 ` Philippe Mathieu-Daudé
2017-05-05 3:23 ` [Qemu-devel] [PATCH 4/5] docker: Add libaio to fedora image Fam Zheng
2017-05-05 8:27 ` Alex Bennée
2017-05-06 16:26 ` Philippe Mathieu-Daudé
2017-05-05 3:23 ` [Qemu-devel] [PATCH 5/5] docker: Add test-block Fam Zheng
2017-05-05 8:28 ` Alex Bennée
2017-05-05 8:55 ` Fam Zheng
2017-05-08 15:11 ` Yash Mankad
2017-05-08 15:52 ` Daniel P. Berrange
2017-05-05 7:44 ` [Qemu-devel] [PATCH 0/5] " Paolo Bonzini
2017-05-05 8:05 ` Fam Zheng
2017-05-05 8:07 ` Paolo Bonzini
2017-05-05 8:52 ` Fam Zheng
2017-05-08 15:55 ` Daniel P. Berrange
2017-05-08 16:06 ` Paolo Bonzini
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=20170505091240.GF21435@lemon.lan \
--to=famz@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).