From: "Alex Bennée" <alex.bennee@linaro.org>
To: Christian Schoenebeck <qemu_oss@crudebyte.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, Laurent Vivier <lvivier@redhat.com>,
Greg Kurz <groug@kaod.org>, Max Reitz <mreitz@redhat.com>
Subject: Re: QEMU policy for real file tests
Date: Thu, 17 Sep 2020 10:26:36 +0100 [thread overview]
Message-ID: <87y2l8ycs3.fsf@linaro.org> (raw)
In-Reply-To: <1836935.RIYQIvKipu@silver>
Christian Schoenebeck <qemu_oss@crudebyte.com> writes:
> Hi,
>
> is there a QEMU policy for test cases that create/write/read/delete real files
> and directories? E.g. should they be situated at a certain location and is any
> measure of sandboxing required?
I don't think we have a hard and fast policy. It also depends on what
you are doing the test in - but ideally you should use a secure mktempd
(that can't clash) and clean-up after you are finished. This is a bit
easier in python than shell I think.
For example iotests end up in $BUILD_DIR/scratch (driven by TEST_DIR
being set somewhere) whereas the gdb stub tests use socket_dir =
TemporaryDirectory("qemu-gdbstub") which get auto-cleaned when it
finishes.
--
Alex Bennée
next prev parent reply other threads:[~2020-09-17 9:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 8:50 QEMU policy for real file tests Christian Schoenebeck
2020-09-17 9:26 ` Alex Bennée [this message]
2020-09-17 9:37 ` Daniel P. Berrangé
2020-09-17 9:55 ` Thomas Huth
2020-09-17 12:06 ` Christian Schoenebeck
2020-09-17 12:24 ` Daniel P. Berrangé
2020-09-17 12:40 ` Peter Maydell
2020-09-17 13:04 ` Thomas Huth
2020-09-17 13:11 ` Peter Maydell
2020-09-17 14:04 ` Christian Schoenebeck
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=87y2l8ycs3.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=groug@kaod.org \
--cc=kwolf@redhat.com \
--cc=lvivier@redhat.com \
--cc=mreitz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu_oss@crudebyte.com \
--cc=thuth@redhat.com \
/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.