linux-kernel - Re: [PATCH] x86, tsc: Fix a preemption leak in restore_sched_clock

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: <AANLkTinr-pUYYGhfRoxjN6si294DOBmPrURWD3z+fTU+@mail.gmail.com>
Date:	Sat, 11 Sep 2010 08:59:37 +0800
From:	Jeff Chua <jeff.chua.linux@...il.com>
To:	Suresh Siddha <suresh.b.siddha@...el.com>,
	Peter Zijlstra <peterz@...radead.org>
Cc:	Nico Schottelius <nico-nospam@...ottelius.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Nico Schottelius <nico-linux-20100709@...ottelius.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Florian Pritz <flo@...n.at>,
	"stable@...nel.org" <stable@...nel.org>,
	Ingo Molnar <mingo@...e.hu>, "Brown, Len" <lenb@...nel.org>
Subject: Re: [PATCH] x86, tsc: Fix a preemption leak in restore_sched_clock_state()

On Sat, Sep 11, 2010 at 5:01 AM, Suresh Siddha
<suresh.b.siddha@...el.com> wrote:
> On Fri, 2010-09-10 at 13:32 -0700, Peter Zijlstra wrote:
>> D'0h !! *facepalm*
>>
>> Shame on me for not spotting that sooner.

It was a hard one to catch.

> Thanks for looking at this and thanks to Jeff for reporting.
>
> Original patch was marked as stable for 2.6.32+, so we need to make sure
> that Greg picks up this piece too along with the original patch.

Verified that it indeed fixed the problem!

Thanks for fixing this.

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