[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5514F004.7030509@nod.at>
Date: Fri, 27 Mar 2015 06:52:04 +0100
From: Richard Weinberger <richard@....at>
To: Geert Uytterhoeven <geert@...ux-m68k.org>,
Rusty Russell <rusty@...tcorp.com.au>
CC: Hajime Tazaki <tazaki@...e.ad.jp>,
Linux-Arch <linux-arch@...r.kernel.org>,
Arnd Bergmann <arnd@...db.de>,
Jonathan Corbet <corbet@....net>,
Christoph Lameter <cl@...ux.com>,
Pekka Enberg <penberg@...nel.org>,
David Rientjes <rientjes@...gle.com>,
Joonsoo Kim <iamjoonsoo.kim@....com>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Linux MM <linux-mm@...ck.org>, Jeff Dike <jdike@...toit.com>,
mathieu.lacage@...il.com
Subject: Re: [RFC PATCH 00/11] an introduction of library operating system
for Linux (LibOS)
Am 27.03.2015 um 04:49 schrieb Geert Uytterhoeven:
> On Fri, Mar 27, 2015 at 4:31 AM, Rusty Russell <rusty@...tcorp.com.au> wrote:
>> Richard Weinberger <richard@....at> 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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists