linux-kernel - Re: [PATCH v2] memblock: Move late alloc warning down to phys alloc

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]

Date: Thu, 20 Jun 2024 00:53:06 +0300
From: Mike Rapoport <rppt@...nel.org>
To: Andrew Morton <akpm@...ux-foundation.org>,
	James Gowans <jgowans@...zon.com>
Cc: Mike Rapoport <rppt@...nel.org>,
	linux-mm@...ck.org,
	linux-kernel@...r.kernel.org,
	Alex Graf <graf@...zon.de>
Subject: Re: [PATCH v2] memblock: Move late alloc warning down to phys alloc

From: Mike Rapoport (IBM) <rppt@...nel.org>

On Wed, 19 Jun 2024 11:55:55 +0200, James Gowans wrote:
> If a driver/subsystem tries to do an allocation after the memblock
> allocations have been freed and the memory handed to the buddy
> allocator, it will not actually be legal to use that allocation: the
> buddy allocator owns the memory. Currently this mis-use is handled by
> the memblock function which does allocations and returns virtual
> addresses by printing a warning and doing a kmalloc instead. However
> the physical allocation function does not to do this check - callers of
> the physical alloc function are unprotected against mis-use.
> 
> [...]

Applied to for-next branch of memblock.git tree, thanks!

[1/1] memblock: Move late alloc warning down to phys alloc
      commit: 94ff46de4a738e7916b68ab5cc0b0380729f02af

tree: https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock
branch: for-next

--
Sincerely yours,
Mike.