[uml-devel] Re: [uml-user] keyring syscalls

[Michael Halcrow <uml@halcrow.us>]

[-- Attachment #1: Type: text/plain, Size: 1756 bytes --]

On Thu, Nov 18, 2004 at 06:39:26PM +0100, Blaisorblade wrote:
> On Thursday 18 November 2004 17:09, Michael Halcrow wrote:
> Ok, please list the new syscalls - I see at least add_key() and
> request_key() too - are these three the only ones? I'll build the
> patch ASAP when getting your answer.

I spent some more time today trying to implement these silly
request_key, add_key, and keyctl syscalls in the 2.6.10 kernel, but I
haven't had any luck.  It would be a *tremendous* help for me in my
filesystem development if I could just get these syscalls working in
UML; it is much more tedious having to use kgdb in my debugging.  I
tried adding entries on to the end of the
include/sysdep-i386/syscalls.h and the kernel/sys_call_table.c files.
I also exported the symbols in os-Linux/user_syms.c.  I am trying to
work from the documentation here:

http://jdike.stearns.org/uml/arch-port.html

I am not entirely clear on the function that ``[ 222 ] =
sys_ni_syscall,'' at the end of the table in syscalls.h is supposed to
serve.  Syscalls in UML contstitutes new territory for me.

I would assume that the __NR_* assignments in the UML environment are
identical to those of the host system.  That means that request_key,
for example, maps to identifier 288 on the i386 architecture, right?
The keyctl.c utility defines these syscall identifiers, so I need to
make sure that I get the numbers right for the syscall table lookup.

Thanks,
Mike
.___________________________________________________________________.
                         Michael A. Halcrow                          
       Security Software Engineer, IBM Linux Technology Center       
GnuPG Fingerprint: 05B5 08A8 713A 64C1 D35D  2371 2D3C FDDA 3EB6 601D

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]