From mboxrd@z Thu Jan 1 00:00:00 1970 From: Xiaokui Shu Subject: Re: retrieve EIP/RIP for syscall in audit Date: Fri, 13 Jul 2012 13:39:47 -0400 Message-ID: References: <1491986.ZcUTPKqv5T@x2> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1491986.ZcUTPKqv5T@x2> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: Steve Grubb Cc: linux-audit@redhat.com List-Id: linux-audit@redhat.com Thank you very much! I will check systemtap for the feature. Best, Xiaokui On Fri, Jul 13, 2012 at 1:27 PM, Steve Grubb wrote: > On Thursday, July 12, 2012 03:04:11 PM Xiaokui Shu 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. > > No. The audit system does not collect that information. Maybe trace points or > systemtap would be a better approach for that kind of thing? > > -Steve > >> 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 >> 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 >> >> -- >> Linux-audit mailing list >> Linux-audit@redhat.com >> https://www.redhat.com/mailman/listinfo/linux-audit