linux-kernel - Re: [PATCH 1/3] mm,thp: no space after colon in Mem-Info fields

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: <57cd9256-1295-c797-5711-807732421063@redhat.com>
Date:   Tue, 15 Aug 2023 19:52:35 +0200
From:   David Hildenbrand <david@...hat.com>
To:     Hugh Dickins <hughd@...gle.com>,
        Andrew Morton <akpm@...ux-foundation.org>
Cc:     Alexey Dobriyan <adobriyan@...il.com>,
        linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH 1/3] mm,thp: no space after colon in Mem-Info fields

On 14.08.23 22:00, Hugh Dickins wrote:
> The SysRq-m or OOM Mem-Info dmesg showed (long lines containing)
> ... shmem:NkB shmem_thp: NkB shmem_pmdmapped: NkB anon_thp: NkB ...
> 
> Delete the space after the colon after shmem_thp, shmem_pmdmapped,
> anon_thp: as the shmem example shows, no other fields have a space
> after the colon in this output.
> 
> Signed-off-by: Hugh Dickins <hughd@...gle.com>
> ---
>   mm/show_mem.c | 6 +++---
>   1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/mm/show_mem.c b/mm/show_mem.c
> index 09c7d036d49e..4b888b18bdde 100644
> --- a/mm/show_mem.c
> +++ b/mm/show_mem.c
> @@ -251,9 +251,9 @@ static void show_free_areas(unsigned int filter, nodemask_t *nodemask, int max_z
>   			" writeback:%lukB"
>   			" shmem:%lukB"
>   #ifdef CONFIG_TRANSPARENT_HUGEPAGE
> -			" shmem_thp: %lukB"
> -			" shmem_pmdmapped: %lukB"
> -			" anon_thp: %lukB"
> +			" shmem_thp:%lukB"
> +			" shmem_pmdmapped:%lukB"
> +			" anon_thp:%lukB"
>   #endif
>   			" writeback_tmp:%lukB"
>   			" kernel_stack:%lukB"

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

-- 
Cheers,

David / dhildenb