From mboxrd@z Thu Jan 1 00:00:00 1970 From: josh-iaAMLnmF4UmaiuxdJuQwMA@public.gmane.org Subject: Re: [PATCHv2 1/1] Documentation: describe how to add a system call Date: Fri, 31 Jul 2015 15:08:28 -0700 Message-ID: <20150731220828.GA30890@cloud> References: <1438242731-27756-2-git-send-email-drysdale@google.com> <20150730083831.GA22182@gmail.com> <20150730190434.GD16452@x> <20150731010234.GA7265@x> <20150731205941.GA30362@cloud> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Andy Lutomirski Cc: Kees Cook , David Drysdale , Ingo Molnar , Linux API , Michael Kerrisk , Andrew Morton , Arnd Bergmann , Shuah Khan , Jonathan Corbet , Eric B Munson , Randy Dunlap , Andrea Arcangeli , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Oleg Nesterov , Linus Torvalds , Greg Kroah-Hartman , Al Viro , Rusty Russell , Peter Zijlstra , Vivek Goyal , Alexei Starovoitov David List-Id: linux-api@vger.kernel.org On Fri, Jul 31, 2015 at 02:19:29PM -0700, Andy Lutomirski wrote: > On Fri, Jul 31, 2015 at 1:59 PM, wrote: > > Agreed. I think the proposal above would be a net improvement, but > > ideally you'd want something that's annotated and generates automatic > > marshalling code. > > > > I assume this is idle musing. If, however, we were to actually do > this, I'd suggest we seriously consider speaking the Cap'n Proto > serialization format. It's quite nice, it encodes and decodes *very* > quickly and, unlike TLV schemes, you don't have to read it in order, > making the read-side code less awkward. That seems like *massive* overkill for a kernel<->userspace syscall interface. I was more thinking about having a few standardized marshal types, and incrementally adding more when more patterns show up. For a first pass, just automatically running copy_from_user and copy_param_struct on appropriate sets of __user parameters identified as such in a structured text file seems quite sufficient. (Plus automatically generating syscalls.h from that.)