Re: REG changes

From: Amon Ott <ao@rsbac.org>
Subject: Re: REG changes
Date: Tue, 20 Feb 2001 09:12:00 +0100

Next Article (by Author): Re: Understanding ACI Amon Ott
Previous Article (by Author): Re: Understanding ACI Amon Ott
Top of Thread: REG changes Amon Ott
Articles sorted by: [Date] [Author] [Subject]

On Die, 20 Feb 2001 Jörgen Sigvardsson wrote:
> On Monday 19 February 2001 18:10, you wrote:
> > Hello again!
> >
> > Having to present the REG interface soon, I made a redesign of the REG
> > internals and added syscall registration. 
> Syscall registration as in dynamically registering a new system call? (I.e., 
> runtime syscall table tweaking?)

It is an idea I originally put into my GACI proposal: One single syscall
sys_rsbac_reg with a handle based dispatcher:

asmlinkage sys_rsbac_reg(rsbac_reg_handle_t handle, void * arg)
  {
     <lookup handle in registered syscall table>
     <if found item, return item->syscall(arg)>
     <else return error>
  }

The registration itself works similar to the usual module registration, but
each module can register as many syscalls as it wants to. And the handles are
separate from the module handles, because they must be known to user space for
syscall placing.

The registeres syscall function can get its parameter struct (with known size)
from user space via the arg pointer and act accordingly.

How the handles get known is a module issue, e.g. fixed values or a field in a
proc entry.

> > All registrations are now kept in
> > dynamic list structures of unlimited length. The changes will soon be
> > documented in an extra document 'REG - writing your own decision module'.
> I'm looking forward to that document.

I hope it will make more people write their own modules and get them published
on the rsbac.org server.

Amon.
-
To unsubscribe from the rsbac list, send a mail to
majordomo@rsbac.org with
unsubscribe rsbac
as single line in the body.

Go to Compuniverse LWGate Home Page.