Received: by 2002:ac0:aed5:0:0:0:0:0 with SMTP id t21csp4548514imb; Wed, 6 Mar 2019 16:37:51 -0800 (PST) X-Google-Smtp-Source: APXvYqyyabxr8w1Kp3FNwj7VxQkx4iny7cexVVfStZlYPM2eS1dW36zyvzMaUNqGP8GRVl834Eqi X-Received: by 2002:a62:1981:: with SMTP id 123mr9976184pfz.69.1551919071120; Wed, 06 Mar 2019 16:37:51 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551919071; cv=none; d=google.com; s=arc-20160816; b=aBKlr0vwy+GmTgu4S8zqmbQ8aU5nxrcPo/Cnvp1d00nOHqb9AQR99hphg3yffKM1k9 z88Cb0WwIIZ0tGmcVGz0kAY5zPdFyXOt8fzNFdtNuIodNvMOpgwQwoNt2ZQsgw+ph5Vp L1w3rNTKO/uEISJyigE+5oayqKiTGPFpJw1xcWSmbtEeSfskLHkQ1D9HgxZSsxEwx+mI EAK2O4BoNe34cFjd5b/14s93Fn+dTX4kiXwURvjZOWjVmwCHdf7X/2ADCOED+jOK1Bbp 3/Q1nakvStzABHdxdQ1DQ8CHcO7PmyLu0E1UOe5f76vzFFMjhAjiWbDaEBpJ9qTII5dg kruQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=OIIL3avLv0JJGnmF3/9V3Uwq0jp+vCztotzjLKOlseY=; b=GvTb40SkwQ79B6eBwDVt7U49t972oGs9GuOYKbZyV6ttCG+CaB0tluUPpgq8mexPMN WXlh9HW9KnT3qZGhA27dbhxPtIB3VizOek8MBpiel96UeN5srSaHqZD51IMxLkKE028U CtHoXJsX/+d5KAsE2NnQUqm4xq+RXkg8kFF9knEv1bwP9urH6fMTS67jXFPVyFRjmExG JS/ollOJNZSdlx5C+saWKun0IAQTaz2+SJA14KplnVo7HFLU08AACtK5fc+o6yxzD+vq ZYS5zeJRgshBUvg5Llo/Pc65Bav1P4uN+wmKYumo/0dgHCxOrx7I4lfUIEniAWN/TzSk kxvQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b="nNN/MavS"; 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; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q88si2817168pfa.222.2019.03.06.16.37.35; Wed, 06 Mar 2019 16:37:51 -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=@google.com header.s=20161025 header.b="nNN/MavS"; 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; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726294AbfCGAhA (ORCPT + 99 others); Wed, 6 Mar 2019 19:37:00 -0500 Received: from mail-vs1-f67.google.com ([209.85.217.67]:37446 "EHLO mail-vs1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726121AbfCGAhA (ORCPT ); Wed, 6 Mar 2019 19:37:00 -0500 Received: by mail-vs1-f67.google.com with SMTP id y19so3433673vsc.4 for ; Wed, 06 Mar 2019 16:36:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=OIIL3avLv0JJGnmF3/9V3Uwq0jp+vCztotzjLKOlseY=; b=nNN/MavSBstEWMjJtBj+urYjYPVzNMcLp+GzbwXr/R9FOLMakEXdIIgT5E3foa5s3A WZ+2jYdp++JvXcbryxL6G+3k3QMa8x3t1G8LrsmlbneHggxzqCuiWCGrJ+Lyilu0WtAN UPrQ0zcnn6JUqXJuHwB7QFn4kTpByxx1jrhxU3O+UDzN03jz0bgdMjI/Wt63h5vwAXmp 7IzlzTGKDPq7HYOB6jWx/KSAPdcc+gXWhtu/vNLD0qqJ1fLvDmwYEiF/nz5nNCgU5dlA Qe9Pl1Y3FhPBVsMR9eQ3vYLduITH5EAqKMx41C5FniJRsDXfLF1GzZ+YrLk2AM7Mx1j/ 5SrQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=OIIL3avLv0JJGnmF3/9V3Uwq0jp+vCztotzjLKOlseY=; b=afujQaWCXhSBnKv9QP5gpn2k3+7lSpoE/9F/aNTGrwlMjfJDzBn/m0FMf7riGYDa0M cwgNJPGl3oAoLVNcK+xpHKSiXVnHvjTkV9fEEZrNCTA7jx3mh6N2ndxtIiHwe63uEYek b2kHv7Sk6cx9dGqG2/9OdlimUkEKZX+4t3ffJ3EePTLqFUB74APADAt3hsRva+PK3xns 9lLycE38phsW6OIQMtcdBjhKAd7gwTT9oYqqWBC5Y5ba9U6mKOLTPsme5w1OMemzH31S vUK98rcmbKPsn8ehCQJjm3ojdEaUUJZTFkHJKIRFihV1RpyXgU22ZeKT8pZXP+Bk931T wvZw== X-Gm-Message-State: APjAAAVRG3gHgZZ4d7XdhcNJstMMoWKW02poej/kMeELH6o1pjvjJbVp FTvJr/7tQ8a5NKxHicHgVtmahBttr5kwhs+jjIvyFQ== X-Received: by 2002:a67:8448:: with SMTP id g69mr5396057vsd.77.1551919018224; Wed, 06 Mar 2019 16:36:58 -0800 (PST) MIME-Version: 1.0 References: <20190118225543.86996-1-joel@joelfernandes.org> <20190119082532.GA9004@kroah.com> <20190119162754.GC231277@google.com> <20190119232503.GA149403@google.com> <78AACAF1-8EBF-4DF3-BE94-5B14E78BA791@zytor.com> <20190120155838.GA23827@google.com> <20190306230944.GB7915@amd> <2205470b-1efc-b357-8b2e-67392cf8bb2e@zytor.com> In-Reply-To: <2205470b-1efc-b357-8b2e-67392cf8bb2e@zytor.com> From: Daniel Colascione Date: Wed, 6 Mar 2019 16:36:46 -0800 Message-ID: Subject: Re: [RFC] Provide in-kernel headers for making it easy to extend the kernel To: "H. Peter Anvin" Cc: Pavel Machek , Joel Fernandes , Greg KH , linux-kernel , Andrew Morton , ast@kernel.org, atish patra , Borislav Petkov , Ingo Molnar , Jan Kara , Jonathan Corbet , Karim Yaghmour , Kees Cook , kernel-team@android.com, "open list:DOCUMENTATION" , Manoj Rao , Masahiro Yamada , Paul McKenney , "Peter Zijlstra (Intel)" , Randy Dunlap , rostedt@goodmis.org, Thomas Gleixner , "maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" , yhs@fb.com Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 6, 2019 at 4:33 PM H. Peter Anvin wrote: > > On 3/6/19 3:37 PM, Daniel Colascione wrote: > > > > I just don't get the opposition to Joel's work. The rest of the thread > > already goes into detail about the problems with pure-filesystem > > solutions, and you and others are just totally ignoring those > > well-thought-out rationales for the module approach and doing > > inflooping on "lol just use a tarball". That's not productive. > > > > You might think they are well thought out, but at least from what I can > tell they seem completely spurious. That sentence is a general-purpose objection to literally anything. Anything so general is useless. If you want to claim that the rationale behind the work is inadequate, you have to explain why the use cases that it enables are either illegitimate or amenable to other solutions, not just call them spurious.