Poison injection from debugfs is silent too. Add calling cxl_mem_report_poison() to make it able to do memory_failure().
Signed-off-by: Shiyang Ruan <ruansy.f...@fujitsu.com> --- drivers/cxl/core/memdev.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/cxl/core/memdev.c b/drivers/cxl/core/memdev.c index e976141ca4a9..b0dcbe6f1004 100644 --- a/drivers/cxl/core/memdev.c +++ b/drivers/cxl/core/memdev.c @@ -366,6 +366,7 @@ int cxl_inject_poison(struct cxl_memdev *cxlmd, u64 dpa) .length = cpu_to_le32(1), }; trace_cxl_poison(cxlmd, cxlr, &record, 0, 0, CXL_POISON_TRACE_INJECT); + cxl_mem_report_poison(cxlmd, cxlr, &record); out: up_read(&cxl_dpa_rwsem); up_read(&cxl_region_rwsem); -- 2.34.1