Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3581907imu; Sun, 11 Nov 2018 18:37:12 -0800 (PST) X-Google-Smtp-Source: AJdET5f6YhG1d3MVcfUnURMfo15f79Ruk5f898uLL89prtQlw2rbkvQF0FD0iNNjrfclU+ZJFr3r X-Received: by 2002:a17:902:1105:: with SMTP id d5-v6mr18867422pla.28.1541990232072; Sun, 11 Nov 2018 18:37:12 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541990232; cv=none; d=google.com; s=arc-20160816; b=0D4NsZcjXE23kG6x84LWhbNsAHRs96JRA/BuF5pjYu+khNarL08t39D4aHg81UDAd0 fp2TDqVXnr0qyraW10N9O5JonL109Ab7fZ6s+YFPPDzhp/vhdc1LYfcZLf84i0kwBz26 BaxQhQp1L87cP2Ri+Zhb8dhAQ7NBTSerETJ6OVj9YAF3bxJ3dmy7VoCaYxOpniLzeib2 ActH9sBW8MbKSx3ADykMoXzjbU0x+CkkYajuLA56WJn6OTR9OLA/MYiUoTrDoe6KTVn5 O6c7Pbut8bLC/Ewed8u9FkFb4AgC8/uBNCduYRgSZh3JR/AyNUFf65nFCzZsWz0EAdVB UK3w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=dUt9/EnY9YQkf6ysdv7hO3draGFJuDu85zj5g3AGhks=; b=b8hnzmCYUZ+2bkF9mC/z8LqDFteoXRMAo8j5TUjOQa0OSKzrg6oy0/iPGtXMVBkiHb zBrIq5+MQSjh8i3/HN63ffYx4gu0Z42cTnak/ZVQsMBbVmSitLqUGpd2SgWOwWLxqFnB QNskz6im6ksALVbTLn2j6BlT+r8a1DWxLdKBHnFTWdEaYjHtuJNieOKxyeMPXT50Lm/a 51Xi+QpSkkB870eHUbnbQ4O0kU/6fhe8BcH/3/VO3L+TeZlc3zu5dxH5hP/J1wDRsi3q HnAe6jw6MyFIDn6mQgwnrjRKEysSVzLou4SZ3pDq4xtCCug22tM8hTsZepjyxQxx7i4I FofQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=t3mlrN7v; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o6-v6si16305298plh.197.2018.11.11.18.36.56; Sun, 11 Nov 2018 18:37:12 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=t3mlrN7v; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730055AbeKLM1a (ORCPT + 99 others); Mon, 12 Nov 2018 07:27:30 -0500 Received: from mail.kernel.org ([198.145.29.99]:46034 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727282AbeKLM1a (ORCPT ); Mon, 12 Nov 2018 07:27:30 -0500 Received: from localhost (unknown [206.108.79.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id A91DB20871; Mon, 12 Nov 2018 02:36:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1541990190; bh=wVU/hd9Wkr+YpJDYbmIzHf60E5NiLEHdR6posnaJIRA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=t3mlrN7vhOoCEa//UJiojqzShE1gQgsHNt/vTuTIE81MuKPGEZdZfcJCt668MfOiS 8E9g71QKFzrabt6Rv2nLimXPuekhXAiYNNaJvn3N2ALF1c3VZYm58gisxHLf3EXDR9 JLuDjVAowBJp1BqqlpQx0GgBhTifbuIfC4CxLmRs= Date: Sun, 11 Nov 2018 18:36:30 -0800 From: Greg KH To: Carlos O'Donell Cc: Daniel Colascione , linux-kernel , Joel Fernandes , Linux API Subject: Re: Official Linux system wrapper library? Message-ID: <20181112023630.GA20359@kroah.com> References: <20181110192027.GA29892@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Nov 11, 2018 at 09:24:40PM -0500, Carlos O'Donell wrote: > On 11/10/18 2:20 PM, Greg KH wrote: > > Also, what about the basic work of making sure our uapi header files can > > actually be used untouched by a libc? That isn't the case these days as > > the bionic maintainers like to keep reminding me. That might be a good > > thing to do _before_ trying to add new things like syscall wrappers. > I agree completely. There are many steps in the checklist to writing > a new syscall, heck we should probably have a checklist! We should have a checklist. That's a great idea. Now to find someone to write it... :) I'll try to make it to the plumbers talk, but I think there's a competing one I am supposed to be at at the same time. greg k-h