linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: Michael Halcrow <uml@halcrow.us>
Cc: Blaisorblade <blaisorblade_spam@yahoo.it>,
	user-mode-linux-devel@lists.sourceforge.net,
	user-mode-linux-user@lists.sourceforge.net
Subject: [uml-devel] Re: [uml-user] keyring syscalls
Date: Tue, 25 Jan 2005 23:37:57 +0100	[thread overview]
Message-ID: <200501252337.58219.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20050125215416.GA2912@halcrow.us>

On Tuesday 25 January 2005 22:54, Michael Halcrow wrote:
> 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.
Well, like 
> 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?
Yes, because when a program says "I want to call the write() syscall", all it 
contains to identify the "write" syscall between all the existing ones is the 
__NR_write value... so it is very important that they never change (on the 
same architecture). As long as UML must emulate i386, the identifiers must 
match.

> 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
Well, it should be fixed in the -mm tree (and probably in 2.6.11-rc2-bk2, I 
guess, though it's not tested)... browse the patches at 
http://user-mode-linux.sourceforge.net/patches.html.

It should be in next release...
-- 
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  parent reply	other threads:[~2005-01-25 22:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20041118160909.GA7630@halcrow.us>
2004-11-18 17:39 ` [uml-devel] Re: [uml-user] keyring syscalls Blaisorblade
2004-11-18 17:43   ` Michael Halcrow
2005-01-25 21:54   ` Michael Halcrow
2005-01-25 22:21     ` Henrik Nordstrom
2005-01-25 22:37     ` Blaisorblade [this message]
2005-01-25 22:46       ` Michael Halcrow
2005-01-25 23:02         ` Blaisorblade

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200501252337.58219.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=blaisorblade_spam@yahoo.it \
    --cc=uml@halcrow.us \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    --cc=user-mode-linux-user@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox