From: Miaohe Lin <linmiaohe@huawei.com>
To: <akpm@linux-foundation.org>
Cc: <willy@infradead.org>, <vbabka@suse.cz>, <dhowells@redhat.com>,
<neilb@suse.de>, <david@redhat.com>, <apopple@nvidia.com>,
<surenb@google.com>, <minchan@kernel.org>, <peterx@redhat.com>,
<sfr@canb.auug.org.au>, <naoya.horiguchi@nec.com>,
<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
<linmiaohe@huawei.com>
Subject: [PATCH v2 0/3] A few fixup patches for mm
Date: Thu, 21 Apr 2022 20:53:45 +0800 [thread overview]
Message-ID: <20220421125348.62483-1-linmiaohe@huawei.com> (raw)
Hi everyone,
This series contains a few patches to avoid mapping random data if swap
read fails and fix lost swap bits in unuse_pte. Also we free hwpoison and
swapin error entry in madvise_free_pte_range. More details can be found
in the respective changelogs. Thanks!
---
v2:
make the terminology consistent and collect Acked-by tag per David
fix lost swap bits in unuse_pte per Peter
free hwpoison and swapin error entry per Alistair
Many thanks Alistair, David and Peter for review!
---
Miaohe Lin (3):
mm/swapfile: unuse_pte can map random data if swap read fails
mm/swapfile: Fix lost swap bits in unuse_pte()
mm/madvise: free hwpoison and swapin error entry in
madvise_free_pte_range
include/linux/swap.h | 7 ++++++-
include/linux/swapops.h | 10 ++++++++++
mm/madvise.c | 13 ++++++++-----
mm/memory.c | 5 ++++-
mm/swapfile.c | 23 ++++++++++++++++++++---
5 files changed, 48 insertions(+), 10 deletions(-)
--
2.23.0
next reply other threads:[~2022-04-21 12:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 12:53 Miaohe Lin [this message]
2022-04-21 12:53 ` [PATCH v2 1/3] mm/swapfile: unuse_pte can map random data if swap read fails Miaohe Lin
2022-04-21 12:53 ` [PATCH v2 2/3] mm/swapfile: Fix lost swap bits in unuse_pte() Miaohe Lin
2022-04-21 13:13 ` David Hildenbrand
2022-04-21 13:50 ` Miaohe Lin
2022-04-21 12:53 ` [PATCH v2 3/3] mm/madvise: free hwpoison and swapin error entry in madvise_free_pte_range Miaohe Lin
2022-04-21 13:25 ` David Hildenbrand
2022-04-21 13:44 ` Miaohe Lin
2022-04-21 14:28 ` Peter Xu
2022-04-22 2:47 ` Miaohe Lin
2022-04-22 2:52 ` Peter Xu
2022-04-22 3:15 ` 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=20220421125348.62483-1-linmiaohe@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=david@redhat.com \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=naoya.horiguchi@nec.com \
--cc=neilb@suse.de \
--cc=peterx@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--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