On Thu, Dec 03, 2020 at 01:57:21PM +, Stefan Hajnoczi wrote:
On Tue, Nov 24, 2020 at 08:08:26PM +0800, Coiby Xu wrote:
Hi Stefan,
On Wed, Nov 11, 2020 at 12:43:26PM +, Stefan Hajnoczi wrote:
> Do not leave stdin and stdout open after fork. stdout is the
> tap-driver.pl pipe. If we keep
On Tue, Nov 24, 2020 at 08:08:26PM +0800, Coiby Xu wrote:
> Hi Stefan,
>
> On Wed, Nov 11, 2020 at 12:43:26PM +, Stefan Hajnoczi wrote:
> > Do not leave stdin and stdout open after fork. stdout is the
> > tap-driver.pl pipe. If we keep the pipe open then tap-driver.pl will not
> > detect that
Hi Stefan,
On Wed, Nov 11, 2020 at 12:43:26PM +, Stefan Hajnoczi wrote:
Do not leave stdin and stdout open after fork. stdout is the
tap-driver.pl pipe. If we keep the pipe open then tap-driver.pl will not
detect that qos-test has terminated and it will hang.
I wonder under which situation
Do not leave stdin and stdout open after fork. stdout is the
tap-driver.pl pipe. If we keep the pipe open then tap-driver.pl will not
detect that qos-test has terminated and it will hang.
Signed-off-by: Stefan Hajnoczi
---
tests/qtest/vhost-user-blk-test.c | 9 +
1 file changed, 9 insert
