From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Rostedt Subject: Re: Formal description of system call interface Date: Mon, 21 Nov 2016 10:37:52 -0500 Message-ID: <20161121103752.70ad1418@gandalf.local.home> References: <20161107103819.GA11374@rei.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20161107103819.GA11374@rei.lan> Sender: linux-kernel-owner@vger.kernel.org To: Cyril Hrubis Cc: Dmitry Vyukov , linux-api@vger.kernel.org, LKML , mtk.manpages@gmail.com, Thomas Gleixner , Sasha Levin , Mathieu Desnoyers , scientist@fb.com, Arnd Bergmann , carlos@redhat.com, syzkaller , Kostya Serebryany , Mike Frysinger , Dave Jones , Tavis Ormandy List-Id: linux-api@vger.kernel.org On Mon, 7 Nov 2016 11:38:20 +0100 Cyril Hrubis 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