From: Thomas Gleixner <tglx@linutronix.de>
To: alexander.levin@verizon.com
Cc: "dvyukov@google.com" <dvyukov@google.com>,
"scientist@fb.com" <scientist@fb.com>,
"glider@google.com" <glider@google.com>,
"andreyknvl@google.com" <andreyknvl@google.com>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"mathieu.desnoyers@efficios.com" <mathieu.desnoyers@efficios.com>,
"daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Nicholas Mc Guire <der.herr@hofr.at>
Subject: Re: [RFC 0/3] ABI spec - verification
Date: Wed, 16 Nov 2016 18:46:23 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1611161845440.3697@nanos> (raw)
In-Reply-To: <1479317803-17220-1-git-send-email-alexander.levin@verizon.com>
On Wed, 16 Nov 2016, alexander.levin@verizon.com wrote:
Cc'ed Nicholas McGuire
> As discussed at plumbers, having a standard spec for the kernel's ABI has
> quite a few uses and enough people wanted it to get the ball rolling.
>
> We agreed that it's desirable to have something that can be used from code
> rather than just a spec on paper both for validation and allowing other users
> (like fuzzers, userspace libraries, and various userspace tools) to build
> on that.
>
> What we ended up deciding on at plumbers is:
>
> - I'll do a few kernel bits do demonstrate how we can validate the spec from
> the kernel.
> - Dmitry Vyukov will provide a way to translate syzkaller's syscall
> documentation into something that can be easily used in the kernel and
> userspace.
> - Various projects will attempt to integrate it to make sure that the
> framework works for them.
>
> Once those bits are done we can focus on getting the spec right, and we'll
> have a good way to validate our work both in userspace and in the kernel.
>
> This patchset is a basic draft of said kernel bits. I mostly want to make
> sure that Dmitry and myself are on the same page as to how integration will
> look like, but also to open it to criticism and suggestions (bikeshedding).
>
>
> Sasha Levin (3):
> abi_spec: basic definitions of constraints, args and syscalls
> abi_spec: hooks into syscall to allow pre and post checking
> abi_spec: example spec for open(), placeholder for rest of syscalls
>
> include/linux/syscalls.h | 7 +-
> include/uapi/linux/abi_spec.h | 58 ++++++
> kernel/Makefile | 2 +
> kernel/abi_spec.c | 456 ++++++++++++++++++++++++++++++++++++++++++
> 4 files changed, 522 insertions(+), 1 deletion(-)
> create mode 100644 include/uapi/linux/abi_spec.h
> create mode 100644 kernel/abi_spec.c
>
> --
> 2.7.4
>
next prev parent reply other threads:[~2016-11-16 17:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 17:37 [RFC 0/3] ABI spec - verification alexander.levin
2016-11-16 17:37 ` [RFC 1/3] abi_spec: basic definitions of constraints, args and syscalls alexander.levin
2016-11-21 14:48 ` Dmitry Vyukov
2016-11-23 14:59 ` alexander.levin
2016-12-12 10:29 ` Dmitry Vyukov
2016-12-12 10:45 ` Dmitry Vyukov
2016-12-14 19:46 ` Dmitry Vyukov
2016-12-14 19:48 ` Dmitry Vyukov
2017-01-04 4:52 ` alexander.levin
2016-12-27 17:23 ` alexander.levin
2016-12-28 7:32 ` Dmitry Vyukov
2016-11-21 15:41 ` Steven Rostedt
2016-11-23 15:03 ` alexander.levin
2016-11-23 15:31 ` Steven Rostedt
2016-11-23 15:33 ` Steven Rostedt
2016-11-16 17:37 ` [RFC 2/3] abi_spec: hooks into syscall to allow pre and post checking alexander.levin
2016-11-21 15:54 ` Steven Rostedt
2016-11-21 15:57 ` Dmitry Vyukov
2016-11-23 15:04 ` alexander.levin
2016-11-16 17:37 ` [RFC 3/3] abi_spec: example spec for open(), placeholder for rest of syscalls alexander.levin
2016-11-16 17:46 ` Thomas Gleixner [this message]
2016-11-21 14:25 ` [RFC 0/3] ABI spec - verification Dmitry Vyukov
2016-11-23 14:36 ` alexander.levin
2016-12-12 10:12 ` Dmitry Vyukov
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=alpine.DEB.2.20.1611161845440.3697@nanos \
--to=tglx@linutronix.de \
--cc=alexander.levin@verizon.com \
--cc=andreyknvl@google.com \
--cc=arnd@arndb.de \
--cc=daniel.vetter@ffwll.ch \
--cc=der.herr@hofr.at \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.org \
--cc=scientist@fb.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).