From: Mike Rapoport <rppt@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>,
James Gowans <jgowans@amazon.com>
Cc: Mike Rapoport <rppt@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Alex Graf <graf@amazon.de>
Subject: Re: [PATCH v2] memblock: Move late alloc warning down to phys alloc
Date: Thu, 20 Jun 2024 00:53:06 +0300 [thread overview]
Message-ID: <171883398192.3581885.4505580925551979480.b4-ty@kernel.org> (raw)
In-Reply-To: <20240619095555.85980-1-jgowans@amazon.com>
From: Mike Rapoport (IBM) <rppt@kernel.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.
next prev parent reply other threads:[~2024-06-19 21:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 9:55 James Gowans
2024-06-19 21:53 ` Mike Rapoport [this message]
2024-06-21 1:15 ` Wei Yang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=171883398192.3581885.4505580925551979480.b4-ty@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=graf@amazon.de \
--cc=jgowans@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox