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: <20100118112619.GA8387@redhat.com>
Date:	Mon, 18 Jan 2010 13:26:22 +0200
From:	"Michael S. Tsirkin" <m.s.tsirkin@...il.com>
To:	Pekka Enberg <penberg@...helsinki.fi>
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

On Sun, Jan 17, 2010 at 07:23:35PM +0200, Pekka Enberg wrote:
> On Sun, Jan 17, 2010 at 6:43 PM, Pekka Enberg <penberg@...helsinki.fi> wrote:
> > 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.
> 
> OK, confirmed. I can see the "flashing" bug with 2.6.32 as well. It
> just takes more time to trigger than in 2.6.33-rc1. I am going back to
> test 2.6.31 now.


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?

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