From: Miaohe Lin <linmiaohe@huawei.com>
To: <akpm@linux-foundation.org>, <naoya.horiguchi@nec.com>
Cc: <willy@infradead.org>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>, <linmiaohe@huawei.com>
Subject: [PATCH v2 0/4] A few fixup patches for mm
Date: Thu, 27 Jul 2023 19:56:39 +0800 [thread overview]
Message-ID: <20230727115643.639741-1-linmiaohe@huawei.com> (raw)
Hi everyone,
This series contains a few fixup patches to fix potential unexpected
return value, fix wrong swap entry type for hwpoisoned swapcache page
and so on. More details can be found in the respective changelogs.
Thanks!
Miaohe Lin (4):
mm/swapfile: fix wrong swap entry type for hwpoisoned swapcache page
mm: memory-failure: fix potential unexpected return value from
unpoison_memory()
mm: memory-failure: avoid false hwpoison page mapped error info
mm: memory-failure: add PageOffline() check
---
v2:
collect Reviewed-by and Acked-by tag per Matthew and Naoya.
1/4: a better fix per Matthew
2/4: fix a code smell per Naoya
Thanks!
---
mm/ksm.c | 2 ++
mm/memory-failure.c | 32 ++++++++++++++++++--------------
mm/swapfile.c | 8 ++++----
3 files changed, 24 insertions(+), 18 deletions(-)
--
2.33.0
next reply other threads:[~2023-07-27 11:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 11:56 Miaohe Lin [this message]
2023-07-27 11:56 ` [PATCH v2 1/4] mm/swapfile: fix wrong swap entry type for hwpoisoned swapcache page Miaohe Lin
2023-07-27 11:56 ` [PATCH v2 2/4] mm: memory-failure: fix potential unexpected return value from unpoison_memory() Miaohe Lin
2023-07-27 11:56 ` [PATCH v2 3/4] mm: memory-failure: avoid false hwpoison page mapped error info Miaohe Lin
2023-07-27 11:56 ` [PATCH v2 4/4] mm: memory-failure: add PageOffline() check Miaohe Lin
2023-07-27 16:57 ` [PATCH v2 0/4] A few fixup patches for mm Andrew Morton
2023-07-28 2:20 ` 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=20230727115643.639741-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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox