From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9627BC4332F for ; Tue, 4 Oct 2022 17:37:50 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229782AbiJDRhs (ORCPT ); Tue, 4 Oct 2022 13:37:48 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34866 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229744AbiJDRh2 (ORCPT ); Tue, 4 Oct 2022 13:37:28 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 179806AA22; Tue, 4 Oct 2022 10:36:05 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id B04DCB808CF; Tue, 4 Oct 2022 17:36:03 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4F49DC433D7; Tue, 4 Oct 2022 17:36:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1664904962; bh=kayiSIodoZR3mJ1pBQAy28WrEVULtTONXZgr/Z9D3es=; h=In-Reply-To:References:Date:From:To:Cc:Subject:From; b=PUIU4GUyuHhT3A9BskdSWSh7FAcmtx2E8PXZrViNak6i8qa++6QJi1Ci0qtDR1rdz L5sZVo/A9qAg6VjphwERSIrk/LYnSins7Dxk8hc7gg1ZcnXZRbgOn9cL4/ePXvpyM0 uG8R4Cr/dxrIicuBvK9dtRtRUBf7XcCuKFnjI1k+7zODgusivc2SVpQ3ACWWp3T5hQ QFZKroS87GdIyzrJqiaFs+9JNJm2FMspNauX29//NDF/s7yQjoFQIwtAUgcDwSex3+ yt0SMr10IVG39obPfi+kuvGaFXURicLZK6Qn9Nm2nKH+F+1mmKAH/g4pZziS2/LbRO 539Eil4yaf/0A== Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailauth.nyi.internal (Postfix) with ESMTP id 2BF7427C0054; Tue, 4 Oct 2022 13:36:00 -0400 (EDT) Received: from imap48 ([10.202.2.98]) by compute2.internal (MEProxy); Tue, 04 Oct 2022 13:36:00 -0400 X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrfeeiuddguddugecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefofgggkfgjfhffhffvvefutgesthdtredtreertdenucfhrhhomhepfdet nhguhicunfhuthhomhhirhhskhhifdcuoehluhhtoheskhgvrhhnvghlrdhorhhgqeenuc ggtffrrghtthgvrhhnpedvhfeuvddthfdufffhkeekffetgffhledtleegffetheeugeej ffduhefgteeihfenucevlhhushhtvghrufhiiigvpedunecurfgrrhgrmhepmhgrihhlfh hrohhmpegrnhguhidomhgvshhmthhprghuthhhphgvrhhsohhnrghlihhthidqudduiedu keehieefvddqvdeifeduieeitdekqdhluhhtoheppehkvghrnhgvlhdrohhrgheslhhinh hugidrlhhuthhordhush X-ME-Proxy: Feedback-ID: ieff94742:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 80CC631A0062; Tue, 4 Oct 2022 13:35:59 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.7.0-alpha0-1015-gaf7d526680-fm-20220929.001-gaf7d5266 Mime-Version: 1.0 Message-Id: <20d483b6-da24-4ddc-b6d4-c0c23b8e5ea2@app.fastmail.com> In-Reply-To: <20221003222133.20948-10-aliraza@bu.edu> References: <20221003222133.20948-1-aliraza@bu.edu> <20221003222133.20948-10-aliraza@bu.edu> Date: Tue, 04 Oct 2022 10:35:38 -0700 From: "Andy Lutomirski" To: "Ali Raza" , "Linux Kernel Mailing List" Cc: "Jonathan Corbet" , masahiroy@kernel.org, michal.lkml@markovi.net, "Nick Desaulniers" , "Thomas Gleixner" , "Ingo Molnar" , "Borislav Petkov" , "Dave Hansen" , "H. Peter Anvin" , "Eric W. Biederman" , "Kees Cook" , "Peter Zijlstra (Intel)" , "Al Viro" , "Arnd Bergmann" , juri.lelli@redhat.com, vincent.guittot@linaro.org, dietmar.eggemann@arm.com, "Steven Rostedt" , "Ben Segall" , mgorman@suse.de, bristot@redhat.com, vschneid@redhat.com, "Paolo Bonzini" , jpoimboe@kernel.org, linux-doc@vger.kernel.org, linux-kbuild@vger.kernel.org, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, linux-arch@vger.kernel.org, "the arch/x86 maintainers" , rjones@redhat.com, munsoner@bu.edu, tommyu@bu.edu, drepper@redhat.com, lwoodman@redhat.com, mboydmcse@gmail.com, okrieg@bu.edu, rmancuso@bu.edu Subject: Re: [RFC UKL 09/10] exec: Give userspace a method for starting UKL process Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 3, 2022, at 3:21 PM, Ali Raza wrote: > From: Eric B Munson > > From: Eric B Munson > > The UKL process might depend on setup that is to be done by user space > prior to its initialization. We need a way to let userspace signal that it > is ready for the UKL process to run. We will have setup a special name for > this process in the kernel config and if this name is passed to exec that > will start the UKL process. This way, if user space setup is required we > can be sure that the process doesn't run until explicitly started. This is just bizarre IMO. Why is there one single UKL process? How about having a way to start a UKL process and then, if desired, start *another* UKL process? (And obviously there would be a security mode in which only a UKL process that is actually part of the kernel image can run or that only a UKL process with a hash that's part of the kernel image can run.) --Andy