Re: [PATCH v2 2/2] namespace: fix signal handling called from unduplicated code

2017-10-15 Thread Nadav Har'El
On Mon, Oct 16, 2017 at 4:30 AM, Justin Cinkelj wrote: > The previous patch (namespace: enable per namespace alarm/signal) > implemented per elf namespace signals for common usecase of alarms. > > But, as Nadav explained, it failed to allow application in a separate > ELF namespace to install its

[PATCH v2 2/2] namespace: fix signal handling called from unduplicated code

2017-10-15 Thread Justin Cinkelj
The previous patch (namespace: enable per namespace alarm/signal) implemented per elf namespace signals for common usecase of alarms. But, as Nadav explained, it failed to allow application in a separate ELF namespace to install its own handler for signals related to a page fault, division by zero

[PATCH v2 1/2] namespace: enable per namespace alarm/signal

2017-10-15 Thread Justin Cinkelj
From: Justin Cinkelj Before patch, netperf netserver.so and netperf.so could not be run in the same VM. The netserver reports "error starting alarm timer, ret 3 errno 28". The patch make alarm (and also signals) per namespace specific, in the wat as environ was made per namespace specific in e93

[PATCH v2 0/2] namespace: enable per namespace alarm/signal

2017-10-15 Thread Justin Cinkelj
The first patch is unmodified from what I aready sent to mail list a while ago. The second patch fixes problem Nadav noticed (and suggested a fix too) - that "it will not really work in places where unduplicated OSv code calls kill() or related functions". See https://groups.google.com/d/msg/osv-d