From owner-soc-status@FreeBSD.ORG Sat Jun 28 13:01:59 2014 Return-Path: Delivered-To: soc-status@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1E21ACF5; Sat, 28 Jun 2014 13:01:59 +0000 (UTC) Received: from mail-oa0-x234.google.com (mail-oa0-x234.google.com [IPv6:2607:f8b0:4003:c02::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 D499625BE; Sat, 28 Jun 2014 13:01:58 +0000 (UTC) Received: by mail-oa0-f52.google.com with SMTP id j17so6900832oag.11 for ; Sat, 28 Jun 2014 06:01:58 -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=ESbLSGngBYjcw2JoEGSKeHaPwZ7JjSNvIAqpRmed7Zk=; b=uz6iSl8Sp7rjPcFRH48d4G/GtT+lpfRIS+L7qnxKAkkLZRzZ02fpOeH1ysNNXSSo91 pQkYDRXgRyzvGniS3yUjBF5KjMPFs709turNkMtssTESBWhJmk+bO3qKfOSbkPEGFr1G aDij8icIMOFiU34KsefSyq4pavCM2CKgF451mqMwziLaDdEzuecgLtoGjI+aFZO4qQjf Y+y0KR+nTUkpXIotYkCCLtLP8TCgaBWLOvi3C98qmhJbbSlNMQl8D+HSaUMf51hk9don mGPIFqpGY5/UuB4cG7VQM28h7bUa4/CzFtiDX/q9eryG2kaoSEEHeW7b2Nn47NdbQ83/ 10iA== MIME-Version: 1.0 X-Received: by 10.60.175.34 with SMTP id bx2mr29893404oec.49.1403960518055; Sat, 28 Jun 2014 06:01:58 -0700 (PDT) Received: by 10.182.216.197 with HTTP; Sat, 28 Jun 2014 06:01:58 -0700 (PDT) Date: Sat, 28 Jun 2014 15:01:58 +0200 Message-ID: Subject: [intel smap, kpatch] weekly report #5 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: Sat, 28 Jun 2014 13:01:59 -0000 This week I started the second phase of GSoC. In this design a run-time kernel and module patching framework. This means that the kernel able to dynamically change their code run-time. In second phase's first week I investigated where must I implement the functionality and which kernel APIs should I use. You can found the current status in my wiki page. On 6/21/14, Oliver Pinter wrote: > 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 >>>> >>> >> >