s390/uv: fix memblock virtual vs physical address confusion
authorHeiko Carstens <hca@linux.ibm.com>
Mon, 13 Dec 2021 18:16:38 +0000 (19:16 +0100)
committerHeiko Carstens <hca@linux.ibm.com>
Thu, 16 Dec 2021 18:58:07 +0000 (19:58 +0100)
commit15b5c1833afc80b952383502eb06529db2b26219
treeebbbdfe1f1927647d2b06cf20dca6455624b7f5e
parentfcfcba6dfc9a57da9c816667c20614ddfd4def10
s390/uv: fix memblock virtual vs physical address confusion

memblock_alloc_try_nid() returns a virtual address, however in error
case the allocated memory is incorrectly freed with memblock_phys_free().
Properly use memblock_free() instead, and pass a physical address to
uv_init() to fix this.

Note: this doesn't fix a bug currently, since virtual and physical
addresses are identical.

Reviewed-by: Alexander Gordeev <agordeev@linux.ibm.com>
Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
arch/s390/kernel/uv.c