From mboxrd@z Thu Jan  1 00:00:00 1970
From: Xiaokui Shu <subbyte@gmail.com>
Subject: Re: retrieve EIP/RIP for syscall in audit
Date: Thu, 12 Jul 2012 15:06:23 -0400
Message-ID: <CAMU3N_Jt9qyQgbK=cYWxXNbz90x4HgQyAZ2UkiYpCP=ApLSXvw@mail.gmail.com>
References: <CAMU3N_J+26jjZ9N0zf-JKEMLnVgaRwfDjd0Ck3JOO+P1Q3mRsA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <linux-audit-bounces@redhat.com>
Received: from mx1.redhat.com (ext-mx13.extmail.prod.ext.phx2.redhat.com
	[10.5.110.18])
	by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP
	id q6CJ6Q08013478
	for <linux-audit@redhat.com>; Thu, 12 Jul 2012 15:06:26 -0400
Received: from mail-lb0-f174.google.com (mail-lb0-f174.google.com
	[209.85.217.174])
	by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q6CJ6OAI005832
	for <linux-audit@redhat.com>; Thu, 12 Jul 2012 15:06:25 -0400
Received: by lbbgm6 with SMTP id gm6so4362427lbb.33
	for <linux-audit@redhat.com>; Thu, 12 Jul 2012 12:06:24 -0700 (PDT)
In-Reply-To: <CAMU3N_J+26jjZ9N0zf-JKEMLnVgaRwfDjd0Ck3JOO+P1Q3mRsA@mail.gmail.com>
List-Unsubscribe: <https://www.redhat.com/mailman/options/linux-audit>,
	<mailto:linux-audit-request@redhat.com?subject=unsubscribe>
List-Archive: <https://www.redhat.com/archives/linux-audit>
List-Post: <mailto:linux-audit@redhat.com>
List-Help: <mailto:linux-audit-request@redhat.com?subject=help>
List-Subscribe: <https://www.redhat.com/mailman/listinfo/linux-audit>,
	<mailto:linux-audit-request@redhat.com?subject=subscribe>
Sender: linux-audit-bounces@redhat.com
Errors-To: linux-audit-bounces@redhat.com
To: linux-audit@redhat.com
List-Id: linux-audit@redhat.com

On Thu, Jul 12, 2012 at 3:04 PM, Xiaokui Shu <subbyte@gmail.com> wrote:
> Hello,
>
> I have a question about one of the features of audit.
> Can I use audit to log the EIP/RIP at time of syscall? There is a "-i"
> flag in strace that does the work.
>
> When I compare the mechanisms of audit and strace(ptrace), I find
> maybe it is not possible for strace to do so. Audit is on the kernel
"strace" -> "audit" in the sentence above.
Sorry for the mistyping.

> side of a syscall, and does not know the audited program's internal
> information (I am not sure if I understand it right). However, one can
> still fetch extra information out of the syscall event (e.g. block a
> syscall when coming, check the audited program stack and clear
> blocking), but it may bring much overhead.
>
> Best,
> Xiaokui