[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: QEMU policy for real file tests

From: Alex Bennée
Subject: Re: QEMU policy for real file tests
Date: Thu, 17 Sep 2020 10:26:36 +0100
User-agent: mu4e 1.5.5; emacs 28.0.50

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

Alex Bennée

reply via email to

[Prev in Thread] Current Thread [Next in Thread]