On Thu, Jul 10, 2014 at 05:33:50AM +0100, AKASHI Takahiro wrote:
> Will,
>
> > (1) Updating syscallno based on w8, but this ties us to the current ABI
> > and could get messy if this register changes in the future.
>
> So, is this the conclusion that I should follow?
I think so, with the
Will,
> (1) Updating syscallno based on w8, but this ties us to the current ABI
> and could get messy if this register changes in the future.
So, is this the conclusion that I should follow?
-Takahiro AKASHI
On 07/09/2014 01:12 PM, Will Deacon wrote:
Hi Akashi,
On Fri, Jul 04, 2014 at
Hi Akashi,
On Fri, Jul 04, 2014 at 08:31:55AM +0100, AKASHI Takahiro wrote:
> secure_computing() should always be called first in syscall_trace_enter().
> If it returns non-zero, we should stop further handling. Then that system
> call may eventually fail, be trapped or the process itself be kille
secure_computing() should always be called first in syscall_trace_enter().
If it returns non-zero, we should stop further handling. Then that system
call may eventually fail, be trapped or the process itself be killed
depending on loaded rules.
In this case, syscall_trace_enter() returns a dedicate
4 matches
Mail list logo
