> I think that another viewpoint of how we prioritize memory type to scan > is kernel vs userspace memory. Current hwpoison mechanism does little to > recover from errors in kernel pages (slab, reserved), so there seesm > little benefit to detect such errors proactively and beforehand. If the > resource for scanning is limited, the user might think of focusing on > scanning userspace memory. Page cache is (in some many use cases) a large user of kernel memory, and there would be options for recovery if errors were pre-emptively found: clean page -> re-read from storage, modified page -> mark in some way to force EIO for read() and fail(?) mmap(). -Tony
