From: Christoph Lameter <cl@gentwo.org>
To: Wladislav Wiebe <wladislav.kw@gmail.com>
Cc: penberg@kernel.org, linux-mm@kvack.org,
linuxppc-dev@lists.ozlabs.org, dedekind1@gmail.com,
dwmw2@infradead.org, linux-mtd@lists.infradead.org
Subject: Re: mm/slab: ppc: ubi: kmalloc_slab WARNING / PPC + UBI driver
Date: Wed, 31 Jul 2013 13:59:18 +0000 [thread overview]
Message-ID: <000001403506934c-ce0f08c9-240a-4464-84aa-f31664b86a74-000000@email.amazonses.com> (raw)
In-Reply-To: <51F8F827.6020108@gmail.com>
On Wed, 31 Jul 2013, Wladislav Wiebe wrote:
> on a PPC 32-Bit board with a Linux Kernel v3.10.0 I see trouble with kmalloc_slab.
> Basically at system startup, something request a size of 8388608 b,
> but KMALLOC_MAX_SIZE has 4194304 b in our case. It points a WARNING at:
> ..
> NIP [c0099fec] kmalloc_slab+0x60/0xe8
> LR [c0099fd4] kmalloc_slab+0x48/0xe8
> Call Trace:
> [ccd3be60] [c0099fd4] kmalloc_slab+0x48/0xe8 (unreliable)
> [ccd3be70] [c00ae650] __kmalloc+0x20/0x1b4
> [ccd3be90] [c00d46f4] seq_read+0x2a4/0x540
> [ccd3bee0] [c00fe09c] proc_reg_read+0x5c/0x90
> [ccd3bef0] [c00b4e1c] vfs_read+0xa4/0x150
> [ccd3bf10] [c00b500c] SyS_read+0x4c/0x84
> [ccd3bf40] [c000be80] ret_from_syscall+0x0/0x3c
> ..
>
> Do you have any idea how I can analyze where these 8388608 b coming from?
It comes from the kmalloc in seq_read(). And 8M read from the proc
filesystem? Wow. Maybe switch the kmalloc to vmalloc()?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-07-31 13:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 11:42 Wladislav Wiebe
2013-07-31 13:59 ` Christoph Lameter [this message]
[not found] ` <alpine.DEB.2.02.1307310858150.30572@gentwo.org>
2013-07-31 15:17 ` Christoph Lameter
[not found] ` <alpine.DEB.2.02.1307311015320.30997@gentwo.org>
2013-07-31 15:45 ` Christoph Lameter
2013-07-31 16:33 ` Wladislav Wiebe
2013-07-31 17:04 ` Christoph Lameter
2013-08-06 7:15 ` Wladislav Wiebe
2013-08-06 14:57 ` Christoph Lameter
2013-07-31 17:34 ` Aaro Koskinen
2013-08-01 8:50 ` Wladislav Wiebe
2013-08-12 11:06 ` Wladislav Wiebe
2013-08-12 23:24 ` Benjamin Herrenschmidt
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=000001403506934c-ce0f08c9-240a-4464-84aa-f31664b86a74-000000@email.amazonses.com \
--to=cl@gentwo.org \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mm@kvack.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=penberg@kernel.org \
--cc=wladislav.kw@gmail.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