On Thu, May 31, 2018 at 4:27 PM, Richard Guy Briggs <r...@redhat.com> wrote:
> Since seccomp events are triggered by user activity, tie the SECCOMP
> record to the syscall record to collect all records from the same event.
>
> See: https://github.com/linux-audit/audit-kernel/issues/87
>
> Signed-off-by: Richard Guy Briggs <r...@redhat.com>
> ---
> kernel/auditsc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Looks good to me, queued up for after the merge window.
> diff --git a/kernel/auditsc.c b/kernel/auditsc.c
> index ceb1c45..fefb9e2 100644
> --- a/kernel/auditsc.c
> +++ b/kernel/auditsc.c
> @@ -2485,7 +2485,7 @@ void audit_seccomp(unsigned long syscall, long signr,
> int code)
> {
> struct audit_buffer *ab;
>
> - ab = audit_log_start(NULL, GFP_KERNEL, AUDIT_SECCOMP);
> + ab = audit_log_start(audit_context(), GFP_KERNEL, AUDIT_SECCOMP);
> if (unlikely(!ab))
> return;
> audit_log_task(ab);
> --
> 1.8.3.1
--
paul moore
www.paul-moore.com
--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit
