From: Miaohe Lin <linmiaohe@huawei.com>
To: <akpm@linux-foundation.org>, <hughd@google.com>
Cc: <willy@infradead.org>, <vbabka@suse.cz>, <dhowells@redhat.com>,
<neilb@suse.de>, <apopple@nvidia.com>, <david@redhat.com>,
<surenb@google.com>, <peterx@redhat.com>, <rcampbell@nvidia.com>,
<naoya.horiguchi@nec.com>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>, <linmiaohe@huawei.com>
Subject: [PATCH v4 0/5] A few fixup patches for mm
Date: Thu, 19 May 2022 20:50:25 +0800 [thread overview]
Message-ID: <20220519125030.21486-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 and so on. More details can
be found in the respective changelogs. Thanks!
---
v4:
collect Reviewed-by per Naoya and David. Thanks for review!
fix infinite loop when swap in shmem error. Thanks Naoya for reporting
the issue!
v3:
collect Acked-by tag per David
remove unneeded pte wrprotect per David
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 (5):
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
mm/shmem: fix infinite loop when swap in shmem error at swapoff time
mm: filter out swapin error entry in shmem mapping
include/linux/swap.h | 7 ++++++-
include/linux/swapops.h | 10 ++++++++++
mm/madvise.c | 18 ++++++++++++------
mm/memory.c | 5 ++++-
mm/shmem.c | 39 +++++++++++++++++++++++++++++++++++++++
mm/swap_state.c | 3 +++
mm/swapfile.c | 21 ++++++++++++++++++---
7 files changed, 92 insertions(+), 11 deletions(-)
--
2.23.0
next reply other threads:[~2022-05-19 12:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 12:50 Miaohe Lin [this message]
2022-05-19 12:50 ` [PATCH v4 1/5] mm/swapfile: unuse_pte can map random data if swap read fails Miaohe Lin
2022-05-19 12:50 ` [PATCH v4 2/5] mm/swapfile: Fix lost swap bits in unuse_pte() Miaohe Lin
2022-05-19 12:50 ` [PATCH v4 3/5] mm/madvise: free hwpoison and swapin error entry in madvise_free_pte_range Miaohe Lin
2022-05-19 12:50 ` [PATCH v4 4/5] mm/shmem: fix infinite loop when swap in shmem error at swapoff time Miaohe Lin
2022-05-20 6:34 ` HORIGUCHI NAOYA(堀口 直也)
2022-05-20 8:17 ` Miaohe Lin
2022-05-22 23:53 ` HORIGUCHI NAOYA(堀口 直也)
2022-05-23 3:01 ` Miaohe Lin
2022-05-23 11:23 ` Miaohe Lin
2022-05-24 6:44 ` HORIGUCHI NAOYA(堀口 直也)
2022-05-24 10:56 ` Miaohe Lin
2022-05-21 9:34 ` Miaohe Lin
2022-05-24 22:10 ` Andrew Morton
2022-05-25 1:42 ` Miaohe Lin
2022-05-25 4:32 ` HORIGUCHI NAOYA(堀口 直也)
2022-05-25 6:40 ` Miaohe Lin
2022-05-26 6:08 ` HORIGUCHI NAOYA(堀口 直也)
2022-05-19 12:50 ` [PATCH v4 5/5] mm: filter out swapin error entry in shmem mapping Miaohe Lin
2022-05-25 4:53 ` HORIGUCHI NAOYA(堀口 直也)
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=20220519125030.21486-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=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@nec.com \
--cc=neilb@suse.de \
--cc=peterx@redhat.com \
--cc=rcampbell@nvidia.com \
--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;
as well as URLs for NNTP newsgroup(s).