Date: Thu, 5 Jul 2018 11:06:27 -0700 From: Conrad Meyer <cem@freebsd.org> To: "Stephen J. Kiernan" <stevek@freebsd.org> Cc: "freebsd-arch@freebsd.org" <arch@freebsd.org> Subject: Re: Veriexec Message-ID: <CAG6CVpV7Cf1DTx0aMoWaisHbrF-J6SbiFuJoJ%2Bj6dKjbEPMQ9A@mail.gmail.com> In-Reply-To: <CAEm%2B2uWJTyF1QyYraGxNS3TpJNPyT0hMnsVAXj%2BUSayH%2BJi4nA@mail.gmail.com> References: <CAG6CVpW3xL5pmiU91WgzXKram7ogMYNzBF3a-ggaXjkD3fMbWw@mail.gmail.com> <CAEm%2B2uWJTyF1QyYraGxNS3TpJNPyT0hMnsVAXj%2BUSayH%2BJi4nA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 5, 2018 at 10:48 AM, Stephen J. Kiernan <stevek@freebsd.org> wrote: > On Tue, Jul 3, 2018 at 7:09 PM, Conrad Meyer <cem@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG6CVpV7Cf1DTx0aMoWaisHbrF-J6SbiFuJoJ%2Bj6dKjbEPMQ9A>