[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAF1ivSZQ=KKC0gAk93eMVwLSCbeEWr=k6YszuE=sb1+Ue521vw@mail.gmail.com>
Date: Wed, 14 Sep 2011 16:56:15 +0800
From: Lin Ming <mlin@...pku.edu.cn>
To: Justin Piszcz <jpiszcz@...idpixels.com>
Cc: linux-kernel@...r.kernel.org, Alan Piszcz <ap@...arrain.com>,
"Li, Shaohua" <shaohua.li@...el.com>,
Andrew Morton <akpm@...gle.com>
Subject: Re: 3.0.1: pagevec_lookup+0x1d/0x30, SLAB issues?
On Mon, Sep 12, 2011 at 6:44 AM, Justin Piszcz <jpiszcz@...idpixels.com> wrote:
>
>
> On Sun, 11 Sep 2011, Justin Piszcz wrote:
>
>> Hi,
>>
>> With 3.0.1 now and all options compiled in and threadirqs removed, I get
>> the same error this user is seeing:
>> http://www.gossamer-threads.com/lists/linux/kernel/1424997
>>
>
> Hello Lin,
>
> I missed your mail (sender IP is in a CIDR blacklist), disabled &
> whitelisted for now:
> http://marc.info/?l=linux-kernel&m=131567477126674&w=2
>
> I've enabled this and I will post a new e-mail / output if it happens
> again with debug enabled for SLAB.
>
> Response to your e-mail:
>
>> Could you tell how to reproduce this?
>
> Running a lot of processes at the same time (memory/cpu+i/o)
>
>> And would you please turn on more debug options to capture more info?
>
> Yup, done now; however, I am using SLAB, not SLUB; so I've enabled:
>
> -> [*] Debug slab memory allocations -> [*] Memory leak debugging -> [*]
> Debug VM
>
>> CONFIG_SLUB_DEBUG=y
>> CONFIG_SLUB_DEBUG_ON=y
>> CONFIG_DEBUG_VM=y
>
> Please let me know if there are any other options you think would be useful
> to enable or if this should be good, if it recurs again-- as noted above
> I will post an update.
Hi, Justin
There is a similar bug report at:
http://marc.info/?t=131594190600005&r=1&w=2
The attached patch from Shaohua fixed the bug.
Could you have a try it?
Lin Ming
View attachment "filemap-dbg.patch" of type "text/x-patch" (1023 bytes)
Powered by blists - more mailing lists