From: Andrew Morton <akpm@linux-foundation.org>
To: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
Cc: Christoph Lameter <clameter@sgi.com>,
LKML <linux-kernel@vger.kernel.org>,
Arjan van de Ven <arjan@infradead.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: NULL pointer in kmem_cache_alloc with 2.6.25-rc1
Date: Mon, 18 Feb 2008 04:59:18 -0800 [thread overview]
Message-ID: <20080218045918.2b80ee08.akpm@linux-foundation.org> (raw)
In-Reply-To: <1203058021.3027.143.camel@ymzhang>
On Fri, 15 Feb 2008 14:47:01 +0800 "Zhang, Yanmin" <yanmin_zhang@linux.intel.com> wrote:
> Call Trace:
> [<ffffffff805e0024>] ? __alloc_skb+0x31/0x121
> [<ffffffff805dc389>] ? sock_alloc_send_skb+0x77/0x1d2
> [<ffffffff80243897>] ? autoremove_wake_function+0x0/0x2e
> [<ffffffff805e12d5>] ? memcpy_fromiovec+0x36/0x66
> [<ffffffff80636ec0>] ? unix_stream_sendmsg+0x165/0x333
> [<ffffffff805d9863>] ? sock_aio_write+0xd1/0xe0
> [<ffffffff80227834>] ? __wake_up_common+0x41/0x74
> [<ffffffff8027d267>] ? do_sync_write+0xc9/0x10c
> [<ffffffff80265fbb>] ? __do_fault+0x382/0x3cd
> [<ffffffff80243897>] ? autoremove_wake_function+0x0/0x2e
> [<ffffffff80268840>] ? handle_mm_fault+0x38a/0x70d
> [<ffffffff806afd39>] ? error_exit+0x0/0x51
> [<ffffffff80228008>] ? __dequeue_entity+0x1c/0x32
> [<ffffffff8027d9bb>] ? vfs_write+0xc0/0x136
> [<ffffffff8027dee5>] ? sys_write+0x45/0x6e
> [<ffffffff8020bdcb>] ? system_call_after_swapgs+0x7b/0x80
off-topic, but... Why are all the backtrace decodes here marked as
being unreliable?
next prev parent reply other threads:[~2008-02-18 13:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 6:47 NULL pointer in kmem_cache_alloc with 2.6.25-rc1 Zhang, Yanmin
2008-02-15 16:42 ` Christoph Lameter
2008-02-19 7:03 ` Zhang, Yanmin
2008-02-19 7:38 ` Pekka Enberg
2008-02-27 22:15 ` Christoph Lameter
2008-02-18 12:59 ` Andrew Morton [this message]
2008-02-18 16:52 ` Arjan van de Ven
2008-02-19 3:14 ` Zhang, Yanmin
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=20080218045918.2b80ee08.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yanmin_zhang@linux.intel.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