linux-kernel - Re: [PATCH v3] mm/hugetlb: avoid hardcoding while checking if cma is enable

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: <20200707125641.dbd2ccd63f525aa5870069d8@linux-foundation.org>
Date:   Tue, 7 Jul 2020 12:56:41 -0700
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Barry Song <song.bao.hua@...ilicon.com>
Cc:     <linux-mm@...ck.org>, <linux-kernel@...r.kernel.org>,
        <linuxarm@...wei.com>, Mike Kravetz <mike.kravetz@...cle.com>,
        Jonathan Cameron <jonathan.cameron@...wei.com>,
        Roman Gushchin <guro@...com>
Subject: Re: [PATCH v3] mm/hugetlb: avoid hardcoding while checking if cma
 is enable

On Tue, 7 Jul 2020 16:02:04 +1200 Barry Song <song.bao.hua@...ilicon.com> wrote:

> hugetlb_cma[0] can be NULL due to various reasons, for example, node0 has
> no memory. so NULL hugetlb_cma[0] doesn't necessarily mean cma is not
> enabled. gigantic pages might have been reserved on other nodes.

I'm trying to figure out whether this should be backported into 5.7.1,
but the changelog doesn't describe any known user-visible effects of
the bug.  Are there any?