linux-kernel - Re: [Bug #11330] int3: 0000 in tsc_read_refs when using powernow

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]

Date:	Mon, 18 Aug 2008 20:33:33 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Alok Kataria <akataria@...are.com>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	Daniel Hecht <dhecht@...are.com>,
	Mikko Vinni <mmvinni@...oo.com>,
	the arch/x86 maintainers <x86@...nel.org>
Subject: Re: [Bug #11330] int3: 0000 in tsc_read_refs when using powernow_k7


* Alok Kataria <akataria@...are.com> wrote:

> On Sat, 2008-08-16 at 12:02 -0700, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.26.  Please verify if it still should be listed and let me know
> > (either way).
> 
> There is this fix 
> 
> commit d554d9a4295dd0595d12eeccbc55d1f495b15176
> Author: Marcin Slusarz <marcin.slusarz@...il.com>
> Date:   Mon Aug 11 00:07:44 2008 +0200
> 
>     x86, tsc: fix section mismatch warning
> 
> which is in x86/tip-master which fixes this issue. 
> I don't see the fix in the mainline tree yet. 
> 
> Maybe Ingo, has it queued, for upstream ?
> Ingo, other than a section mismatch warning it also fixes a real bug.

yeah, hpa queued it up into x86/urgent as well earlier today, it will go 
out with the next pull request.

	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/