From owner-soc-status@FreeBSD.ORG Fri Jun 20 22:02:18 2014 Return-Path: Delivered-To: soc-status@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9A4E84BF; Fri, 20 Jun 2014 22:02:18 +0000 (UTC) Received: from mail-ob0-x234.google.com (mail-ob0-x234.google.com [IPv6:2607:f8b0:4003:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5C5BB2030; Fri, 20 Jun 2014 22:02:18 +0000 (UTC) Received: by mail-ob0-f180.google.com with SMTP id vb8so1755168obc.39 for ; Fri, 20 Jun 2014 15:02:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=/QrA0Meao1yvfBv7ps7Wc2pEa+cm9+L0+hPeMPN16Mg=; b=zDL3iZSKUeq5EjXAWSix4jGQwCvSnV2Ivhj+0dJYuNSOQvIuaG8Wi5FFogxpc5edG1 2zA6oHNNPNUq7axd8ntYnY5qLTb/aLLumNtuu420Df5Vus7CboaTtEtEbYzIsC1m8a4O IeNkxDfn7sOIH7XQvcWRCrkD/nYmvgk/e3JlSlWmNH0sIXLI4+OT5zerH5AIgffhdE9K 30c3HfHzyRJEy0wXDjp2UHki8an/h3MYuvlZQxvsrctaelEEp/35UFxWa1J5NJ8ZAXxU XfwR5gcERZsRY9XCIaWQniLzWzF6YpGjblr5Ny7H6tV5ceLYlqfZWFcey+Q/tftKJYsa o/oQ== MIME-Version: 1.0 X-Received: by 10.60.70.200 with SMTP id o8mr6350453oeu.55.1403301737628; Fri, 20 Jun 2014 15:02:17 -0700 (PDT) Received: by 10.182.216.197 with HTTP; Fri, 20 Jun 2014 15:02:17 -0700 (PDT) Date: Sat, 21 Jun 2014 00:02:17 +0200 Message-ID: Subject: Re: [intel smap, kpatch] weekly report #4 From: Oliver Pinter To: soc-status@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: gavin@freebsd.org X-BeenThere: soc-status@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Summer of Code Status Reports and Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jun 2014 22:02:18 -0000 Hi! At this week i am hunting a triple fault during the boot. This caused by a compiler error, when CPUTYPE in /etc/make.conf was set to core-avx2, after removing this the first phase was done. All of my test running fine and the system are stable. Originally only amd64 implementation required, but I added to i386 too - but the later not yet tested. In next phase I design a proper way how to patch kernel and modules at boot and run-time. What's done: * SMAP for amd64 * test SMAP for amd64 * build framework * VM creation * SMAP for i386 (not tested) * some other tool, that make my life easier The current status can you find on my wiki page. On 6/15/14, Oliver Pinter wrote: > Hi all! > > In the last week I was mostly done with implementation, as you can see > on my wiki page. The most of i386 commits are not tested because a > cross-build problem on amd64 system. > Other resolvable problem are on amd64 system, where the machine triple > faulted, because wrong assembler statements generated with the > compiler. I'm deep in debugging both of two case. This issue are too > in my wiki page under this section: > https://wiki.freebsd.org/SummerOfCode2014/IntelSMAPandKernelPatching#notes > > I have at this week my last exam at Thursday. After that I'm focusing > fully on GSoC. > > On 6/6/14, Oliver Pinter wrote: >> Hi all! >> >> Previous week I started to work on SMAP for amd64 and i386. For amd64 >> many parts are in good state. The codes currently are only compile >> tested, at next week I create a VM, and create run-time tests. For >> i386 started the work on yesterday. >> All of my status can be found on my wiki page. >> >> What's done, but not tested in this week: >> * {amd64,i386} trap handler >> * amd64 initialization >> * {amd64,i386} identification >> * {amd64,i386} exceptions >> * amd64 pmap changes >> * amd64 support.S changes >> * amd64 ia32 compat exceptions >> * i386 ddb extension >> >> At next week I plan to finish all of amd64 things, and most of i386 >> things, and begin to test; start to design a proper way to create >> kpatch and/or ifunc like things. >> >> >> svn: http://svnweb.freebsd.org/socsvn/soc2014/op/ >> git: https://github.com/opntr/opBSD (branches: >> op/gsoc2014/{master,smap,kpatch} ) >> wiki: >> https://wiki.freebsd.org/SummerOfCode2014/IntelSMAPandKernelPatching >> >> >> On 5/29/14, Oliver Pinter wrote: >>> Hi all! >>> >>> I'm working on Intel SMAP technology in first half of GSoC. >>> At first week I investigated in SMAP technology and relevant FreeBSD >>> codes, whats changed since my Bsc thesis. >>> >>> I implemented a vulnerable kernel module and PoC to test allowed and >>> not allowed memory access scenario. Created my wiki page, svn repo, >>> and git repo. >>> >>> svn: http://svnweb.freebsd.org/socsvn/soc2014/op/ >>> git: https://github.com/opntr/opBSD (branches: >>> op/gsoc2014/{master,smap,kpatch} ) >>> wiki: >>> https://wiki.freebsd.org/SummerOfCode2014/IntelSMAPandKernelPatching >>> test-cases: >>> http://svnweb.freebsd.org/socsvn/soc2014/op/tests/smap-tester/ >>> >>> Good days, >>> Oliver >>> >> >