From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on archive.lwn.net X-Spam-Level: X-Spam-Status: No, score=-6.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, RCVD_IN_DNSWL_HI autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by archive.lwn.net (Postfix) with ESMTP id 468E17D04D for ; Thu, 7 Mar 2019 23:12:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726268AbfCGXML (ORCPT ); Thu, 7 Mar 2019 18:12:11 -0500 Received: from mail-qk1-f194.google.com ([209.85.222.194]:45461 "EHLO mail-qk1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726267AbfCGXMK (ORCPT ); Thu, 7 Mar 2019 18:12:10 -0500 Received: by mail-qk1-f194.google.com with SMTP id v139so10121669qkb.12 for ; Thu, 07 Mar 2019 15:12:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelfernandes.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=M3bALdIkkTXR5Cl9wrkQz8PrR1SUO0MiBjS3cu5nIVU=; b=eGmMPxZPHYxgib0WVlf0KAJZUvJqIszcB29lMR3bfoCY4qGVJz61Qh7LzWV8NUYgDQ g/+xaKYjl90EiSgfmwzNZEuiGh+Xpdp9q8dZf1owvGS91v+ac4/YDN4Hk2ya0UUAjXeW 3O6O9EcZVmW5I1WQFqEBiDVE3BNOMAp0UHwUo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=M3bALdIkkTXR5Cl9wrkQz8PrR1SUO0MiBjS3cu5nIVU=; b=sYxwfiMeuxXPIEEV0JGyNM3r4lYmv9Vc3Y1UR5vJA6GisthqoTkUy/lFNKd9Q0Mvx3 No3JTyYRbP7apGMlzavaVdZszxOilp7FPueGLu8QbWkZiqE/QtoYE0TlaiMaRsy7Gw4g Ru3jMjdpnV5Z3464HqWApGNUvqvMFleMs47ToyNVQKWWqV5ZYORAAtuhej7O5ywpiuEc 6TlViT9d12xzXMVRiSP/gVGqoiuNvgMp8vVPsstyYPJ24MI3g1omsOmmKXu5tDFfnkmL 99/9NkKtkCYFq4cuP6bj1/+BCdF7kQgblygd481WVQwMyIxFRiMZrFFAb9Junxi2jDA0 MU6w== X-Gm-Message-State: APjAAAVFTIC4nuxK6bYhHeAzHhawZ2UCgcA2/a787btQxyplwCLvNciH 6ZmLyECkUokXqeWZ06CCJWCvmA== X-Google-Smtp-Source: APXvYqxWVObFtxc8k9qGwgpv8swA9U5M/tTW2j1JQwAybhEyWe7eCOqUCuBW7F0561tKaDSiK3xe6g== X-Received: by 2002:a37:6d41:: with SMTP id i62mr241170qkc.209.1552000329639; Thu, 07 Mar 2019 15:12:09 -0800 (PST) Received: from localhost ([2620:0:1004:1100:cca9:fccc:8667:9bdc]) by smtp.gmail.com with ESMTPSA id b66sm3600500qkj.57.2019.03.07.15.12.07 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 07 Mar 2019 15:12:08 -0800 (PST) Date: Thu, 7 Mar 2019 18:12:07 -0500 From: Joel Fernandes To: "Enrico Weigelt, metux IT consult" Cc: Greg KH , Daniel Colascione , "H. Peter Anvin" , Pavel Machek , 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 Subject: Re: [RFC] Provide in-kernel headers for making it easy to extend the kernel Message-ID: <20190307231207.GA51897@google.com> References: <20190120155838.GA23827@google.com> <20190306230944.GB7915@amd> <754146f0-8b57-8644-81c1-528b5ca7dba1@zytor.com> <0c46ab5f-8bd6-6916-fc4a-b6f00d456011@metux.net> <5ebec282-57b0-6ebe-0876-ce0dd7b0c11c@metux.net> <20190307205505.GB30028@kroah.com> <5e558126-9038-1ca5-4519-7b5864ca9fa1@metux.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5e558126-9038-1ca5-4519-7b5864ca9fa1@metux.net> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-doc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.org Enrico, On Thu, Mar 07, 2019 at 11:11:22PM +0100, Enrico Weigelt, metux IT consult wrote: > On 07.03.19 21:55, Greg KH wrote: > > > Ick, no, no more squashfs please, let's just kill that mess once and for > > all :) > > okay, then: s/squashfs/whatever_fs_image_or_archive_you_like/; > > > Again, putting this in a simple compressed tar image allows anyone to do > > whatever they need to with this. If they want a full filesystem, > > uncompress it and use it there. If they just want it in-memory where > > they can uncompress it and then discard it, that works too. > > And let me stress the point: doesn't need any kernel changes at all, > when it's just a file in the same place where the .ko's live. Yes, but you're missing the point that some people would also opt to build it into the kernel during their development/debugging (Config=y). For such folks, they don't want to update the FS with anything during debug runs either. Your "whole same place where the .ko lives" doesn't address Daniel's usecase. You may say "initrd", but this is a much cleaner solution to that IMO. There is no initrd needed and the path to the header files will be at a standard location that is already pre-decided by the kernel. As Greg said, you are welcome to keep it disabled for yourself if you don't want it. This doesn't affect anyone else who doesn't use it.