linux-kernel - Re: [PATCH] of: document /sys/firmware/fdt

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-kTMUuYRaTdikzRZ_ZKKkQEDCiCrR=-Mzok67xmMN5zQ@mail.gmail.com>
Date:   Wed, 14 Jun 2017 12:16:53 +0200
From:   Ard Biesheuvel <ard.biesheuvel@...aro.org>
To:     Mark Rutland <mark.rutland@....com>
Cc:     Frank Rowand <frowand.list@...il.com>,
        Rob Herring <robh+dt@...nel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] of: document /sys/firmware/fdt

On 14 June 2017 at 11:55, Mark Rutland <mark.rutland@....com> wrote:
> [Adding Ard, as he added /sys/firmware/fdt]
>

Thanks

> On Tue, Jun 13, 2017 at 09:20:07PM -0700, frowand.list@...il.com wrote:
>> From: Frank Rowand <frank.rowand@...y.com>
>>
>> Add ABI documentation for /sys/firmware/fdt
>>
>> Update contact for /sys/firmware/devicetree/* to include mail list
>>
>> Signed-off-by: Frank Rowand <frank.rowand@...y.com>
>
> FWIW:
>
> Acked-by: Mark Rutland <mark.rutland@....com>
>

Reviewed-by: Ard Biesheuvel <ard.biesheuvel@...aro.org>

>> ---
>>  Documentation/ABI/testing/sysfs-firmware-ofw | 27 ++++++++++++++++++++++++++-
>>  1 file changed, 26 insertions(+), 1 deletion(-)
>>
>> diff --git a/Documentation/ABI/testing/sysfs-firmware-ofw b/Documentation/ABI/testing/sysfs-firmware-ofw
>> index f562b188e71d..8e700db6c295 100644
>> --- a/Documentation/ABI/testing/sysfs-firmware-ofw
>> +++ b/Documentation/ABI/testing/sysfs-firmware-ofw
>> @@ -1,6 +1,6 @@
>>  What:                /sys/firmware/devicetree/*
>>  Date:                November 2013
>> -Contact:     Grant Likely <grant.likely@...aro.org>
>> +Contact:     Grant Likely <grant.likely@...aro.org>, devicetree@...r.kernel.org
>>  Description:
>>               When using OpenFirmware or a Flattened Device Tree to enumerate
>>               hardware, the device tree structure will be exposed in this
>> @@ -26,3 +26,28 @@ Description:
>>               name plus address). Properties are represented as files
>>               in the directory. The contents of each file is the exact
>>               binary data from the device tree.
>> +
>> +What:                /sys/firmware/fdt
>> +Date:                February 2015
>> +KernelVersion:       3.19
>> +Contact:     Frank Rowand <frank.rowand@...y.com>, devicetree@...r.kernel.org
>> +Description:
>> +             Exports the FDT blob that was passed to the kernel by
>> +             the bootloader. This allows userland applications such
>> +             as kexec to access the raw binary. This blob is also
>> +             useful when debugging since it contains any changes
>> +             made to the blob by the bootloader.
>> +
>> +             The fact that this node does not reside under
>> +             /sys/firmware/device-tree is deliberate: FDT is also used
>> +             on arm64 UEFI/ACPI systems to communicate just the UEFI
>> +             and ACPI entry points, but the FDT is never unflattened
>> +             and used to configure the system.
>> +
>> +             A CRC32 checksum is calculated over the entire FDT
>> +             blob, and verified at late_initcall time. The sysfs
>> +             entry is instantiated only if the checksum is valid,
>> +             i.e., if the FDT blob has not been modified in the mean
>> +             time. Otherwise, a warning is printed.
>> +Users:               kexec, debugging
>> +
>> --
>> Frank Rowand <frank.rowand@...y.com>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe devicetree" in
>> the body of a message to majordomo@...r.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.