Naman Jain 404cd6bffe mshv_vtl: Fix vmemmap_shift exceeding MAX_FOLIO_ORDER ... When registering VTL0 memory via MSHV_ADD_VTL0_MEMORY, the kernel computes pgmap->vmemmap_shift as the number of trailing zeros in the OR of start_pfn and last_pfn, intending to use the largest compound page order both endpoints are aligned to. However, this value is not clamped to MAX_FOLIO_ORDER, so a sufficiently aligned range (e.g. physical range [0x800000000000, 0x800080000000), corresponding to start_pfn=0x800000000 with 35 trailing zeros) can produce a shift larger than what memremap_pages() accepts, triggering a WARN and returning -EINVAL: WARNING: ... memremap_pages+0x512/0x650 requested folio size unsupported The MAX_FOLIO_ORDER check was added by commit 646b67d575 ("mm/memremap: reject unreasonable folio/compound page sizes in memremap_pages()"). Fix this by clamping vmemmap_shift to MAX_FOLIO_ORDER so we always request the largest order the kernel supports, in those cases, rather than an out-of-range value. Also fix the error path to propagate the actual error code from devm_memremap_pages() instead of hard-coding -EFAULT, which was masking the real -EINVAL return. Fixes: 7bfe3b8ea6 ("Drivers: hv: Introduce mshv_vtl driver") Cc: stable@vger.kernel.org Signed-off-by: Naman Jain <namjain@linux.microsoft.com> Reviewed-by: Michael Kelley <mhklinux@outlook.com> Signed-off-by: Wei Liu <wei.liu@kernel.org>		2026-04-14 04:44:31 +00:00
..
asm-generic	Scheduler changes for v7.0:	2026-02-10 12:50:10 -08:00
cxl
drm	Merge drm/drm-fixes into drm-misc-fixes	2026-02-23 10:09:45 +01:00
fwctl
linux	mshv_vtl: Fix vmemmap_shift exceeding MAX_FOLIO_ORDER	2026-04-14 04:44:31 +00:00
misc
mtd
rdma	RDMA v7.0 merge window	2026-02-12 17:05:20 -08:00
regulator
scsi
sound	ASoC: SOF: ipc4-topology: Add new tokens for pipeline direction	2026-02-04 13:26:05 +00:00
video
xen
Kbuild