On Thu, Jun 26, 2014 at 5:37 AM, David Drysdale wrote:
> On Mon, Jun 23, 2014 at 02:58:06PM -0700, Kees Cook wrote:
>> In preparation for adding seccomp locking, move filter creation away
>> from where it is checked and applied. This will allow for locking where
>> no memory allocation is
On Thu, Jun 26, 2014 at 5:37 AM, David Drysdale drysd...@google.com wrote:
On Mon, Jun 23, 2014 at 02:58:06PM -0700, Kees Cook wrote:
In preparation for adding seccomp locking, move filter creation away
from where it is checked and applied. This will allow for locking where
no memory
On Mon, Jun 23, 2014 at 02:58:06PM -0700, Kees Cook wrote:
> In preparation for adding seccomp locking, move filter creation away
> from where it is checked and applied. This will allow for locking where
> no memory allocation is happening. The validation, filter attachment,
> and seccomp mode
On Mon, Jun 23, 2014 at 02:58:06PM -0700, Kees Cook wrote:
In preparation for adding seccomp locking, move filter creation away
from where it is checked and applied. This will allow for locking where
no memory allocation is happening. The validation, filter attachment,
and seccomp mode setting
In preparation for adding seccomp locking, move filter creation away
from where it is checked and applied. This will allow for locking where
no memory allocation is happening. The validation, filter attachment,
and seccomp mode setting can all happen under the future locks.
Signed-off-by: Kees
In preparation for adding seccomp locking, move filter creation away
from where it is checked and applied. This will allow for locking where
no memory allocation is happening. The validation, filter attachment,
and seccomp mode setting can all happen under the future locks.
Signed-off-by: Kees
6 matches
Mail list logo