From: "H. Peter Anvin" <hpa@zytor.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
libseccomp-discuss@lists.sourceforge.net
Subject: Re: Making a universal list of syscalls?
Date: Wed, 05 Mar 2014 16:16:35 -0800 [thread overview]
Message-ID: <5317BE63.1000600@zytor.com> (raw)
In-Reply-To: <CALCETrWM2N59+4ao2T1xgX_W0-cHXzYLZUO_fkSRt4O9NrNTow@mail.gmail.com>
On 03/05/2014 04:13 PM, Andy Lutomirski wrote:
>
> I think that SYSCALLS.def won't work as is -- SYSCALLS.def
> references unistd, which ought to be autogenerated from the syscalls
> list. But a somewhat less magical variant should work.
>
Well, that is because unistd.h is one of the very few things the kernel
actually *does* export (containing system call numbers, and *usually* is
enough to detect presence/absence of a certain system call, which is
actually all you need in the vast majority of cases.)
-hpa
next prev parent reply other threads:[~2014-03-06 0:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 20:40 Making a universal list of syscalls? Andy Lutomirski
2014-02-27 20:53 ` Eric Paris
2014-02-27 20:53 ` [libseccomp-discuss] " Eric Paris
2014-02-27 21:16 ` Paul Moore
2014-03-04 19:27 ` H. Peter Anvin
2014-03-06 0:13 ` Andy Lutomirski
2014-03-06 0:13 ` Andy Lutomirski
2014-03-06 0:16 ` H. Peter Anvin [this message]
2014-03-05 11:08 ` David Howells
2014-03-06 23:37 ` H. Peter Anvin
2014-03-06 23:40 ` Andy Lutomirski
2014-03-06 23:44 ` H. Peter Anvin
2014-03-17 19:36 ` Michael Kerrisk
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=5317BE63.1000600@zytor.com \
--to=hpa@zytor.com \
--cc=libseccomp-discuss@lists.sourceforge.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.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.