From: David Woodhouse <dwmw2@infradead.org>
To: Linux Audit Discussion <linux-audit@redhat.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
netdev@oss.sgi.com, "David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.12-rc4-mm2 - sleeping function called from invalid context at mm/slab.c:2502
Date: Wed, 18 May 2005 18:52:35 +0100 [thread overview]
Message-ID: <1116438756.25594.76.camel@localhost.localdomain> (raw)
In-Reply-To: <20050518170033.GT27549@shell0.pdx.osdl.net>
On Wed, 2005-05-18 at 10:00 -0700, Chris Wright wrote:
> * Herbert Xu (herbert@gondor.apana.org.au) wrote:
> > Guys, please CC netdev on issues like this.
>
> Sorry Herbert, we hadn't yet concluded that it's not an issue that we
> need to resolve within audit.
I suspect that it _is_ an issue we can resolve entirely within audit
code. See the patch I posted half an hour or so ago to the linux-audit
list. If we agree on that approach, I'll do the equivalent for the git
tree either later this evening or tomorrow.
I've reverted your recent change to put audit messages directly into
skbs "in order to eliminate the extra copy", on the basis that it
blatantly wasn't having that effect anyway. Now we copy from the
audit_buffer into an optimally-sized skb which netlink_trim() won't have
to mangle. I've also removed the skb_get() immediately before
netlink_send() which always made me unhappy.
--
dwmw2
next prev parent reply other threads:[~2005-05-18 17:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200505171624.j4HGOQwo017312@turing-police.cc.vt.edu>
[not found] ` <20050517165528.GB27549@shell0.pdx.osdl.net>
[not found] ` <1116349464.23972.118.camel@hades.cambridge.redhat.com>
[not found] ` <20050517174300.GE27549@shell0.pdx.osdl.net>
2005-05-18 8:30 ` 2.6.12-rc4-mm2 - sleeping function called from invalid context at mm/slab.c:2502 Herbert Xu
2005-05-18 17:00 ` Chris Wright
2005-05-18 17:52 ` David Woodhouse [this message]
2005-05-18 21:29 ` Herbert Xu
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=1116438756.25594.76.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).