[haiku-commits] Re: haiku: hrev45507 - src/add-ons/kernel/network/notifications
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: haiku-commits@xxxxxxxxxxxxx
- Date: Tue, 23 Apr 2013 13:09:03 +0200 (CEST)
On April 23, 2013 at 10:55 AM Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:
> On 04/22/2013 12:08 PM, "Axel Dörfler" wrote:
> [...]
> > Alternatively, one could enhance the generic syscall mechanism to be able to
> > load the module providing the API on the fly, so that that one could then
> > take
> > care of registering the service in case the network stack is not loaded.
> > This
> > would allow to completely decouple the needs of userland applications, and
> > the
> > network stack.
> Indeed, this sounds like a nice solution. Instead of a function pointer
> the syscall could be invoked via a new module operation instead. This
> would safe the trouble of having to deal with a function pointer that my
> change when the module is reloaded.
Sounds nice. We might want to use dedicated modules (ie. those having a module
name ending with for example "/syscall/v1"), though, so a module operation might
not be necessary -- this would effectively prevent users to load random modules.
Would this be desirable for security reasons? OTOH just loading a module should
not really do much harm.
Bye,
Axel.
Other related posts:
