linux-kernel - Re: [PATCH] memory-hotplug.rst: fix wrong /sys/device/ path

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: <8df8d6dd-d0fc-908e-77c7-a67167e1c74f@redhat.com>
Date:   Fri, 22 Sep 2023 09:33:59 +0200
From:   David Hildenbrand <david@...hat.com>
To:     Wang Jinchao <wangjinchao@...sion.com>,
        Oscar Salvador <osalvador@...e.de>,
        Jonathan Corbet <corbet@....net>, linux-mm@...ck.org,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Cc:     xulei <stone.xulei@...sion.com>
Subject: Re: [PATCH] memory-hotplug.rst: fix wrong /sys/device/ path

On 22.09.23 04:00, Wang Jinchao wrote:
> Actually, it should be /sys/devices/
> 
> Signed-off-by: Wang Jinchao <wangjinchao@...sion.com>
> ---
>   Documentation/admin-guide/mm/memory-hotplug.rst | 8 ++++----
>   1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/Documentation/admin-guide/mm/memory-hotplug.rst b/Documentation/admin-guide/mm/memory-hotplug.rst
> index cfe034cf1e87..01595965734a 100644
> --- a/Documentation/admin-guide/mm/memory-hotplug.rst
> +++ b/Documentation/admin-guide/mm/memory-hotplug.rst
> @@ -250,15 +250,15 @@ Observing the State of Memory Blocks
>   The state (online/offline/going-offline) of a memory block can be observed
>   either via::
>   
> -	% cat /sys/device/system/memory/memoryXXX/state
> +	% cat /sys/devices/system/memory/memoryXXX/state
>   
>   Or alternatively (1/0) via::
>   
> -	% cat /sys/device/system/memory/memoryXXX/online
> +	% cat /sys/devices/system/memory/memoryXXX/online
>   
>   For an online memory block, the managing zone can be observed via::
>   
> -	% cat /sys/device/system/memory/memoryXXX/valid_zones
> +	% cat /sys/devices/system/memory/memoryXXX/valid_zones
>   
>   Configuring Memory Hot(Un)Plug
>   ==============================
> @@ -326,7 +326,7 @@ however, a memory block might span memory holes. A memory block spanning memory
>   holes cannot be offlined.
>   
>   For example, assume 1 GiB memory block size. A device for a memory starting at
> -0x100000000 is ``/sys/device/system/memory/memory4``::
> +0x100000000 is ``/sys/devices/system/memory/memory4``::
>   
>   	(0x100000000 / 1Gib = 4)
>   

Reviewed-by: David Hildenbrand <david@...hat.com>

-- 
Cheers,

David / dhildenb