Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2282944imu; Sat, 10 Nov 2018 11:21:07 -0800 (PST) X-Google-Smtp-Source: AJdET5cn0XGinv0yFb0KMMFGT1wkQ8bctWBDx10tpBBMcNFa30QmLzWvqId9V4IwjCxMUGNZJdEg X-Received: by 2002:a62:5881:: with SMTP id m123-v6mr14117420pfb.160.1541877667773; Sat, 10 Nov 2018 11:21:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541877667; cv=none; d=google.com; s=arc-20160816; b=mydxayecWdnmFYjW2w4/GrVpnnnd7yv0n8SFTMqXqEiIsQZl+V2Jm26BsbKLQATEzK yaP4u2beEaMZQqD5BX/+8viP0uWVvCQCbEsFgw6dijMSHXnrhdai0/r5v6fo1hYGhLJi v+ZmMa4gd7953i6uplLdLsRO8bFdfbP7jQbdubURebIJDCLSAd/iOP++cNECNcIGSeI2 WCOP3H5/EuE99/b70iuRmWgqPFNW5N2fwBG51AcKeFAHG2bygumSEfyuB6VdyfEfWkqR 4nIpwQGyOKq/aRzUxh3er1xmMyBte9AKx+DKzAqpws/QWSYMSFdn0My3F8WKSjdEuMZQ HUSQ== 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=T8+5HrAy0QLlYpukkqo9GW1f5/KGMSQvytUhgbd6tto=; b=ISTezQdCOi9ab4w9Wnedybw7QrKj14XOLdzHx3MY9EQ3t1aLVp/mp9euo/57XVeKsL TclJPl+b8K0sCB+IQwnsIef02OiYtXohkHyGXPbJ/3yGDq72U0fYyw3TQ5YuseBnjRPd g8I80Juwk3fzWgvxHih+dSPZtY86RVtwATeZfPgDPhlWd1cl8fZpXLMsVRGm11t0qDkz xY43SzYss4u740Mzsuj7jiGtvhb0nwu/RxAW1Ey0o5ByRVafLQOTLTF1ULFFtkvbB7gI 8LrkYythDggK8X/Na8ASV8XtG/YFkoSBVPfNsBD15cLL7B/PVP3ke9Fvnnteimz+OokW BIyA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=MReYaiGr; 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 193si11105268pgc.220.2018.11.10.11.20.50; Sat, 10 Nov 2018 11:21:07 -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=MReYaiGr; 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 S1725948AbeKKFGa (ORCPT + 99 others); Sun, 11 Nov 2018 00:06:30 -0500 Received: from mail.kernel.org ([198.145.29.99]:45444 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725778AbeKKFG3 (ORCPT ); Sun, 11 Nov 2018 00:06:29 -0500 Received: from localhost (71-6-98-120.static-ip.telepacific.net [71.6.98.120]) (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 85BAA20684; Sat, 10 Nov 2018 19:20:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1541877627; bh=yHEjlh1S+M2kqb2D80PkFcukg2D68LO5ActflyYTMyU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=MReYaiGrXOHTGbou/MMsw+5CloOYJxQzgKsy+tLEiso3CF2sn614u6eJQKXA6yE0I 8wN9PHkKlq6HOLWgqKiri3p28PtIZ8PIoifooTbu+JmWrWhA5d0SzEkbCyzZsujeLM e66E2JTfGk4PC8nMih4vjkyF5NKB0sYwn5V+o/pU= Date: Sat, 10 Nov 2018 11:20:27 -0800 From: Greg KH To: Daniel Colascione Cc: linux-kernel , Joel Fernandes , Linux API Subject: Re: Official Linux system wrapper library? Message-ID: <20181110192027.GA29892@kroah.com> References: 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 Sat, Nov 10, 2018 at 10:52:06AM -0800, Daniel Colascione wrote: > Now that glibc is basically not adding any new system call wrappers, Why are they not doing that anymore? And there's no reason you have to use glibc, there are many other libcs out there that hopefully are adding the new syscalls :) > how about publishing an "official" system call glue library as part of > the kernel distribution, along with the uapi headers? I don't think > it's reasonable to expect people to keep using syscall(__NR_XXX) for > all new functionality, especially as the system grows increasingly > sophisticated capabilities (like the new mount API, and hopefully the > new process API) outside the strictures of the POSIX process. Patches are always welcome to be reviewed. But watch out that they don't conflict with the libc headers. I know we had a "klibc" proposed a long time ago but that died off for various reasons before it could get merged. 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. thanks, greg k-h