linux-kernel - Re: 3.0.1: pagevec_lookup+0x1d/0x30, SLAB issues?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.02.1109111837200.19558@p34.internal.lan>
Date:	Sun, 11 Sep 2011 18:44:17 -0400 (EDT)
From:	Justin Piszcz <jpiszcz@...idpixels.com>
To:	linux-kernel@...r.kernel.org
cc:	Alan Piszcz <ap@...arrain.com>, mlin@...pku.edu.cn
Subject: Re: 3.0.1: pagevec_lookup+0x1d/0x30, SLAB issues?

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.

Justin.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/