lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKv+Gu-KPypju6roQaVKP0DHE3aZijVVqLGwNyhiRSNqn1r6-w@mail.gmail.com>
Date:   Tue, 1 Oct 2019 10:54:40 +0200
From:   Ard Biesheuvel <ard.biesheuvel@...aro.org>
To:     Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:     Narendra K <Narendra.K@...l.com>,
        linux-efi <linux-efi@...r.kernel.org>,
        Ingo Molnar <mingo@...nel.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        James Morse <james.morse@....com>,
        Mario Limonciello <mario.limonciello@...l.com>,
        Xiaofei Tan <tanxiaofei@...wei.com>
Subject: Re: [PATCH 4/5] efi: Export Runtime Configuration Interface table to sysfs

On Tue, 1 Oct 2019 at 10:51, Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
>
> Hi Ard, Narendra,
>
> On Mon, Aug 12, 2019 at 5:07 PM Ard Biesheuvel
> <ard.biesheuvel@...aro.org> wrote:
> > From: Narendra K <Narendra.K@...l.com>
> >
> > System firmware advertises the address of the 'Runtime
> > Configuration Interface table version 2 (RCI2)' via
> > an EFI Configuration Table entry. This code retrieves the RCI2
> > table from the address and exports it to sysfs as a binary
> > attribute 'rci2' under /sys/firmware/efi/tables directory.
> > The approach adopted is similar to the attribute 'DMI' under
> > /sys/firmware/dmi/tables.
> >
> > RCI2 table contains BIOS HII in XML format and is used to populate
> > BIOS setup page in Dell EMC OpenManage Server Administrator tool.
> > The BIOS setup page contains BIOS tokens which can be configured.
> >
> > Signed-off-by: Narendra K <Narendra.K@...l.com>
> > Reviewed-by: Mario Limonciello <mario.limonciello@...l.com>
> > Signed-off-by: Ard Biesheuvel <ard.biesheuvel@...aro.org>
>
> Thanks, this is now commit 1c5fecb61255aa12 ("efi: Export Runtime
> Configuration Interface table to sysfs").
>
> > --- a/drivers/firmware/efi/Kconfig
> > +++ b/drivers/firmware/efi/Kconfig
> > @@ -180,6 +180,19 @@ config RESET_ATTACK_MITIGATION
> >           have been evicted, since otherwise it will trigger even on clean
> >           reboots.
> >
> > +config EFI_RCI2_TABLE
> > +       bool "EFI Runtime Configuration Interface Table Version 2 Support"
> > +       help
> > +         Displays the content of the Runtime Configuration Interface
> > +         Table version 2 on Dell EMC PowerEdge systems as a binary
> > +         attribute 'rci2' under /sys/firmware/efi/tables directory.
> > +
> > +         RCI2 table contains BIOS HII in XML format and is used to populate
> > +         BIOS setup page in Dell EMC OpenManage Server Administrator tool.
> > +         The BIOS setup page contains BIOS tokens which can be configured.
> > +
> > +         Say Y here for Dell EMC PowerEdge systems.
>
> A quick Google search tells me these are Intel Xeon.
> Are arm/arm64/ia64 variants available, too?
> If not, this should be protected by "depends on x86" ("|| COMPILE_TEST"?).
>

Hello Geert,

The code in question is entirely architecture agnostic, and defaults
to 'n', so I am not convinced this is needed. (It came up in the
review as well)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ