Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934755AbcKKRLL (ORCPT ); Fri, 11 Nov 2016 12:11:11 -0500 Received: from mail-ua0-f182.google.com ([209.85.217.182]:34031 "EHLO mail-ua0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933992AbcKKRLG (ORCPT ); Fri, 11 Nov 2016 12:11:06 -0500 MIME-Version: 1.0 In-Reply-To: References: From: Andy Lutomirski Date: Fri, 11 Nov 2016 09:10:45 -0800 Message-ID: Subject: Re: Formal description of system call interface To: Dmitry Vyukov Cc: Linux API , LKML , Michael Kerrisk , Thomas Gleixner , Sasha Levin , Mathieu Desnoyers , scientist@fb.com, Steven Rostedt , Arnd Bergmann , "Carlos O'Donell" , syzkaller , Kostya Serebryany , Mike Frysinger , Dave Jones , Tavis Ormandy Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 886 Lines: 19 On Sun, Nov 6, 2016 at 2:39 PM, Dmitry Vyukov wrote: > Hello, > > This is notes from the discussion we had at Linux Plumbers this week > regarding providing a formal description of system calls (user API). > > The idea come up in the context of syzkaller, syscall fuzzer, which > has descriptions for 1000+ syscalls mostly concentrating on types of > arguments and return values. However, problems are that a small group > of people can't write descriptions for all syscalls; can't keep them > up-to-date and doesn't have necessary domain expertise to do correct > descriptions in some cases. > > We identified a surprisingly large number of potential users for such > descriptions: Let me add one more: consolidation of all the incompatible arch syscall tables. A sufficiently descriptive format should be parseable at build time to generate the syscall tables.