From: Michael Halcrow <uml@halcrow.us>
To: Blaisorblade <blaisorblade_spam@yahoo.it>
Cc: Michael Halcrow <uml@halcrow.us>,
user-mode-linux-devel@lists.sourceforge.net,
user-mode-linux-user@lists.sourceforge.net
Subject: [uml-devel] Re: [uml-user] keyring syscalls
Date: Thu, 18 Nov 2004 11:43:24 -0600 [thread overview]
Message-ID: <20041118174324.GA8993@halcrow.us> (raw)
In-Reply-To: <200411181839.26596.blaisorblade_spam@yahoo.it>
[-- Attachment #1: Type: text/plain, Size: 1314 bytes --]
On Thu, Nov 18, 2004 at 06:39:26PM +0100, Blaisorblade wrote:
> On Thursday 18 November 2004 17:09, Michael Halcrow wrote:
> > Howdy folks,
> >
> > I am attempting to use David Howells' new keyring in 2.6.10-rc2
> > UML and am getting a ``Function not implemented'' error with
> > keyctl. I was getting that in my host kernel until I mucked with
> > the __NR_* #define's in the userspace keyctl.c to align with the
> > values in the 2.6.10-rc2 entry.S. I imagine that new syscalls
> > require some magic in UML that I am unfamiliar with. I tried
> > adding some entries to arch/um/include/sysdep-i386/syscalls.h for
> > keyctl et. al., to no avail, but I'm kind of shooting the dark
> > here.
>
> 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.
Yes, those are the only three. Thanks!
Mike
.___________________________________________________________________.
Michael A. Halcrow
Security Software Engineer, IBM Linux Technology Center
GnuPG Fingerprint: 05B5 08A8 713A 64C1 D35D 2371 2D3C FDDA 3EB6 601D
"Never go to a doctor whose office plants have died."
- Erma Bombeck
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-11-18 17:43 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 [this message]
2005-01-25 21:54 ` Michael Halcrow
2005-01-25 22:21 ` Henrik Nordstrom
2005-01-25 22:37 ` Blaisorblade
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=20041118174324.GA8993@halcrow.us \
--to=uml@halcrow.us \
--cc=blaisorblade_spam@yahoo.it \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.