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 X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id AB2ADC282CE for ; Tue, 4 Jun 2019 20:07:34 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 2D37C2067C for ; Tue, 4 Jun 2019 20:07:34 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=google.com header.i=@google.com header.b="pv/6OPT1" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 2D37C2067C Authentication-Results: mail.kernel.org; dmarc=fail (p=reject dis=none) header.from=google.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Received: from lists.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 45JNJ403mXzDqVR for ; Wed, 5 Jun 2019 06:07:32 +1000 (AEST) Authentication-Results: lists.ozlabs.org; spf=pass (mailfrom) smtp.mailfrom=google.com (client-ip=2607:f8b0:4864:20::141; helo=mail-it1-x141.google.com; envelope-from=matthewgarrett@google.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=pass (p=reject dis=none) header.from=google.com Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=google.com header.i=@google.com header.b="pv/6OPT1"; dkim-atps=neutral Received: from mail-it1-x141.google.com (mail-it1-x141.google.com [IPv6:2607:f8b0:4864:20::141]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 45JNGQ46XSzDq5t for ; Wed, 5 Jun 2019 06:06:00 +1000 (AEST) Received: by mail-it1-x141.google.com with SMTP id n189so59985itd.0 for ; Tue, 04 Jun 2019 13:06:00 -0700 (PDT) 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=ZREhuJlsDtH89ZVDYphzf41RLCVZZkM936cBZurEuKE=; b=pv/6OPT1BwcW5kLEBR+t89bzJ6UremuUyrRRzifMONzXagldwUIj4ryQti4Jce45X3 YEqlt80vgw/1s9GumZrTUbCOUG1NmsmW6pUOoHe9r1iHLbpAPBsMiCQti4XuzcoymGTf yRK4Yp32kJT1dNc4oAtYkpiMcmE6Y3X7yQXCgUTLsgrsSA7TI8MEz14fbjA3EbNcjAlY 2idbOTzsQd664g8fX2JJ8XhDoeqMwDy4YUdEwBa5PaQXDZn8oJjRkRjkseIlZr4mFJto QT6ZqnKS7YsQaium2oEVGTjkIDxej2XHbJmZ/VKarQFFIw/oW3HevHdtuWUbxY+c7WM1 NCVA== 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=ZREhuJlsDtH89ZVDYphzf41RLCVZZkM936cBZurEuKE=; b=nQruzOl0HhARh+WIHy4YOvEfAFmqL16vbKC4eTELeuGB22eDMT+LikbX6YJPqCaKV6 rvVqQ9kk418jReZKCn4lxztE61LIoseyi44LfrYpZYWUpBEJIQbwkXul03fizZ7x8pj6 NQhFUzMVHpS9SvinU+XoNU4YJlC0T6fIZ9zKVe1eTy1zXGfU8FQ1PeFrIho1bvo/RqST 5OR67WNt5FxyGMJe0LPP4wbQ1B9i2S2e4yDOJP//ZHtXzKqJnEv+ysKN5Bt5hgYEFatC OhaFpz5xBHPt4iOCt/7oeBYKQx1eVluCiKTo5xOXsNeli91mhnYpKocbWb//8hmIx9iQ AOVQ== X-Gm-Message-State: APjAAAUMiiDUOu+ljakf+gG6wfiW1sTHUvHlmYEJhpLiLB/TJr3MmKZu OExgOJ2mt87iFJcj49FYrMcQxBK6Y64WowlboY5iMQ== X-Google-Smtp-Source: APXvYqwsa9hUdLg9OFkrqEiChjF1ClMm07RxLnCex43+ESQGujO4p+QXESe0Hiljy+pNbzZoo6W0gnVr8MJ1YwSahpo= X-Received: by 2002:a24:bd4:: with SMTP id 203mr22280225itd.119.1559678756641; Tue, 04 Jun 2019 13:05:56 -0700 (PDT) MIME-Version: 1.0 References: <20190520062553.14947-1-dja@axtens.net> <316a0865-7e14-b36a-7e49-5113f3dfc35f@linux.vnet.ibm.com> <87zhmzxkzz.fsf@dja-thinkpad.axtens.net> <20190603072916.GA7545@kroah.com> <87tvd6xlx9.fsf@dja-thinkpad.axtens.net> In-Reply-To: From: Matthew Garrett Date: Tue, 4 Jun 2019 13:05:45 -0700 Message-ID: Subject: Re: [WIP RFC PATCH 0/6] Generic Firmware Variable Filesystem To: Nayna Content-Type: text/plain; charset="UTF-8" X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Greg KH , Nayna Jain , Claudio Carvalho , Mimi Zohar , George Wilson , Elaine Palmer , linux-fsdevel@vger.kernel.org, linuxppc-dev , Daniel Axtens Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On Tue, Jun 4, 2019 at 1:01 PM Nayna wrote: > It seems efivars were first implemented in sysfs and then later > separated out as efivarfs. > Refer - Documentation/filesystems/efivarfs.txt. > > So, the reason wasn't that sysfs should not be used for exposing > firmware variables, > but for the size limitations which seems to come from UEFI Specification. > > Is this limitation valid for the new requirement of secure variables ? I don't think the size restriction is an issue now, but there's a lot of complex semantics around variable deletion and immutability that need to be represented somehow.