From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: retrieve EIP/RIP for syscall in audit Date: Fri, 13 Jul 2012 13:27:06 -0400 Message-ID: <1491986.ZcUTPKqv5T@x2> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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