From: Thorsten Kukuk <kukuk@suse.de>
To: libc-hacker@sources.redhat.com
Subject: key* syscalls mismatch
Date: Fri, 23 Jun 2006 11:01:00 -0000 [thread overview]
Message-ID: <20060623110138.GA14533@suse.de> (raw)
Hi,
ChangeLog.15 contains the following entry:
2004-10-20 Ulrich Drepper <drepper@redhat.com>
* sysdeps/unix/sysv/linux/syscalls.list: Add entries for setaltroot,
key_add, key_request, and keyctl syscalls.
* sysdeps/unix/sysv/linux/Versions: Export them.
sysdeps/unix/sysv/linux/syscalls.list contains keyctl, add_key and
request_key, but sysdeps/unix/sysv/linux/Versions contains none of
them.
So what is the status of this syscalls? Was the export revoked, or
never commited?
Thorsten
--
Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de
SUSE LINUX Products GmbH Maxfeldstr. 5 D-90409 Nuernberg
--------------------------------------------------------------------
Key fingerprint = 8C6B FD92 EE0F 42ED F91A 6A73 6D1A 7F05 2E59 24BB
next reply other threads:[~2006-06-23 11:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 11:01 Thorsten Kukuk [this message]
2006-06-23 11:07 ` Andreas Schwab
2006-08-01 7:16 ` Ulrich Drepper
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=20060623110138.GA14533@suse.de \
--to=kukuk@suse.de \
--cc=libc-hacker@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).