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 D9886C4332F for ; Mon, 12 Dec 2022 06:12:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231284AbiLLGMJ (ORCPT ); Mon, 12 Dec 2022 01:12:09 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34600 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231249AbiLLGMF (ORCPT ); Mon, 12 Dec 2022 01:12:05 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B8059CE20; Sun, 11 Dec 2022 22:12:04 -0800 (PST) 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 6C2B4B80B72; Mon, 12 Dec 2022 06:12:03 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 9F0E0C433EF; Mon, 12 Dec 2022 06:12:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1670825522; bh=HNQ+jgM7nK49r0QXRAxcWzevnlOGKXqz3QgiETxRhHc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=WM0p9cjRA54uIuhCbl3bNcjmtBqXqjXOC3mdqoTPMfXNGFGVY+p2LjDHubsqAvGNB dtfxv2dYaZK0bzf5t8f37JjGjSbnHHD6vnwMO8yrTT4w13cgZukg1Dg/Y2fB2b3TAR 5LSj2GE832dWK6oLrVDYpmOMou+L9g4VWVxl5Pls= Date: Mon, 12 Dec 2022 07:11:58 +0100 From: Greg Kroah-Hartman To: Andrew Donnellan Cc: Nayna , Nayna Jain , linuxppc-dev@lists.ozlabs.org, linux-fsdevel@vger.kernel.org, linux-efi@vger.kernel.org, linux-security-module , linux-kernel@vger.kernel.org, Michael Ellerman , npiggin@gmail.com, christophe.leroy@csgroup.eu, Dov Murik , George Wilson , Matthew Garrett , Dave Hansen , Benjamin Herrenschmidt , Paul Mackerras , Russell Currey , Stefan Berger , "Serge E. Hallyn" , "Ritesh Harjani (IBM)" Subject: Re: [PATCH 2/4] fs: define a firmware security filesystem named fwsecurityfs Message-ID: References: <20221106210744.603240-1-nayna@linux.ibm.com> <20221106210744.603240-3-nayna@linux.ibm.com> <8447a726-c45d-8ebb-2a74-a4d759631e64@linux.vnet.ibm.com> <20221119114234.nnfxsqx4zxiku2h6@riteshh-domain> <6f2a4a5f-ab5b-8c1b-47d5-d4e6dca5fc3a@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Dec 12, 2022 at 11:58:56AM +1100, Andrew Donnellan wrote: > On Wed, 2022-11-23 at 13:57 -0500, Nayna wrote: > > > > Given there are no other exploiters for fwsecurityfs and there should > > be > > no platform-specific fs, would modifying sysfs now to let userspace > > create files cleanly be the way forward? Or, if we should strongly > > consider securityfs, which would result in updating securityfs to > > allow > > userspace creation of files and then expose variables via a more > > platform-specific directory /sys/kernel/security/pks? We want to pick > > the best available option and would find some hints on direction > > helpful > > before we develop the next patch. > > Ping - it would be helpful for us to know your thoughts on this. sysfs is not for userspace creation of files, you all know this :) greg k-h