From owner-freebsd-current@freebsd.org Thu Jan 4 01:39:51 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 24D9EEBBD25 for ; Thu, 4 Jan 2018 01:39:51 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DC590713B1 for ; Thu, 4 Jan 2018 01:39:50 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x22f.google.com with SMTP id m11so161002iti.1 for ; Wed, 03 Jan 2018 17:39:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=YgWTQY961clYZ+0IMwVbOEIaxWSZoll9kBETEAprkA0=; b=ANeQPRW/cNaUYOK/2rDdZUuFpdpVaCscwFsAeZ0ZtRX7dUJToniSstDpQDcLRPrpNc 4I5Umvo+l+VXEanMPSN0ea0rOnDSJV+zBsnkm2vHaWPl7B/MNYQOwbzs4yPlqlb9B3JL 6eL0dvQzICq3nWBjDOTxcKGSsGLjAaHtdVuxfAfx6w/Elo5b5dE9G+MLzpYv5M3N6OAG ZR1I+rK0RKSFGgoinxKH1dBo5LbmawJ7nHqICUDG7PnP0PN3qzZVE5zsfOhq4J3nbGwX jl16Hi9x4JbwnKG17IYpyWXYrVWGrIhgDejwVBk8Q3ZPAoBLM66hU0uIf+Zch2+C1Da/ upmg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=YgWTQY961clYZ+0IMwVbOEIaxWSZoll9kBETEAprkA0=; b=HE08dfgsnIl7K7ggInLQPVU8GOqUvAt2XzNirH4sOPj2cl0H/DlKMBbvEfmdRqd4Lz kri1f4wWJ7ptZtV7raEx643g4Ko31rZJx3gAOTBow3K+HM4cBT7lVLda9i2guFypTxi7 zL41msoPwGdDs+2RTK/OxUWVhw2Cfvao8jRIrsbk++9r6U9ZwS+qvpPWE+c6+EtTADqM Vp7qGnELb1cQo79ijeVe0SmzLCklcONc7tQ2TEaXLEy5dNlM1MH5bTwpWzMpaQzcaHSt 7Z29F2HmG6scQ0dxdEVngIOMk+18GBJ3WIDHyQo0IkavSwKi4wPpslNdSIh/URWux1te bWuQ== X-Gm-Message-State: AKGB3mKX/4lKnLWmh4HWB78XIKirscikLcHtgkCbnTERQ1Uas7Y13lFA c5hgiA3u5tPIR9iBTe1BrIkeMSbIWMrHk9LirVC0cw== X-Google-Smtp-Source: ACJfBouJH+SaEhmEWRw8PpT9Ww3WXMfsgyCciRnf34GzBf4Cz4JreqxLEe0oHIbjQlU/1KRn13dGk3+dzwWinrkvXsQ= X-Received: by 10.36.221.147 with SMTP id t141mr3959351itf.140.1515029990219; Wed, 03 Jan 2018 17:39:50 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.164.203 with HTTP; Wed, 3 Jan 2018 17:39:49 -0800 (PST) In-Reply-To: References: <9dda0496-be16-35c6-6c45-63d03b218ccb@protected-networks.net> From: blubee blubeeme Date: Thu, 4 Jan 2018 09:39:49 +0800 Message-ID: Subject: Re: Intel CPU design flaw - FreeBSD affected? To: Mark Heily Cc: Warner Losh , Michael Butler , freebsd-current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jan 2018 01:39:51 -0000 On Thu, Jan 4, 2018 at 8:51 AM, Mark Heily wrote: > On Jan 2, 2018 19:05, "Warner Losh" 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" > 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