From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, willy@infradead.org,
naoya.horiguchi@nec.com, dan.j.williams@intel.com,
jane.chu@oracle.com, akpm@linux-foundation.org
Subject: [folded-merged] mm-convert-dax-lock-unlock-page-to-lock-unlock-folio-fix.patch removed from -mm tree
Date: Wed, 04 Oct 2023 13:17:02 -0700 [thread overview]
Message-ID: <20231004201703.B95AEC433C7@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm-convert-dax-lock-unlock-page-to-lock-unlock-folio-fix
has been removed from the -mm tree. Its filename was
mm-convert-dax-lock-unlock-page-to-lock-unlock-folio-fix.patch
This patch was dropped because it was folded into mm-convert-dax-lock-unlock-page-to-lock-unlock-folio.patch
------------------------------------------------------
From: Jane Chu <jane.chu@oracle.com>
Subject: mm-convert-dax-lock-unlock-page-to-lock-unlock-folio-fix
Date: Fri, 8 Sep 2023 16:23:36 -0600
add comment to mf_generic_kill_procss(), simplify
mf_generic_kill_procs:folio initialization.
Link: https://lkml.kernel.org/r/20230908222336.186313-1-jane.chu@oracle.com
Signed-off-by: Jane Chu <jane.chu@oracle.com>
Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
Acked-by: Naoya Horiguchi <naoya.horiguchi@nec.com>
Cc: Dan Williams <dan.j.williams@intel.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/memory-failure.c | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)
--- a/mm/memory-failure.c~mm-convert-dax-lock-unlock-page-to-lock-unlock-folio-fix
+++ a/mm/memory-failure.c
@@ -1713,11 +1713,19 @@ static void unmap_and_kill(struct list_h
kill_procs(to_kill, flags & MF_MUST_KILL, false, pfn, flags);
}
+/*
+ * Only dev_pagemap pages get here, such as fsdax when the filesystem
+ * either do not claim or fails to claim a hwpoison event, or devdax.
+ * The fsdax pages are initialized per base page, and the devdax pages
+ * could be initialized either as base pages, or as compound pages with
+ * vmemmap optimization enabled. Devdax is simplistic in its dealing with
+ * hwpoison, such that, if a subpage of a compound page is poisoned,
+ * simply mark the compound head page is by far sufficient.
+ */
static int mf_generic_kill_procs(unsigned long long pfn, int flags,
struct dev_pagemap *pgmap)
{
- struct page *page = pfn_to_page(pfn);
- struct folio *folio = page_folio(page);
+ struct folio *folio = pfn_folio(pfn);
LIST_HEAD(to_kill);
dax_entry_t cookie;
int rc = 0;
_
Patches currently in -mm which might be from jane.chu@oracle.com are
mm-convert-dax-lock-unlock-page-to-lock-unlock-folio.patch
reply other threads:[~2023-10-04 20:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231004201703.B95AEC433C7@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=jane.chu@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=naoya.horiguchi@nec.com \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.