From owner-freebsd-security@freebsd.org Tue Jan 16 15:54:24 2018 Return-Path: Delivered-To: freebsd-security@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 3CFBFE7760E for ; Tue, 16 Jan 2018 15:54:24 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7A28F7FFD1 for ; Tue, 16 Jan 2018 15:54:23 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id w0GFsA2a075929 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 16 Jan 2018 17:54:13 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w0GFsA2a075929 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w0GFsA0o075928; Tue, 16 Jan 2018 17:54:10 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 16 Jan 2018 17:54:10 +0200 From: Konstantin Belousov To: Gordon Tetlow Cc: freebsd-security Subject: Re: Response to Meltdown and Spectre Message-ID: <20180116155410.GC55707@kib.kiev.ua> References: <20180108175751.GH9701@gmail.com> <20180113161026.GR1684@kib.kiev.ua> <20180116095730.GP1684@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jan 2018 15:54:24 -0000 On Tue, Jan 16, 2018 at 07:31:43AM -0800, Gordon Tetlow wrote: > On Tue, Jan 16, 2018 at 1:57 AM, Konstantin Belousov > wrote: > > On Mon, Jan 15, 2018 at 09:20:24PM -0800, Gordon Tetlow wrote: > >> On Sat, Jan 13, 2018 at 8:10 AM, Konstantin Belousov > >> wrote: > >> > On Mon, Jan 08, 2018 at 09:57:51AM -0800, Gordon Tetlow wrote: > >> >> Meltdown (CVE-2017-5754) > >> >> ~~~~~~~~~~~~~~~~~~~~~~~~ > >> >> Initial work can be tracked at https://reviews.freebsd.org/D13797. > >> >> Please note this is a work in progress and some stuff is likely to be > >> >> broken. > >> > I consider this patch as ready for review now. > >> > >> Awesome! So, what's next? Do we have some testers we can solicit to > >> beat on this? I believe des@ had a test case to try out? Based on > >> where we are, what needs to be done to get this into the tree? > >> Secondarily, what's needed to get this in shape for 10.3/10.4/11.1? > > > > As expected, nothing happens WRT review. > > Who is a good person to review this? alc? (I can't think of any other > VM people out there). amd64 pmap is only smaller part of the patch, the trampoline code is IMO both more risky and more complicated. > > > Peter tested the patch, it seems to be fine. I put shims to allow i386 > > to compile. My idea is to flip the default to non-PTI and commit the > > patch as is today. > > Is there a reason to leave the PTI off in CURRENT? I'd rather turn it > on and break some stuff to get the testing coverage than to leave it > off. Because there is a lot of whine about performance, including uncertainity about several CPU families, because we still do not have have a test tool, and because there are some bits broken more than in non-pti kernel.