From: Igmar Palsenberg <igmar@palsenberg.com>
To: musl@lists.openwall.com
Subject: Re: capset() capget() syscalls
Date: Wed, 05 Sep 2012 11:28:54 +0200 [thread overview]
Message-ID: <50471B56.8040804@palsenberg.com> (raw)
In-Reply-To: <20120905061905.GQ27715@brightrain.aerifal.cx>
>> Hi,
>>
>> Attached patch adds types to the existing syscalls, and defines the
>> types in the header. All CAP_* defines are also added.
> I'm curious what applications expect this header and definitions.
> glibc does not have such a header. My impression is that it might have
> existed at some point but that it was removed a long time ago, and
> that any use of capabilities without libcap (which presumably contains
> its own copy of the definitions for interfacing with the kernel) was
> long ago deprecated.
>
> Can you clear these issues up?
My own. Those definitions are part of the kernel syscall. While glibc
does support structure definitions for most syscalls,
capabilities seem to be an exception. (they are in linux/capabilities.h
to be exact). Oh, and I really dislike the interfaces libcap provides.
I pull those definitions in myself now, because pulling in kernel header
files is considered a bad practice (c) Linus Torvalds
Since these won't add a byte of code, it might be a good idea.
I'm open for suggestions however.
Igmar
next prev parent reply other threads:[~2012-09-05 9:28 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 11:51 igmar
2012-09-05 6:19 ` Rich Felker
2012-09-05 9:28 ` Igmar Palsenberg [this message]
2012-09-05 14:24 ` Rich Felker
2012-09-05 17:01 ` Justin Cormack
2012-09-06 3:04 ` Rich Felker
2012-09-06 3:10 ` John Spencer
2012-09-06 3:20 ` Rich Felker
2012-09-06 3:28 ` Kurt H Maier
2012-09-06 3:41 ` Rich Felker
2012-09-06 4:41 ` Kurt H Maier
2012-09-06 8:22 ` Justin Cormack
2012-09-06 9:28 ` Szabolcs Nagy
2012-09-06 14:23 ` Rich Felker
2012-09-07 4:56 ` Rich Felker
2012-09-08 16:02 ` Justin Cormack
2012-09-08 22:14 ` Rich Felker
2012-09-09 20:04 ` Justin Cormack
2012-09-09 20:14 ` Rich Felker
2012-09-09 21:13 ` James Cloos
2012-09-09 21:55 ` Rich Felker
2012-09-09 22:12 ` Justin Cormack
2012-09-09 22:29 ` Rich Felker
2012-09-09 22:37 ` Justin Cormack
2012-09-10 15:07 ` James Cloos
2012-09-08 21:25 ` Justin Cormack
2012-09-08 22:15 ` Rich Felker
2012-09-08 23:56 ` Rich Felker
2012-09-09 0:21 ` Rich Felker
2012-09-09 8:21 ` Justin Cormack
2012-09-09 19:40 ` Justin Cormack
2012-09-09 21:02 ` Rich Felker
2012-09-09 21:07 ` Justin Cormack
2012-09-09 21:23 ` Justin Cormack
2012-09-09 21:31 ` Justin Cormack
2012-09-09 21:58 ` Rich Felker
2012-09-09 22:14 ` Justin Cormack
2012-09-15 1:54 ` Rich Felker
2012-09-16 14:13 ` Justin Cormack
2012-09-17 2:27 ` Rich Felker
2012-09-06 11:47 ` Igmar Palsenberg
2012-09-06 11:36 ` Igmar Palsenberg
2012-09-06 14:11 ` Rich Felker
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=50471B56.8040804@palsenberg.com \
--to=igmar@palsenberg.com \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).