From: "R, Sricharan" <r.sricharan@ti.com>
To: linux-mm@kvack.org
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>, linux-omap@vger.kernel.org
Subject: Re: Crash with VMALLOC api
Date: Sat, 23 Jun 2012 12:02:13 +0530 [thread overview]
Message-ID: <CAJ7qFScaFM5UHkjUe_wayB6rQQv31i6fN_3+uDh9+j15n88gig@mail.gmail.com> (raw)
In-Reply-To: <CAJ7qFSdiGw1krDbWg6HvwBymp2gwrYKb8UuA00wSP0rgZi-EMw@mail.gmail.com>
Hi,
BTW i was facing the issue on OMAP4430 SDP platform with
mainline.
Thanks,
Sricharan
On Sat, Jun 23, 2012 at 11:28 AM, R, Sricharan <r.sricharan@ti.com> wrote:
> Hi,
> I am observing a below crash with VMALLOC call on mainline kernel.
> The issue happens when there is insufficent vmalloc space.
> Isn't it expected that the API should return a NULL instead of crashing when
> there is not enough memory?. This can be reproduced with succesive vmalloc
> calls for a size of about say 10MB, without a vfree, thus exhausting
> the memory.
>
> Strangely when vmalloc is requested for a large chunk, then at that time API
> does not crash instead returns a NULL correctly.
>
> Please correct me if my understanding is not correct..
>
> --------------------------------------------------------------------------------------
>
> [ 345.059841] Unable to handle kernel paging request at virtual
> address 90011000
> [ 345.067063] pgd = ebc34000
> [ 345.069793] [90011000] *pgd=00000000
> [ 345.073383] Internal error: Oops: 5 [#1] PREEMPT SMP ARM
> [ 345.078685] Modules linked in: bcmdhd cfg80211 inv_mpu_ak8975
> inv_mpu_kxtf9 mpu3050
> [ 345.086380] CPU: 0 Tainted: G W (3.4.0-rc1-05660-g0d4b175 #1)
> [ 345.093351] PC is at vmap_page_range_noflush+0xf0/0x200
> [ 345.098569] LR is at vmap_page_range+0x14/0x50
> [ 345.103005] pc : [<c01091c8>] lr : [<c01092ec>] psr: 80000013
> [ 345.103009] sp : ebc41e38 ip : fe000fff fp : 00002000
> [ 345.114472] r10: c0a78480 r9 : 90011000 r8 : c096e2ac
> [ 345.119685] r7 : 90011000 r6 : 00000000 r5 : fe000000 r4 : 00000000
> [ 345.126198] r3 : 50011452 r2 : f385c400 r1 : fe000fff r0 : f385c400
> [ 345.132713] Flags: Nzcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
> [ 345.139835] Control: 10c5387d Table: abc3404a DAC: 00000015
>
> Thanks,
> Sricharan
--
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:[~2012-06-23 6:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-23 5:58 R, Sricharan
2012-06-23 6:32 ` R, Sricharan [this message]
2012-06-24 20:47 ` David Rientjes
2012-06-25 17:23 ` R, Sricharan
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=CAJ7qFScaFM5UHkjUe_wayB6rQQv31i6fN_3+uDh9+j15n88gig@mail.gmail.com \
--to=r.sricharan@ti.com \
--cc=linux-mm@kvack.org \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.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