From: Alexander Viro <aviro@redhat.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com, aaw@google.com, a.p.zijlstra@chello.nl
Subject: Re: [patch 058/209] audit: rework execve audit
Date: Fri, 27 Jul 2007 17:21:10 -0400 [thread overview]
Message-ID: <20070727212110.GG13539@devserv.devel.redhat.com> (raw)
In-Reply-To: <200707271711.22499.sgrubb@redhat.com>
On Fri, Jul 27, 2007 at 05:11:22PM -0400, Steve Grubb wrote:
> On Friday 27 July 2007 17:03:59 Alexander Viro wrote:
> > On Fri, Jul 27, 2007 at 04:13:10PM -0400, Steve Grubb wrote:
> > > WARNING: at kernel/auditsc.c:859 audit_log_execve_info() (Not tainted)
> > >
> > > Call Trace:
> > > [<ffffffff8106b06f>] audit_log_exit+0x5d7/0x964
> > > [<ffffffff81050805>] trace_hardirqs_on+0x12e/0x151
> > > [<ffffffff8106b60b>] audit_syscall_exit+0x9b/0x300
> > > [<ffffffff8100ee62>] syscall_trace_leave+0x2c/0x87
> > > [<ffffffff8100beb1>] int_very_careful+0x3a/0x43
> >
> > Umm... which architecture?
>
> Its the x86_64 kernel on a Turion64 processor.
I think I understand what's going on. Test for execve failure in
there is bloody bogus.
next prev parent reply other threads:[~2007-07-27 21:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 8:48 [patch 058/209] audit: rework execve audit akpm
2007-07-27 20:13 ` Steve Grubb
2007-07-27 20:44 ` Peter Zijlstra
2007-07-27 20:57 ` Steve Grubb
2007-07-27 21:55 ` Peter Zijlstra
2007-07-27 22:06 ` Peter Zijlstra
2007-07-27 22:24 ` Peter Zijlstra
2007-07-27 20:50 ` Alexander Viro
2007-07-27 21:03 ` Alexander Viro
2007-07-27 21:11 ` Steve Grubb
2007-07-27 21:21 ` Alexander Viro [this message]
2007-07-27 22:55 ` [PATCH] audit: fix two bugs in the new execve audit code Peter Zijlstra
2007-07-27 23:05 ` Andrew Morton
2007-07-28 2:05 ` Steve Grubb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070727212110.GG13539@devserv.devel.redhat.com \
--to=aviro@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=aaw@google.com \
--cc=linux-audit@redhat.com \
--cc=sgrubb@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.