From: "H. Peter Anvin" <hpa@zytor.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: David Howells <dhowells@redhat.com>,
"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: Thu, 06 Mar 2014 15:44:58 -0800 [thread overview]
Message-ID: <5319087A.8000109@zytor.com> (raw)
In-Reply-To: <CALCETrXt7bqQxymOC0ke+4Uaqv7nGOHqw3YhVHf4YKvJ4b8WpQ@mail.gmail.com>
On 03/06/2014 03:40 PM, Andy Lutomirski wrote:
> On Thu, Mar 6, 2014 at 3:37 PM, H. Peter Anvin <hpa@zytor.com> wrote:
>> On 03/05/2014 03:08 AM, David Howells wrote:
>>> It would be really nice if we could do this in such a manner that we could
>>> build strace from it.
>>
>> strace, seccomp, klibc, ... we all need more or less the same stuff.
>
> strace also needs to know what the pointed-to type is for pointer
> arguments, whether pointers are input, output, or both, and what kind
> of flags / constants fit in which integer slot.
>
Yes. That kind of information also needs to be annotated.
It might take a while to get there, but it should be part of the design.
-hpa
next prev parent reply other threads:[~2014-03-06 23:45 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
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 [this message]
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=5319087A.8000109@zytor.com \
--to=hpa@zytor.com \
--cc=dhowells@redhat.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.