From: David Woodhouse <dwmw2@infradead.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 16:36:53 +0100 [thread overview]
Message-ID: <1116603414.29037.36.camel@localhost.localdomain> (raw)
In-Reply-To: <1116601757.12489.130.camel@moss-spartans.epoch.ncsc.mil>
On Fri, 2005-05-20 at 11:09 -0400, Stephen Smalley wrote:
> The lock is being held by the af_unix code (unix_state_wlock), not
> avc_audit; the AVC is called under all kinds of circumstances (softirq,
> hard irq, caller holding locks on relevant objects) for permission
> checking and must never sleep.
>
> One option might be to defer some of the AVC auditing to the audit
> framework (e.g. save the vfsmount and dentry on the current audit
> context and let audit_log_exit perform the audit_log_d_path).
Yeah, maybe. Assuming you pin them, it's easy enough to hang something
off the audit context's aux list which refers to them. I'm really not
that fond of the idea of allocating a whole PATH_MAX with GFP_ATOMIC.
--
dwmw2
next prev parent reply other threads:[~2005-05-20 15:39 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 [this message]
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
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=1116603414.29037.36.camel@localhost.localdomain \
--to=dwmw2@infradead.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