aboutsummaryrefslogtreecommitdiffstats
path: root/lib/xarray.c
diff options
context:
space:
mode:
authorGregory Price <[email protected]>2025-04-10 14:28:31 +0000
committerAndrew Morton <[email protected]>2025-05-13 06:50:49 +0000
commit3592a86a2b6be115000b82af78fe7f96fbc658a4 (patch)
tree97fa147e37b0fa740fc1e28213e358460146fdf3 /lib/xarray.c
parentmm: page-flags-layout.h: change the KASAN_TAG_WIDTH for HW_TAGS (diff)
downloadkernel-3592a86a2b6be115000b82af78fe7f96fbc658a4.tar.gz
kernel-3592a86a2b6be115000b82af78fe7f96fbc658a4.zip
DAX: warn when kmem regions are truncated for memory block alignment
Device capacity intended for use as system ram should be aligned to the architecture-defined memory block size or that capacity will be silently truncated and capacity stranded. As hotplug dax memory becomes more prevelant, the memory block size alignment becomes more important for platform and device vendors to pay attention to - so this truncation should not be silent. This issue is particularly relevant for CXL Dynamic Capacity devices, whose capacity may arrive in spec-aligned but block-misaligned chunks. Link: https://lkml.kernel.org/r/[email protected] Suggested-by: David Hildenbrand <[email protected]> Suggested-by: Dan Williams <[email protected]> Reviewed-by: Dan Williams <[email protected]> Tested-by: Alison Schofield <[email protected]> Reviewed-by: Jonathan Cameron <[email protected]> Acked-by: David Hildenbrand <[email protected]> Signed-off-by: Gregory Price <[email protected]> Cc: Dave Jiang <[email protected]> Cc: Vishal Verma <[email protected]> Signed-off-by: Andrew Morton <[email protected]>
Diffstat (limited to 'lib/xarray.c')
0 files changed, 0 insertions, 0 deletions