From: Andy Lutomirski <luto@amacapital.net>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Linux API <linux-api@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Sasha Levin <levinsasha928@gmail.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
scientist@fb.com, Steven Rostedt <rostedt@goodmis.org>,
Arnd Bergmann <arnd@arndb.de>,
"Carlos O'Donell" <carlos@redhat.com>,
syzkaller <syzkaller@googlegroups.com>,
Kostya Serebryany <kcc@google.com>,
Mike Frysinger <vapier@google.com>,
Dave Jones <davej@codemonkey.org.uk>,
Tavis Ormandy <taviso@google.com>
Subject: Re: Formal description of system call interface
Date: Fri, 11 Nov 2016 09:10:45 -0800 [thread overview]
Message-ID: <CALCETrVS_t+sHNSL=eDP_yRU0w78rKUT=JAXOxHd-J5=SwwQBQ@mail.gmail.com> (raw)
In-Reply-To: <CACT4Y+YYgs43nJnyg3B9cHWOue62iMW3ZgXQKiKG12A1NVMgtg@mail.gmail.com>
On Sun, Nov 6, 2016 at 2:39 PM, Dmitry Vyukov <dvyukov@google.com> wrote:
> Hello,
>
> This is notes from the discussion we had at Linux Plumbers this week
> regarding providing a formal description of system calls (user API).
>
> The idea come up in the context of syzkaller, syscall fuzzer, which
> has descriptions for 1000+ syscalls mostly concentrating on types of
> arguments and return values. However, problems are that a small group
> of people can't write descriptions for all syscalls; can't keep them
> up-to-date and doesn't have necessary domain expertise to do correct
> descriptions in some cases.
>
> We identified a surprisingly large number of potential users for such
> descriptions:
Let me add one more: consolidation of all the incompatible arch
syscall tables. A sufficiently descriptive format should be parseable
at build time to generate the syscall tables.
next prev parent reply other threads:[~2016-11-11 17:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-06 22:39 Formal description of system call interface Dmitry Vyukov
2016-11-07 0:28 ` Szabolcs Nagy
2016-11-21 15:03 ` Dmitry Vyukov
2016-11-22 13:07 ` Szabolcs Nagy
2016-11-07 10:38 ` Cyril Hrubis
2016-11-21 15:14 ` Dmitry Vyukov
2016-11-21 15:34 ` Tavis Ormandy
2016-11-21 16:10 ` Cyril Hrubis
2016-11-21 15:37 ` Steven Rostedt
2016-11-21 15:48 ` Dmitry Vyukov
2016-11-21 16:58 ` Cyril Hrubis
2016-11-11 17:10 ` Andy Lutomirski [this message]
2016-11-21 15:17 ` Dmitry Vyukov
2017-04-21 15:14 ` Carlos O'Donell
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='CALCETrVS_t+sHNSL=eDP_yRU0w78rKUT=JAXOxHd-J5=SwwQBQ@mail.gmail.com' \
--to=luto@amacapital.net \
--cc=arnd@arndb.de \
--cc=carlos@redhat.com \
--cc=davej@codemonkey.org.uk \
--cc=dvyukov@google.com \
--cc=kcc@google.com \
--cc=levinsasha928@gmail.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mtk.manpages@gmail.com \
--cc=rostedt@goodmis.org \
--cc=scientist@fb.com \
--cc=syzkaller@googlegroups.com \
--cc=taviso@google.com \
--cc=tglx@linutronix.de \
--cc=vapier@google.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 NNTP newsgroup(s).