Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751488AbcKGAet (ORCPT ); Sun, 6 Nov 2016 19:34:49 -0500 Received: from port70.net ([81.7.13.123]:38832 "EHLO port70.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751130AbcKGAek (ORCPT ); Sun, 6 Nov 2016 19:34:40 -0500 X-Greylist: delayed 303 seconds by postgrey-1.27 at vger.kernel.org; Sun, 06 Nov 2016 19:34:40 EST Date: Mon, 7 Nov 2016 01:28:40 +0100 From: Szabolcs Nagy To: Dmitry Vyukov Cc: linux-api@vger.kernel.org, LKML , mtk.manpages@gmail.com, Thomas Gleixner , Sasha Levin , Mathieu Desnoyers , scientist@fb.com, Steven Rostedt , Arnd Bergmann , carlos@redhat.com, syzkaller , Kostya Serebryany , Mike Frysinger , Dave Jones , Tavis Ormandy Subject: Re: Formal description of system call interface Message-ID: <20161107002839.GN5749@port70.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1179 Lines: 29 * Dmitry Vyukov [2016-11-06 14:39:28 -0800]: > This is notes from the discussion we had at Linux Plumbers this week > regarding providing a formal description of system calls (user API). yes a database of the syscall abis would be useful ..depending on the level of detail it has. (right now there is not even spec about what registers the syscall entry point may clobber on the various abis which would be useful to know when making syscalls) > Action points: > - polish DSL for description (must be extensible) > - write a parser for DSL > - provide definition for mm syscalls (mm is reasonably simple > and self-contained) > - see if we can do validation of mm arguments for all abi variants? e.g. mmap offset range is abi dependent. > For the reference, current syzkaller descriptions are in txt files here: > https://github.com/google/syzkaller/tree/master/sys ... > Taking the opportunity, if you see that something is missing/wrong > in the descriptions of the subsystem you care about, or if it is not > described at all, fixes are welcome. abi variants are missing (abi variation makes a lot of syscall interface related work painful).