From: Chris Wright <chrisw@osdl.org>
To: Linux Audit Discussion <linux-audit@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.12-rc4-mm2 - sleeping function called from invalid context at mm/slab.c:2502
Date: Fri, 20 May 2005 10:19:06 -0700 [thread overview]
Message-ID: <20050520171906.GZ27549@shell0.pdx.osdl.net> (raw)
In-Reply-To: <1116608736.12489.170.camel@moss-spartans.epoch.ncsc.mil>
* Stephen Smalley (sds@tycho.nsa.gov) wrote:
> On Fri, 2005-05-20 at 10:01 -0700, Chris Wright wrote:
> > > +struct audit_aux_data_avc {
> >
> > I guess it's not really avc specific (although it's primary user).
>
> You mean generalize the struct for possible re-use by other audit
> helpers but keep the type value and function distinct?
> audit_aux_data_path? Analogous to struct path in namei.c.
Yup.
> > Won't this change the order quite a bit? And how do you correlate path
> > vs. exe, etc.? Oh, I see, you're not using it for exe...
>
> Could be an issue for syscalls that involve multiple files, e.g. rename.
> We are at least still logging the last component name, device, and inode
> number with the avc message, and only deferring logging of the full
> pathname.
If it works for you, it's really only effecting your messages at this point.
I took David's idea to mean replace audit_log_d_path altogether, and all
paths logged on exit with aux data.
thanks,
-chris
next prev parent reply other threads:[~2005-05-20 17:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 16:24 2.6.12-rc4-mm2 - sleeping function called from invalid context at mm/slab.c:2502 Valdis.Kletnieks
2005-05-17 16:55 ` Chris Wright
2005-05-17 17:04 ` David Woodhouse
2005-05-17 17:43 ` Chris Wright
2005-05-18 8:30 ` Herbert Xu
2005-05-18 17:00 ` Chris Wright
2005-05-18 17:52 ` David Woodhouse
2005-05-18 21:29 ` Herbert Xu
2005-05-17 18:01 ` Valdis.Kletnieks
2005-05-19 11:34 ` David Woodhouse
2005-05-19 18:45 ` Valdis.Kletnieks
2005-05-20 14:30 ` Valdis.Kletnieks
2005-05-20 14:59 ` David Woodhouse
2005-05-20 15:09 ` Stephen Smalley
2005-05-20 15:36 ` David Woodhouse
2005-05-20 16:40 ` Stephen Smalley
2005-05-20 16:55 ` David Woodhouse
2005-05-20 16:58 ` Stephen Smalley
2005-05-20 17:26 ` Stephen Smalley
2005-05-20 23:27 ` David Woodhouse
2005-05-20 17:01 ` Chris Wright
2005-05-20 17:05 ` Stephen Smalley
2005-05-20 17:19 ` Chris Wright [this message]
2005-05-20 17:05 ` David Woodhouse
2005-05-20 17:06 ` Stephen Smalley
2005-05-20 16:41 ` Chris Wright
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=20050520171906.GZ27549@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox