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

Re: [Xen-devel] [PATCH v2 5/6] tools/dm_depriv: Add first cut RLIMITs

To: George Dunlap <george.dunlap@xxxxxxxxxx>
From: Ian Jackson <ian.jackson@xxxxxxxxxx>
Date: Tue, 25 Sep 2018 12:03:57 +0100
Cc: Anthony Perard <anthony.perard@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx, Wei Liu <wei.liu2@xxxxxxxxxx>
Delivery-date: Tue, 25 Sep 2018 11:04:03 +0000
List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

George Dunlap writes ("Re: [PATCH v2 5/6] tools/dm_depriv: Add first cut 
RLIMITs"):
> Does osstest need to actually parse the output at all?  Couldn't it just
> capture the output verbatim in a log file, and use the exit code as a
> pass/fail (or grep for FAILED)?

Yes.  Each of these tests should be its own substep.  That way we can
unconditionally run the test and later add individual restriction
features.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

References:
- [Xen-devel] [PATCH v2 1/6] docs/qemu-deprivilege: Revise and update with status and future plans
  - From: George Dunlap
- [Xen-devel] [PATCH v2 5/6] tools/dm_depriv: Add first cut RLIMITs
  - From: George Dunlap
- Re: [Xen-devel] [PATCH v2 5/6] tools/dm_depriv: Add first cut RLIMITs
  - From: Ian Jackson
- Re: [Xen-devel] [PATCH v2 5/6] tools/dm_depriv: Add first cut RLIMITs
  - From: George Dunlap

Prev by Date: [Xen-devel] [PATCH V3] x86/altp2m: clean up p2m_{get/set}_suppress_ve()
Next by Date: Re: [Xen-devel] null scheduler bug
Previous by thread: Re: [Xen-devel] [PATCH v2 5/6] tools/dm_depriv: Add first cut RLIMITs
Next by thread: [Xen-devel] [PATCH v2 6/6] RFC: tools/dm_restrict: Enable QEMU sandboxing
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.