netdev - Re: [net-2.6][2.6.38-rc2] panic during stress testing

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]

Date:	Tue, 08 Feb 2011 13:51:13 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	jesse.brandeburg@...el.com
Cc:	netdev@...r.kernel.org, jeffrey.e.pieper@...el.com
Subject: Re: [net-2.6][2.6.38-rc2] panic during stress testing

From: Jesse Brandeburg <jesse.brandeburg@...el.com>
Date: Tue, 08 Feb 2011 10:32:05 -0800

> We are currently testing patches and ran into this panic, doesn't
> immediately seem related to the driver.
> 
> During TCP/UDP ipv4/6 stress testing on 82574L, 2.6.38-rc2 x86_64
> (net-2.6 with e1000e patches under test) gets numerous OOM killer
> messages, followed by a bug/Oops and panic. could not reproduce the
> bug/panic on 2.6.37, but the OOM killer messages are still seen.
> 
> Could well be related somehow to testing with DEBUG_PAGEALLOC enabled.
> 
> panic dump and .config follows:
> 
> BUG: unable to handle kernel paging request at ffffffff81089738
> IP: [<ffffffff812e2139>] dst_destroy+0x4b/0xf3
> PGD 1695067 PUD 1699063 PMD 10001e1 
> Oops: 0003 [#1] PREEMPT SMP DEBUG_PAGEALLOC
> last sysfs file: /sys/devices/system/cpu/cpu3/cache/index2/shared_cpu_map
> CPU 1 
> Modules linked in: nfsd exportfs lockd sunrpc dca e1000e [last unloaded: igb]

So some piece of freed memory is being referenced in dst_destroy(), can you
match dst_destroy+0x4b to a line in that function for your build?

You should always do this when submitting a trace like this.

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html