Date: Thu, 4 Jan 2018 09:39:49 +0800 From: blubee blubeeme <gurenchan@gmail.com> To: Mark Heily <mark@heily.com> Cc: Warner Losh <imp@bsdimp.com>, Michael Butler <imb@protected-networks.net>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: Intel CPU design flaw - FreeBSD affected? Message-ID: <CALM2mEmh7C=G899zQfE5yV6AUgNTgWO2pQ8-x-3acoZR3n3JCA@mail.gmail.com> In-Reply-To: <CAGfo=8kDVFvuXVf0572LvBY6e3F0XrxDrj_YE6A9puc3T1S3eQ@mail.gmail.com> References: <9dda0496-be16-35c6-6c45-63d03b218ccb@protected-networks.net> <CANCZdfra8iS6ptP9Ct401sLum2mZi4dg0KTnkayQjUMbyDc4pQ@mail.gmail.com> <CAGfo=8kDVFvuXVf0572LvBY6e3F0XrxDrj_YE6A9puc3T1S3eQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 4, 2018 at 8:51 AM, Mark Heily <mark@heily.com> wrote: > On Jan 2, 2018 19:05, "Warner Losh" <imp@bsdimp.com> wrote: > > The register article says the specifics are under embargo still. That wou= ld > make it hard for anybody working with Intel to comment publicly on the fl= aw > and any mitigations that may be underway. It would be unwise to assume th= at > all the details are out until the embargo lifts. > > > Details of the flaws are now published at: > > https://meltdownattack.com > > > Warner > > On Jan 2, 2018 4:13 PM, "Michael Butler" <imb@protected-networks.net> > wrote: > > > Has any impact assessment been made as to FreeBSD's exposure or > > mitigation strategies? > > > > 'Kernel memory leaking' Intel processor design flaw forces Linux, > > Windows redesign - The Register > > > > Other OSes will need an update, performance hits loom A fundamental > > design flaw in Intel's processor chips has forced a significant redesig= n > > of the Linux and Windows kernels to defang the chip-level security bug.= =E2=80=A6 > > Programmers are scrambling to overhaul the open-source Linux kernel's > > virtual memory system. Meanwhile, Microsoft is expected to publicly > > introduce necessary changes to its Windows operating system in this > > month's Patch Tuesday ... > > > > https://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/ > > > > imb > > > > _______________________________________________ > > 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" > > > _______________________________________________ > 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= " > _______________________________________________ > 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= " > This is insane... And to think a few months ago people were complaining that Ryzen processors and specifically Threadripper might be insecure in data centers, ha. This is a massive clusterfk
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALM2mEmh7C=G899zQfE5yV6AUgNTgWO2pQ8-x-3acoZR3n3JCA>