linux-kernel - Re: rt2800usb: memory corruption?

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:	Sun, 02 Aug 2009 08:29:06 +0200
From:	Mike Galbraith <efault@....de>
To:	Pavel Roskin <proski@....org>
Cc:	linux-wireless <linux-wireless@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	"John W. Linville" <linville@...driver.com>
Subject: Re: rt2800usb: memory corruption?

On Sun, 2009-08-02 at 07:16 +0200, Mike Galbraith wrote:
> On Sat, 2009-08-01 at 20:21 -0400, Pavel Roskin wrote:
> > On Sat, 2009-08-01 at 12:55 +0200, Mike Galbraith wrote:
> > 
> > > Enabled slub/pagealloc debugging.  First down/rmmod said...
> > 
> > I suggest that you try kmemcheck.  It's very slow, but it finds memory
> > problems when they occur, not when it's too late.
> > 
> > You may want to disable kmemleak and framebuffer support and make sure
> > that X doesn't start, at it will be too slow.  Slub debugging might
> > conflict with kmemcheck, so it's better to disable it.
> 
> 
> I didn't even get as far as down/rmmod.  Kmemcheck fired as soon as the
> interface came up.

Corruption seems to be SMP only.  I cycled down/rmmod/modprobe a few
times with kmemcheck enabled (disables smp unfortunately), kmemcheck
didn't trigger, nor did box have a conniption.

	-Mike

--
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/