Re: [libvirt] [PATCH] 4/10 AppArmor driver updates

2010-04-05 Thread Jamie Strandboge
On Mon, 2010-04-05 at 16:15 -0500, Jamie Strandboge wrote: > 4_qemu_driver_stdin_path.patch: adjust args to qemudStartVMDaemon() to > also specify path to stdin_fd, so this can be passed to the AppArmor > driver via *SetSecurityAllLabel(). This updates all calls to > qemudStartVMDaemon() as well a

Re: [libvirt] [PATCH] 4/10 AppArmor driver updates

2010-04-14 Thread Daniel P. Berrange
On Mon, Apr 05, 2010 at 04:21:16PM -0500, Jamie Strandboge wrote: > On Mon, 2010-04-05 at 16:15 -0500, Jamie Strandboge wrote: > > > 4_qemu_driver_stdin_path.patch: adjust args to qemudStartVMDaemon() to > > also specify path to stdin_fd, so this can be passed to the AppArmor > > driver via *SetSe

Re: [libvirt] [PATCH] 4/10 AppArmor driver updates

2010-06-04 Thread Laine Stump
Jamie, This patch was ACKed but somehow never pushed. Is it still okay to push it as is? On Mon, 2010-04-05 at 16:15 -0500, Jamie Strandboge wrote: > 4_qemu_driver_stdin_path.patch: adjust args to qemudStartVMDaemon() to > also specify path to stdin_fd, so this can be passed to the AppArmor > d

Re: [libvirt] [PATCH] 4/10 AppArmor driver updates

2010-06-07 Thread Laine Stump
On 06/04/2010 12:20 PM, Laine Stump wrote: Jamie, This patch was ACKed but somehow never pushed. Is it still okay to push it as is? Based on affirmative feedback from Jamie, I just pushed this patch. On Mon, 2010-04-05 at 16:15 -0500, Jamie Strandboge wrote: 4_qemu_driver_stdin_pa