[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <YOiZif/oQWkVzDgg@kernel.org>
Date: Fri, 9 Jul 2021 21:46:33 +0300
From: Mike Rapoport <rppt@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Kefeng Wang <wangkefeng.wang@...wei.com>,
Guenter Roeck <linux@...ck-us.net>,
Mike Rapoport <rppt@...nel.org>,
Mike Rapoport <rppt@...ux.ibm.com>,
Russell King <linux@...linux.org.uk>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: [GIT PULL] memblock, arm: fixup for the pfn_valid() rework for
v5.14-rc1
Hi Linus,
This is a fix for the rework of ARM's pfn_valid() implementation merged
during this merge window.
The following changes since commit a180bd1d7e16173d965b263c5a536aa40afa2a2a:
iov_iter: remove uaccess_kernel() warning from iov_iter_init() (2021-07-04 16:12:42 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock.git tags/fixes-2021-07-09
for you to fetch changes up to 024591f9a6e0164ec23301784d1e6d8f6cacbe59:
arm: ioremap: don't abuse pfn_valid() to check if pfn is in RAM (2021-07-06 09:01:47 +0300)
----------------------------------------------------------------
arm: ioremap: don't abuse pfn_valid() to check if pfn is in RAM
The semantics of pfn_valid() is to check presence of the memory map for a
PFN and not whether a PFN is in RAM. The memory map may be present for a
hole in the physical memory and if such hole corresponds to an MMIO range,
__arm_ioremap_pfn_caller() will produce a WARN() and fail:
Use memblock_is_map_memory() instead of pfn_valid() to check if a PFN is in
RAM or not.
----------------------------------------------------------------
Mike Rapoport (1):
arm: ioremap: don't abuse pfn_valid() to check if pfn is in RAM
arch/arm/mm/ioremap.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
--
Sincerely yours,
Mike.
Powered by blists - more mailing lists