linux-kernel - Re: 2.6.33-rc2: Reported regressions from 2.6.32

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] [day] [month] [year] [list]

Message-ID: <4B5447D8.9060701@cs.helsinki.fi>
Date:	Mon, 18 Jan 2010 13:36:56 +0200
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	"Michael S. Tsirkin" <m.s.tsirkin@...il.com>
CC:	Florian Mickler <florian@...kler.org>,
	linux-kernel@...r.kernel.org, kernel-testers@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: 2.6.33-rc2: Reported regressions from 2.6.32

Michael S. Tsirkin kirjoitti:
> Well, I've been using 2.6.32 day to day since it came out and never saw
> this bug there. What do you do to trigger this bug?

It usually triggers when I'm building a kernel. I don't have a good test 
case for this, I just need to use the machine long enough to see a 
flash. And it's pretty hard to trigger in 2.6.32.

I am now bisecting in the middle of the i915 merge in 2.6.31 so if 
people know there are suspicious commits that I should try to revert, 
please let me know.

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