linux-kernel - Re: Memory corruption with 2.6.32.10, but not with 2.6.34-rc3

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20100401165144.GB1138@suse.de>
Date:	Thu, 1 Apr 2010 09:51:44 -0700
From:	Greg KH <gregkh@...e.de>
To:	Daniel Mack <daniel@...aq.de>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	AKML <linux-arm-kernel@...ts.infradead.org>,
	linux-wireless@...r.kernel.org,
	Sven Neumann <s.neumann@...mfeld.com>
Subject: Re: Memory corruption with 2.6.32.10, but not with 2.6.34-rc3

On Thu, Apr 01, 2010 at 03:21:56PM +0200, Daniel Mack wrote:
> 
> I can cherry-pick things if anyone pin-points something and run
> lont-time tests again. Any pointer appreciated.

Oh, how about running 'git bisect' to try to find the solution?  Just
remember to reverse 'good' and 'bad' for when you tell git bisect what
the results are.

thanks,

greg k-h
--
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/