linux-kernel - Re: [PATCH] sparc64: Register hugepages during arch init

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] [day] [month] [year] [list]

Date:   Thu, 20 Jul 2017 12:38:26 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     nitin.m.gupta@...cle.com
Cc:     bob.picco@...cle.com, pasha.tatashin@...cle.com,
        steven.sistare@...cle.com, paul.gortmaker@...driver.com,
        thomas.tai@...cle.com, atish.patra@...cle.com,
        sparclinux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] sparc64: Register hugepages during arch init

From: Nitin Gupta <nitin.m.gupta@...cle.com>
Date: Wed, 19 Jul 2017 17:12:54 -0700

> Add hstate for each supported hugepage size using
> arch initcall. This change fixes some hugepage
> parameter parsing inconsistencies:
> 
> case 1: no hugepage parameters
> 
>  Without hugepage parameters, only a hugepages-8192kB entry is visible
>  in sysfs.  It's different from x86_64 where both 2M and 1G hugepage
>  sizes are available.
> 
> case 2: default_hugepagesz=[64K|256M|2G]
> 
>  When specifying only a default_hugepagesz parameter, the default
>  hugepage size isn't really changed and it stays at 8M. This is again
>  different from x86_64.
> 
> Orabug: 25869946
> 
> Reviewed-by: Bob Picco <bob.picco@...cle.com>
> Signed-off-by: Nitin Gupta <nitin.m.gupta@...cle.com>

Applied and queued up for -stable, thanks.