From: David Stevens <stevensd@chromium.org>
To: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>
Cc: Peter Xu <peterx@redhat.com>,
Matthew Wilcox <willy@infradead.org>,
"Kirill A . Shutemov" <kirill@shutemov.name>,
Yang Shi <shy828301@gmail.com>,
David Hildenbrand <david@redhat.com>,
Hugh Dickins <hughd@google.com>, Jiaqi Yan <jiaqiyan@google.com>,
linux-kernel@vger.kernel.org,
David Stevens <stevensd@chromium.org>
Subject: [PATCH v5 0/3] mm/khugepaged: fix khugepaged+shmem races
Date: Tue, 7 Mar 2023 14:20:33 +0900 [thread overview]
Message-ID: <20230307052036.1520708-1-stevensd@google.com> (raw)
From: David Stevens <stevensd@chromium.org>
Fix two races in khugepaged+shmem that cause issues with userfaultfd and
lseek, respectively.
v4 -> v5:
- Rebase on mm-unstable (9caa15b8a499)
- Gather acks
v3 -> v4:
- Base changes on mm-everything (fba720cb4dc0)
- Add patch to refactor error handling control flow in collapse_file
- Rebase userfaultfd patch with no significant logic changes
- Different approach for fixing lseek race
v2 -> v3:
- Use XA_RETRY_ENTRY to synchronize with reads from the page cache
under the RCU read lock in userfaultfd fix
- Add patch to fix lseek race
v1 -> v2:
- Different approach for userfaultfd fix
David Stevens (3):
mm/khugepaged: refactor collapse_file control flow
mm/khugepaged: skip shmem with userfaultfd
mm/khugepaged: maintain page cache uptodate flag
include/trace/events/huge_memory.h | 3 +-
mm/khugepaged.c | 259 ++++++++++++++++-------------
2 files changed, 142 insertions(+), 120 deletions(-)
--
2.40.0.rc0.216.gc4246ad0f0-goog
next reply other threads:[~2023-03-07 5:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 5:20 David Stevens [this message]
2023-03-07 5:20 ` [PATCH v5 1/3] mm/khugepaged: refactor collapse_file control flow David Stevens
2023-03-23 19:51 ` Hugh Dickins
2023-03-07 5:20 ` [PATCH v5 2/3] mm/khugepaged: skip shmem with userfaultfd David Stevens
2023-03-23 19:48 ` Hugh Dickins
2023-03-24 5:34 ` David Stevens
2023-03-28 15:48 ` Peter Xu
2023-03-07 5:20 ` [PATCH v5 3/3] mm/khugepaged: maintain page cache uptodate flag David Stevens
2023-03-23 19:07 ` Hugh Dickins
2023-03-23 21:56 ` Matthew Wilcox
2023-03-23 22:28 ` Song Liu
2023-03-24 1:56 ` Hugh Dickins
2023-03-24 3:30 ` Matthew Wilcox
2023-03-24 6:03 ` Song Liu
2023-03-24 13:31 ` Matthew Wilcox
2023-03-29 16:53 ` Song Liu
2023-03-28 9:48 ` David Stevens
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=20230307052036.1520708-1-stevensd@google.com \
--to=stevensd@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=hughd@google.com \
--cc=jiaqiyan@google.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.com \
--cc=shy828301@gmail.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