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]
Message-Id: <162196703657.2318431.4855809369951976839.b4-ty@kernel.org>
Date:   Tue, 25 May 2021 19:58:41 +0100
From:   Will Deacon <will@...nel.org>
To:     Anshuman Khandual <anshuman.khandual@....com>,
        linux-arm-kernel@...ts.infradead.org
Cc:     catalin.marinas@....com, kernel-team@...roid.com,
        Will Deacon <will@...nel.org>, linux-kernel@...r.kernel.org,
        Mark Rutland <mark.rutland@....com>
Subject: Re: [PATCH] arm64/mm: Make vmemmap_free() available only with CONFIG_MEMORY_HOTPLUG

On Mon, 24 May 2021 13:10:30 +0530, Anshuman Khandual wrote:
> vmemmap_free() callsites (mm/sparse.c) and declaration (include/linux/mm.h)
> are protected with CONFIG_MEMORY_HOTPLUG. This function is not required if
> CONFIG_MEMORY_HOTPLUG is not enabled. Hence move the config wrapper outside
> the function definition.

Applied to arm64 (for-next/mm), thanks!

[1/1] arm64/mm: Make vmemmap_free() available only with CONFIG_MEMORY_HOTPLUG
      https://git.kernel.org/arm64/c/40221c737608

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ