From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pl1-f202.google.com (mail-pl1-f202.google.com [209.85.214.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 3146A386C10 for ; Tue, 2 Jun 2026 21:56:05 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.214.202 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780437367; cv=none; b=LgLBeS5CAA+Kk3YksLcCqlVemk5bxHOQsmpQxOMd1zAdXXUL+CEcPoxoCgjKuUhnmRN/ahc0oK2oRmUtay/OHQs8/BMsj5wmxYy8Gdietk0vk0e7wDTvWGxvoqq/I8XoSESuExT7K3C1adlqHusl8eMzsSecBELHBcwF97xN0ok= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780437367; c=relaxed/simple; bh=hNGRPXZPv9VsFGCFlzGsilsBaOfx9YAE5+5vnJAC+ps=; h=Date:Mime-Version:Message-ID:Subject:From:To:Cc:Content-Type; b=GYhBEhh4Cl2OKuq0077gwAwrgu6Y9HIIoJGi4/tP4fBOrCTi9cGnEXyzvdD1ColZsUCCrIviWsMu8RQFiOiPb6wmus38fvUsC98H9q1AaSU07STcy6gADqf0GPOhDGJ4Wbna11YIBOMKNrAaTS2RQcQup4vbyO2KQhEOh3N2K8M= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=google.com; spf=pass smtp.mailfrom=flex--wyihan.bounces.google.com; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b=s7X6SGo2; arc=none smtp.client-ip=209.85.214.202 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=google.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=flex--wyihan.bounces.google.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="s7X6SGo2" Received: by mail-pl1-f202.google.com with SMTP id d9443c01a7336-2bf1845bddfso51370195ad.1 for ; Tue, 02 Jun 2026 14:56:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20251104; t=1780437364; x=1781042164; darn=vger.kernel.org; h=content-transfer-encoding:cc:to:from:subject:message-id :mime-version:date:from:to:cc:subject:date:message-id:reply-to; bh=y7tMKLqZLoUguahKVkzXwJunwH2CC8Y+lNvapE/6WPM=; b=s7X6SGo2eyAveVu+TUdTSMp8gBuV+ImpQGVebhJRxmab11A4TNO6Nndo3540M4AtwZ UbnZ0AVnF5gL2K3nPb+moFKsNIbptYBsfbZ4GGiVtmcY4qnOJgHHujeKXX17V4YKTu0U fZBsg6ZBhTpIjv8PowTdFBDvnI3nbREtKDTWqksFiCVH6YtModnKW3aeGhF1oyW+cYPS iT9YDCULFyoxVaXGW2z26pURPRIHuTT76hu3nDSz5PTCHc9qjYcYNejdVUkwge/rXZMV q/TdwEAB2QNZUTLSEuDiu6SmQGMgTq0R2OneZAwR1Rt00eoEnvEGo7gKgHxBDV4GgEsM w4jw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1780437364; x=1781042164; h=content-transfer-encoding:cc:to:from:subject:message-id :mime-version:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=y7tMKLqZLoUguahKVkzXwJunwH2CC8Y+lNvapE/6WPM=; b=YxyOTGH7heq+yJ2lmAus60OtNCaxjFyUJeBGp5GpoobjNdeSozYrSf9oWXzml5g74+ 8RMD7ms8GGj74qxka9lE8lIhr67S3r5dsgDWYx5/9NTdrwUX0EdPXXuxQYHhgI/oPJUC Jh487L2euwutEk9aesh+JdWQM4mexvJKqjEEOwHhzdSH+kszkODlzLCAYyLPIrhXohyX 6a0kX4XwwNhUc24f4PS3A6bRUsFFlbRknjAH+oxncs5CBeI3iOozCwfXftvaB9G91CAf VhmXWamwpOAIZ/pvbuPbdizy4lGDpFLFaMyjqRGUSp93VT2TXHyEMy3gDWjtij77kqEQ 2TPA== X-Forwarded-Encrypted: i=1; AFNElJ/j6RT9HYxlhuk8s1n1XX1SuI7jf9cj+94sKO6X5aShpRZ47seMgKkmzVo2Nxoo2axuUyiAvneu0C6N9k0=@vger.kernel.org X-Gm-Message-State: AOJu0Yywoju95gCVY8WCadaaUYixFdPShiXMNr7kCFVinof6Hki8R9nt RXnAigTne3d8blv7sDONw+YJ20DCIqjpUmVAPId4fnvhszAdeGbVdy1nUyMKPenw23STu9uTdv+ 4fuyiQw== X-Received: from plbbh1.prod.google.com ([2002:a17:902:a981:b0:2bd:bfca:529b]) (user=wyihan job=prod-delivery.src-stubby-dispatcher) by 2002:a17:902:c948:b0:2b2:4d36:7aa with SMTP id d9443c01a7336-2c1644cab59mr5323895ad.35.1780437364217; Tue, 02 Jun 2026 14:56:04 -0700 (PDT) Date: Tue, 02 Jun 2026 21:55:40 +0000 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 X-B4-Tracking: v=1; b=H4sIAFxRH2oC/x3MQQqDMBBG4avIrDsgQWvwKuJiav60A0ZlQqUi3 t3Q5fcW76QMU2Tqq5MMu2Zdl4LmUdH0keUN1lBMrnbPunUdJ6TVDo6i89fAKXLALAcCR/1xF1r xsREv/kXlsRlK/v+H8bpu5AUH/28AAAA= X-Change-Id: 20260527-memory-failure-mf-delayed-fix-7d5a8f4a8a8b X-Developer-Key: i=wyihan@google.com; a=ed25519; pk=cRi0fKzS5BMxlHyHY2pJv3w/1zcgfYKr6EYGYppdMYc= X-Developer-Signature: v=1; a=ed25519-sha256; t=1780437363; l=2245; i=wyihan@google.com; s=20260319; h=from:subject:message-id; bh=fRnbbxlBDk4YfThNS9s3/pmtvrbRvFIdtObDaBTv/hU=; b=D5bk2bmUWWudEj1T7hfEsakTn+vs93FjxKXokW9ffFkWPkCyo4/U4PI0D+/WRcNzSfFoIDCq0 DrI7ZczMCBoD8NfOhTuMdcBZJb+mUexkYE+ixEiHfOjRm1AvyTZ5eaw X-Mailer: b4 0.14.3 Message-ID: <20260602-memory-failure-mf-delayed-fix-v4-0-a5bc7db5a9b2@google.com> Subject: [PATCH v4 0/7] mm: Fix MF_DELAYED handling on memory failure From: Lisa Wang To: Miaohe Lin , Naoya Horiguchi , Andrew Morton , Paolo Bonzini , Shuah Khan , Hugh Dickins , Baolin Wang , David Hildenbrand , Lorenzo Stoakes , "Liam R. Howlett" , Vlastimil Babka , Mike Rapoport , Suren Baghdasaryan , Michal Hocko , linux-mm@kvack.org, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, linux-kselftest@vger.kernel.org Cc: rientjes@google.com, seanjc@google.com, ackerleytng@google.com, vannapurve@google.com, michael.roth@amd.com, jiaqiyan@google.com, tabba@google.com, dave.hansen@linux.intel.com, Lisa Wang Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Here's a fourth revision to fix MF_DELAYED handling on memory failure. This patch series addresses an issue in the memory failure handling path where MF_DELAYED is incorrectly treated as an error. This issue was discovered while testing memory failure handling for guest_memfd. The proposed solution involves - 1. Clarifying the definition of MF_DELAYED to mean that memory failure handling is only partially completed, and that the metadata for the memory that failed (as in struct page/folio) is still referenced. 2. Updating shmem=E2=80=99s handling to align with the clarified definition= . 3. Updating how the result of .error_remove_folio() is interpreted. Changes from v3: + Split an independent guest_memfd_memory_failure_test, as suggested by Ackerley and Sean + Align error logging style in truncate_error_folio, as suggested by Miaohe and David + Verify a clean shmem page can be read successfully after soft-offline memory failure, as suggested by Miaohe Thanks! + RFC v3: https://lore.kernel.org/all/20260408-memory-failure-mf-delayed-fi= x-rfc-v3-v3-0-718f45eb7c75@google.com/ Signed-off-by: Lisa Wang --- Lisa Wang (7): mm: memory_failure: Clarify the MF_DELAYED definition mm: memory_failure: Allow truncate_error_folio to return MF_DELAYED mm: shmem: Update shmem handler to the MF_DELAYED definition mm: memory_failure: Generalize extra_pins handling to all MF_DELAYED = cases mm: selftests: Add shmem into memory failure test KVM: selftests: Add the guest_memfd memory failure test KVM: selftests: Test guest_memfd behavior with respect to stage 2 pag= e tables mm/memory-failure.c | 29 +- mm/shmem.c | 2 +- tools/testing/selftests/kvm/Makefile.kvm | 2 + .../kvm/guest_memfd_memory_failure_test.c | 402 +++++++++++++++++= ++++ tools/testing/selftests/mm/memory-failure.c | 111 +++++- 5 files changed, 527 insertions(+), 19 deletions(-) --- base-commit: 38741a8e3bc1b809d64f8c8885ab15c3e40700ff change-id: 20260527-memory-failure-mf-delayed-fix-7d5a8f4a8a8b Best regards, --=20 Lisa Wang