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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <84144f021001170843s67afae24oaabf09e9b13af8db@mail.gmail.com>
Date:	Sun, 17 Jan 2010 18:43:40 +0200
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	Florian Mickler <florian@...kler.org>
Cc:	linux-kernel@...r.kernel.org, kernel-testers@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	"Michael S. Tsirkin" <m.s.tsirkin@...il.com>
Subject: Re: 2.6.33-rc2: Reported regressions from 2.6.32

Hi Florian,

(Please don't trim the cc list.)

On Sun, Jan 17, 2010 at 5:17 PM, Florian Mickler <florian@...kler.org> wrote:
> on which side of the merge? linus or drm?
> i.e. it is to be expected to be before the merge, (but on the drm side)
> so don't get confused... or did i misunderstood the situation?

Like I said, don't read too much into the results but the current
situation looks like the regression happened _after_ 2.6.32 but before
any of the DRM code was merged to 2.6.33-rc1. I don't think that makes
much sense which is why I'm back to testing 2.6.32 more to see if the
bug is there already but just harder to trigger for whatever reason.

                        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/