diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2021-07-10 18:17:13 +0200 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2021-07-10 18:17:13 +0200 |
commit | b6fd9e259457b847646844ed202b830e585289dd (patch) | |
tree | 95c6ae71b2102b8038cc56ea1feb20228f08dbf7 /drivers/char/hw_random/Kconfig | |
parent | Merge branch 'for-5.14-fixes' of git://git.kernel.org/pub/scm/linux/kernel/gi... (diff) | |
parent | arm: ioremap: don't abuse pfn_valid() to check if pfn is in RAM (diff) | |
download | linux-b6fd9e259457b847646844ed202b830e585289dd.tar.xz linux-b6fd9e259457b847646844ed202b830e585289dd.zip |
Merge tag 'fixes-2021-07-09' of git://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock
Pull memblock fix from Mike Rapoport:
"This is a fix for the rework of ARM's pfn_valid() implementation
merged during this merge window.
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"
* tag 'fixes-2021-07-09' of git://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock:
arm: ioremap: don't abuse pfn_valid() to check if pfn is in RAM
Diffstat (limited to 'drivers/char/hw_random/Kconfig')
0 files changed, 0 insertions, 0 deletions