From: Miaohe Lin <linmiaohe@huawei.com>
To: <akpm@linux-foundation.org>, <naoya.horiguchi@nec.com>,
<shy828301@gmail.com>, <mike.kravetz@oracle.com>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
<linmiaohe@huawei.com>
Subject: [PATCH v3 0/2] A few fixup patches for memory failure
Date: Fri, 18 Mar 2022 15:39:43 +0800 [thread overview]
Message-ID: <20220318073945.62164-1-linmiaohe@huawei.com> (raw)
Hi everyone,
This series contains a patch to avoid calling invalidate_inode_page()
with unexpected pages and another one to make non-LRU movable pages
unhandlable. More details can be found in the respective changelogs.
Thanks!
---
v2->v3:
drop patch "mm/memory-failure.c: fix race with changing page compound again"
collect reviewed-by and acked-by tag
fix stale commit id in the commit log
v1->v2:
drop "mm/memory-failure.c: fix wrong user reference report"
make non-LRU movable pages unhandlable
fix confusing commit log and introduce MF_MSG_DIFFERENT_PAGE_SIZE
Many thanks Naoya, Mike and Yang Shi for review!
---
Miaohe Lin (2):
mm/memory-failure.c: avoid calling invalidate_inode_page() with
unexpected pages
mm/memory-failure.c: make non-LRU movable pages unhandlable
mm/memory-failure.c | 22 ++++++++++++++--------
1 file changed, 14 insertions(+), 8 deletions(-)
--
2.23.0
next reply other threads:[~2022-03-17 11:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 7:39 Miaohe Lin [this message]
2022-03-18 7:39 ` [PATCH v3 1/2] mm/memory-failure.c: avoid calling invalidate_inode_page() with unexpected pages Miaohe Lin
2022-03-17 12:29 ` David Hildenbrand
2022-03-18 6:29 ` Miaohe Lin
2022-03-18 7:39 ` [PATCH v3 2/2] mm/memory-failure.c: make non-LRU movable pages unhandlable Miaohe Lin
2022-03-17 12:11 ` David Hildenbrand
2022-03-18 6:28 ` Miaohe Lin
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=20220318073945.62164-1-linmiaohe@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=naoya.horiguchi@nec.com \
--cc=shy828301@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox