From: Tavis Ormandy <taviso@google.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Cyril Hrubis <chrubis@suse.cz>,
linux-api@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Michael Kerrisk-manpages <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@redhat.com, syzkaller <syzkaller@googlegroups.com>,
Kostya Serebryany <kcc@google.com>,
Mike Frysinger <vapier@google.com>,
Dave Jones <davej@codemonkey.org.uk>
Subject: Re: Formal description of system call interface
Date: Mon, 21 Nov 2016 07:34:49 -0800 [thread overview]
Message-ID: <CAJ_zFkL3D5dzn+h1ydNg9rF11wrsyCv6uhp5=VNH82d4E5ewUA@mail.gmail.com> (raw)
In-Reply-To: <CACT4Y+aUzdX8NqMu+Y3s53vEmoBw7KysB3g2PEjZ6MyJimki1Q@mail.gmail.com>
On Mon, Nov 21, 2016 at 7:14 AM, Dmitry Vyukov <dvyukov@google.com> wrote:
>
>
> Re more complex side effects. I always feared that a description suitable
> for automatic verification (i.e. zero false positives, otherwise it is useless)
> may be too difficult to achieve.
>
> Cyril, Tavis, can you come up with some set of predicates that can be
> checked automatically yet still useful?
> We can start small, e.g. "must not alter virtual address space".
Yes, I've been working on creating something like this, I have a
simple working prototype. I cant promise it has zero false positives
right now, but I think that is achievable.
Let me dig it up (I had put it on the back burner).
Tavis.
next prev parent reply other threads:[~2016-11-21 15:35 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 [this message]
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
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='CAJ_zFkL3D5dzn+h1ydNg9rF11wrsyCv6uhp5=VNH82d4E5ewUA@mail.gmail.com' \
--to=taviso@google.com \
--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=rostedt@goodmis.org \
--cc=scientist@fb.com \
--cc=syzkaller@googlegroups.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).