From owner-freebsd-arch@freebsd.org Thu Jul 5 18:06:35 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CC2111043AEA for ; Thu, 5 Jul 2018 18:06:35 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 5CF028D85E for ; Thu, 5 Jul 2018 18:06:35 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 1BBF51043AE2; Thu, 5 Jul 2018 18:06:35 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 090691043AE1 for ; Thu, 5 Jul 2018 18:06:35 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-it0-f52.google.com (mail-it0-f52.google.com [209.85.214.52]) (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 9722A8D85B; Thu, 5 Jul 2018 18:06:34 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-it0-f52.google.com with SMTP id p4-v6so13204888itf.2; Thu, 05 Jul 2018 11:06:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=A3WH6u2JyP6B6zpYxG66tHgoYLA6Y8/T6apL8jh2aGI=; b=Um/8G0nq9LUisn8SLtk7ei2+mDGhT0TD3sT4abwc8zu5+GuIRIo1oH5VJN+h3Gh+Z0 TNEqRlkg9bNzLd+m2pQs6X5XPVteZ+qtfgcuuUMpJ8O4hVW58m3Y9vSxm8JBeHMqCjne qst9sITKNSb/DR1XoWwE/QSNoRH5nq95OMXNSPn+pWMpe0VmWOsg/2GmMaz5Kn5wR1Lg DnwPnWtVkkadkyUe40XHViBvC8L1hRtGmM0vjphJkd1+ZS7bJvLVtmp7LsWp94G1B3JO uejBD/t6cMnMHo3EPxe7d0/7poww6EEdO7TU4J8zC8N8HIidejZJ80Kpf4Q/kWjRDopJ FA4w== X-Gm-Message-State: APt69E38uvwrZW35/oLKA9pE5zZqGqCR33irRAo0Jc60FCJ0Hz6nSiuK B1hiGY+UkWJT5pEB468ZDrlfEv3/ X-Google-Smtp-Source: AAOMgpfq4uc5MVMeV0uu5O08N5smMpf7ojAEJ8+D7wE+FJysV74KbkPbwjSXcbK0/RxoBLqeuZ+7pQ== X-Received: by 2002:a24:dec5:: with SMTP id d188-v6mr5450443itg.123.1530813988403; Thu, 05 Jul 2018 11:06:28 -0700 (PDT) Received: from mail-it0-f54.google.com (mail-it0-f54.google.com. [209.85.214.54]) by smtp.gmail.com with ESMTPSA id v132-v6sm4007646ita.9.2018.07.05.11.06.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 05 Jul 2018 11:06:28 -0700 (PDT) Received: by mail-it0-f54.google.com with SMTP id 188-v6so13611902ita.5; Thu, 05 Jul 2018 11:06:28 -0700 (PDT) X-Received: by 2002:a02:954d:: with SMTP id y71-v6mr5995980jah.19.1530813988184; Thu, 05 Jul 2018 11:06:28 -0700 (PDT) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 2002:a02:7e0a:0:0:0:0:0 with HTTP; Thu, 5 Jul 2018 11:06:27 -0700 (PDT) In-Reply-To: References: From: Conrad Meyer Date: Thu, 5 Jul 2018 11:06:27 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Veriexec To: "Stephen J. Kiernan" Cc: "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jul 2018 18:06:36 -0000 On Thu, Jul 5, 2018 at 10:48 AM, Stephen J. Kiernan wrote: > On Tue, Jul 3, 2018 at 7:09 PM, Conrad Meyer wrote: >> >> Hi, >> >> It's been two weeks since this went in broken. What's the status? >> Has any progress been made on fixing the glaring issues? > > The backout commits for the veriexecctl bits (r335681) and the hooks > into the build to compile the kernel modules (r335682) happened on > 26 Jun 2018. I'm familiar with these commits, but was asking more about the topic you glanced on below. (Additionally, I don't really like the use of "revert" (as used in the commit message) or "backout" (here) to describe the kernel changes. The bad code is still present, but disabled by default.) > There's work in progress on fixing the issues with the meta-data store > and its use. Ok. Can you elaborate on that progress? Is it happening in public? Is there any kind of (loose) schedule in mind? Thanks, Conrad