linux-kernel - Re: [PATCH v3 1/2] mm/memblock: Add reserved memory release function

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: <Z7RwWyD67BxWPnK8@kernel.org>
Date: Tue, 18 Feb 2025 13:34:51 +0200
From: Mike Rapoport <rppt@...nel.org>
To: Masami Hiramatsu <mhiramat@...nel.org>
Cc: Steven Rostedt <rostedt@...dmis.org>, linux-kernel@...r.kernel.org,
	linux-trace-kernel@...r.kernel.org,
	Mark Rutland <mark.rutland@....com>,
	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH v3 1/2] mm/memblock: Add reserved memory release function

On Tue, Feb 18, 2025 at 11:47:11AM +0200, Mike Rapoport wrote:
> On Tue, Feb 18, 2025 at 05:42:57PM +0900, Masami Hiramatsu wrote:
> > Hi Mike,
> > 
> > 
> > Thanks! but I can not use free_reserved_area() here because it uses
> > virt_to_page(). Here we only know the physical address in the map.
> > I think we can use free_reserved_page() instead. Is that OK?
> 
> For reserve_mem ranges virt_to_phys() will work, they are allocated from the

I meant phys_to_virt() of course :)

> memory that is covered by the direct map.

-- 
Sincerely yours,
Mike.