linux-kernel - Re: [PATCH v3, x86]: Use selfsnoop HW feature to manage conflicting memory types

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]

Message-ID: <AANLkTi=7TwkZOHDcswXp-SgEzs4Ms12xcQ0+Ga9t21DT@mail.gmail.com>
Date:	Sun, 14 Nov 2010 21:37:33 +0100
From:	Uros Bizjak <ubizjak@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	x86@...nel.org
Subject: Re: [PATCH v3, x86]: Use selfsnoop HW feature to manage conflicting
 memory types

On Sun, Nov 14, 2010 at 7:33 PM, Uros Bizjak <ubizjak@...il.com> wrote:
> Hello!
>
> Attached patch enhances v2 patch at [1] to disable selfsnoop with a
> kernel command line parameter. The feature is also disabled on all
> processors earlier than Core 2 due to Pentium-M errata.
>
> I have investigated the erratas in this area and documented the one
> found in the source.
>
> The patch was tested on 4 core i7 (8 threads) and there were no
> problems at all with the patched kernel.

Also, I'd like to point out that similar change was introduced in
FreeBSD as part of r195749 in July 2009, see [1].

[1] http://svn.freebsd.org/viewvc/base?view=revision&revision=195749

Uros.
--
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/