From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Weinberger Subject: Re: [RFC PATCH 00/11] an introduction of library operating system for Linux (LibOS) Date: Fri, 27 Mar 2015 06:52:04 +0100 Message-ID: <5514F004.7030509@nod.at> References: <1427202642-1716-1-git-send-email-tazaki@sfc.wide.ad.jp> <551164ED.5000907@nod.at> <55117565.6080002@nod.at> <55118277.5070909@nod.at> <55133BAF.30301@nod.at> <5514560A.7040707@nod.at> <87iodnqfp1.fsf@rustcorp.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: owner-linux-mm@kvack.org To: Geert Uytterhoeven , Rusty Russell Cc: Hajime Tazaki , Linux-Arch , Arnd Bergmann , Jonathan Corbet , Christoph Lameter , Pekka Enberg , David Rientjes , Joonsoo Kim , Andrew Morton , "linux-kernel@vger.kernel.org" , "linux-doc@vger.kernel.org" , "netdev@vger.kernel.org" , Linux MM , Jeff Dike , mathieu.lacage@gmail.com List-Id: linux-arch.vger.kernel.org Am 27.03.2015 um 04:49 schrieb Geert Uytterhoeven: > On Fri, Mar 27, 2015 at 4:31 AM, Rusty Russell wrote: >> Richard Weinberger writes: >>> This also infers that arch/lib will be broken most of the time as >>> every time the networking stack references a new symbol it >>> has to be duplicated into arch/lib. >>> >>> But this does not mean that your idea is bad, all I want to say that >>> I'm not sure whether arch/lib is the right approach. >>> Maybe Arnd has a better idea. >> >> Exactly why I look forward to getting this in-tree. Jeremy Kerr and I >> wrote nfsim back in 2005(!) which stubbed around the netfilter >> infrastructure; with failtest and valgrind it found some nasty bugs. It >> was too much hassle to maintain out-of-tree though :( >> >> I look forward to a flood of great bugfixes from this work :) > > IIRC, the ability to run UML under valgrind was also one of its key features? > And that's not limited to networking. Sadly this feature went never mainline. You needed a rather invading patch for both Linux and valgrind. But now with KASan we have a much more powerful feature to find issues. Thanks, //richard -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from a.ns.miles-group.at ([95.130.255.143]:65277 "EHLO radon.swed.at" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751329AbbC0FwO (ORCPT ); Fri, 27 Mar 2015 01:52:14 -0400 Message-ID: <5514F004.7030509@nod.at> Date: Fri, 27 Mar 2015 06:52:04 +0100 From: Richard Weinberger MIME-Version: 1.0 Subject: Re: [RFC PATCH 00/11] an introduction of library operating system for Linux (LibOS) References: <1427202642-1716-1-git-send-email-tazaki@sfc.wide.ad.jp> <551164ED.5000907@nod.at> <55117565.6080002@nod.at> <55118277.5070909@nod.at> <55133BAF.30301@nod.at> <5514560A.7040707@nod.at> <87iodnqfp1.fsf@rustcorp.com.au> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-arch-owner@vger.kernel.org List-ID: To: Geert Uytterhoeven , Rusty Russell Cc: Hajime Tazaki , Linux-Arch , Arnd Bergmann , Jonathan Corbet , Christoph Lameter , Pekka Enberg , David Rientjes , Joonsoo Kim , Andrew Morton , "linux-kernel@vger.kernel.org" , "linux-doc@vger.kernel.org" , "netdev@vger.kernel.org" , Linux MM , Jeff Dike , mathieu.lacage@gmail.com Message-ID: <20150327055204.6ngbwJykJQ3QHyExwe7qqOLR5RvVt_c9FsbZWTEsXTQ@z> Am 27.03.2015 um 04:49 schrieb Geert Uytterhoeven: > On Fri, Mar 27, 2015 at 4:31 AM, Rusty Russell wrote: >> Richard Weinberger writes: >>> This also infers that arch/lib will be broken most of the time as >>> every time the networking stack references a new symbol it >>> has to be duplicated into arch/lib. >>> >>> But this does not mean that your idea is bad, all I want to say that >>> I'm not sure whether arch/lib is the right approach. >>> Maybe Arnd has a better idea. >> >> Exactly why I look forward to getting this in-tree. Jeremy Kerr and I >> wrote nfsim back in 2005(!) which stubbed around the netfilter >> infrastructure; with failtest and valgrind it found some nasty bugs. It >> was too much hassle to maintain out-of-tree though :( >> >> I look forward to a flood of great bugfixes from this work :) > > IIRC, the ability to run UML under valgrind was also one of its key features? > And that's not limited to networking. Sadly this feature went never mainline. You needed a rather invading patch for both Linux and valgrind. But now with KASan we have a much more powerful feature to find issues. Thanks, //richard