From owner-freebsd-current@FreeBSD.ORG  Mon Jun  9 18:34:59 2008
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 8B9641065673;
	Mon,  9 Jun 2008 18:34:59 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 18AC88FC24;
	Mon,  9 Jun 2008 18:34:57 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Message-ID: <484D77D2.9050102@FreeBSD.org>
Date: Mon, 09 Jun 2008 20:34:58 +0200
From: Kris Kennaway <kris@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Julian Elischer <julian@elischer.org>
References: <484CC690.9020303@elischer.org> <484CFE6E.7040305@FreeBSD.org>
	<484D6B38.3020207@elischer.org>
In-Reply-To: <484D6B38.3020207@elischer.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Marko Zec <zec@FreeBSD.org>, FreeBSD Current <current@freebsd.org>,
	freebsd-virtualization@freebsd.org
Subject: Re: kinda headsup..
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jun 2008 18:34:59 -0000

Julian Elischer wrote:
> Kris Kennaway wrote:
>> Julian Elischer wrote:
>>> At the BSDCAn devsummit we discussed how to proceed with committing 
>>> Vimage to -current.
>>>
>>> the Milestones included something like:
>>>
>>> June 8 (today) Headsup....
>>>
>>> June 15        commit changes that add macros for vnet
>>>                (network module) and vinet(inet virtualisation)
>>>                with macros defined in such a way to make 0 actual
>>>                differences. provable by md5 etc.
>>>                Documentat
>>>                  s/hostname/g//V_hostname/
>>>                  #define V_hostname hostname
>>>                2 weeks settle time, next step prepared, tested
>>>                and reviewed.
>> ...
>>
>>> diffs can be found at:
>>>  http://www.freebsd.org/~julian/vimage.diff and it are usually
>>> fairly up to date.
>>
>> Did Marko fix the panic I saw back in May?  I wasn't even able to boot 
>> a vimage kernel yet, let alone begin testing it :)
> 
> is this the ipv6 panic?
> I must admit I have not heard..
> he was looking at it back thne and has committed stuff since then..
> 
> I use it with IPV4 quite successfully quite often.
> 
> note that the first commits are pretty much quaranteed to not have that 
> problem.. as they are effective NOPs
> 
> 
> I'll get back to you  on it..

Yes, the panic occurs when one runs a vimage kernel on a CVS world. 
It's presumably a case of incomplete validation of the input from userland.

I'd still like someone to validate the initial commits and establish a 
framework for ongoing testing, because we've seen cases recently where 
things as simple as structure alignment changes can have >30% 
performance impact, so if it's not entirely a NOP then there is still 
potential for trouble.

Kris