Date: Wed, 3 Jan 2018 10:23:20 -0900 From: Royce Williams <royce@techsolvency.com> To: freebsd-security@freebsd.org Subject: Re: Intel hardware bug Message-ID: <CA%2BE3k90d21gazzxFOAY2ZBD01HPXbn9v_whOpG1yVvPPCpuysA@mail.gmail.com> In-Reply-To: <104827876.20180103220138@serebryakov.spb.ru> References: <477ab39d-286d-d9a2-d31e-fd5f7f1679a8@sentex.net> <7692356.NWgAdSPsLq@elisha.atlnet> <104827876.20180103220138@serebryakov.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 3, 2018 at 10:01 AM, Lev Serebryakov <lev@freebsd.org> wrote: > Hello Joey, > > Wednesday, January 3, 2018, 4:56:50 AM, you wrote: > > > No way around it. It's hardware FAIL, and ignoring it isn't an option > since > > it's apparently a huge hole. > Looks like there IS way around it and it was "silently" committed to Linux > > http://pythonsweetness.tumblr.com/post/169166980422/the- > mysterious-case-of-the-linux-page-table > > But TLB flush on each syscall (twice) will slow down system, of course, so > there should be option to disable it. > For what it's worth, this purports to be a PoC: https://gist.github.com/dougallj/f9ffd7e37db35ee953729491cfb71392 Royce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BE3k90d21gazzxFOAY2ZBD01HPXbn9v_whOpG1yVvPPCpuysA>