Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 5 Jan 2018 02:27:40 +0800
From:      blubee blubeeme <gurenchan@gmail.com>
To:        "Klaus P. Ohrhallinger" <k@7he.at>
Cc:        FreeBSD current <freebsd-current@freebsd.org>
Subject:   Re: Intel CPU design flaw - FreeBSD affected? // disabling _R_DTSC
Message-ID:  <CALM2mEk1Dtd9f0gc6pScjVizr-2j5N6YRXiJM%2BDqm5maejd5NQ@mail.gmail.com>
In-Reply-To: <52b2f48c-332c-8984-838f-4902da0ebc81@7he.at>
References:  <9dda0496-be16-35c6-6c45-63d03b218ccb@protected-networks.net> <18376c97-3c0d-49c8-9483-96b95a84f3f1@7he.at> <52b2f48c-332c-8984-838f-4902da0ebc81@7he.at>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jan 5, 2018 at 2:25 AM, Klaus P. Ohrhallinger <k@7he.at> wrote:

> On 04.01.2018 19:23, Klaus P. Ohrhallinger wrote:
> > Hello,
> >
> > I disabled the ldtsc and ldtscp instructions for usermode on one of my
> > production servers:
> >
>
> Oops, RDTSC of course.
>
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>
I'd love to see if RISC-V is vulnerable to this?

I think they are in the best position to capitalize on this clusterfk...



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALM2mEk1Dtd9f0gc6pScjVizr-2j5N6YRXiJM%2BDqm5maejd5NQ>