From: Steven Rostedt <rostedt@goodmis.org>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: Dmitry Vyukov <dvyukov@google.com>,
linux-api@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
mtk.manpages@gmail.com, Thomas Gleixner <tglx@linutronix.de>,
Sasha Levin <levinsasha928@gmail.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
scientist@fb.com, Arnd Bergmann <arnd@arndb.de>,
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: Mon, 21 Nov 2016 10:37:52 -0500 [thread overview]
Message-ID: <20161121103752.70ad1418@gandalf.local.home> (raw)
In-Reply-To: <20161107103819.GA11374@rei.lan>
On Mon, 7 Nov 2016 11:38:20 +0100
Cyril Hrubis <chrubis@suse.cz> wrote:
> I'm not sure if something like this is really doable or in the scope of
> this project, but it may be worth a try.
>
Looking ahead into the future, I was also thinking that if this becomes
robust, we could also start an integration specification, that could
describe how different system calls interact with each other. Like
open() to read(), write() and close().
But this is just an idea that popped in my head while reading this
thread. We want to start small first, but still could keep this in the
back of our minds for future enhancements.
-- Steve
next prev parent reply other threads:[~2016-11-21 15:37 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 [this message]
2016-11-21 15:48 ` Dmitry Vyukov
2016-11-21 16:58 ` Cyril Hrubis
2016-11-11 17:10 ` Andy Lutomirski
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=20161121103752.70ad1418@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=arnd@arndb.de \
--cc=carlos@redhat.com \
--cc=chrubis@suse.cz \
--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=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).