linux-kernel - Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression

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

Date:	Tue, 26 Aug 2008 15:28:15 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	David Witbrodt <dawitbro@...global.net>
Cc:	Yinghai Lu <yhlu.kernel@...il.com>,
	Linux-kernel Mailing List <linux-kernel@...r.kernel.org>,
	the arch/x86 maintainers <x86@...nel.org>, stable@...nel.org
Subject: Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user
	with the same regression


* David Witbrodt <dawitbro@...global.net> wrote:

> > Note that the hpet fix is now upstream  [...]
> 
> Any chance this can be applied to stable 2.6.26.x?
> 
> Half of my agenda was selfish (to be sure future kernels would not 
> hang on my 2 home servers), but the other half was to ensure that 
> Debian would not have hanging kernels in their next stable release.

it's a backport candidate, but i think we should wait a bit with that, 
until after .27-rc5 or -rc6, to make sure there are no side-effects.

The upstream commit is:

 commit a2bd7274b47124d2fc4dfdb8c0591f545ba749dd
 Author: Yinghai Lu <yhlu.kernel@...il.com>
 Date:   Mon Aug 25 00:56:08 2008 -0700

    x86: fix HPET regression in 2.6.26 versus 2.6.25, check hpet against BAR, v3

btw., are both of your systems that were hanging fixed by this commit?

> Thanks again for all the hard work,

you are welcome!

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