From: Mike Kravetz <mike.kravetz@oracle.com>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: "Matthew Wilcox" <willy@infradead.org>,
"Hugh Dickins" <hughd@google.com>,
"Andrea Arcangeli" <aarcange@redhat.com>,
"Michal Hocko" <mhocko@kernel.org>,
"Marc-André Lureau" <marcandre.lureau@gmail.com>,
"David Herrmann" <dh.herrmann@gmail.com>,
"Khalid Aziz" <khalid.aziz@oracle.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Mike Kravetz" <mike.kravetz@oracle.com>
Subject: [PATCH v4 0/3] restructure memfd code
Date: Sun, 15 Apr 2018 11:21:16 -0700 [thread overview]
Message-ID: <20180415182119.4517-1-mike.kravetz@oracle.com> (raw)
This is a replacement for "Patch series restructure memfd code, v2"
which was previously in mmotm. This previous series incorrectly moved
the memfd code out of shemm.c as a separate commit. Please let me know
if there are any issues with the way code is restructured/moved in this
series. Specifically, the last patch.
While redoing the series, all sparse warnings in mm/shmem.c are fixed
in patch 1. Patch 2 updates comments, definitions, function names and
file checking such that patch 3 is code movement only.
v4 adds more cleanups in patch 2 before code movement.
Mike Kravetz (3):
mm/shmem: add __rcu annotations and properly deref radix entry
mm/shmem: update file sealing comments and file checking
mm: restructure memfd code
fs/Kconfig | 3 +
fs/fcntl.c | 2 +-
include/linux/memfd.h | 16 +++
include/linux/shmem_fs.h | 13 --
mm/Makefile | 1 +
mm/memfd.c | 345 +++++++++++++++++++++++++++++++++++++++++++++++
mm/shmem.c | 338 ++--------------------------------------------
7 files changed, 377 insertions(+), 341 deletions(-)
create mode 100644 include/linux/memfd.h
create mode 100644 mm/memfd.c
--
2.13.6
next reply other threads:[~2018-04-15 18:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-15 18:21 Mike Kravetz [this message]
2018-04-15 18:21 ` [PATCH v4 1/3] mm/shmem: add __rcu annotations and properly deref radix entry Mike Kravetz
2018-04-15 18:21 ` [PATCH v4 2/3] mm/shmem: update file sealing comments and file checking Mike Kravetz
2018-04-17 23:40 ` Khalid Aziz
2018-04-15 18:21 ` [PATCH v4 3/3] mm: restructure memfd code Mike Kravetz
2018-04-17 23:42 ` Khalid Aziz
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=20180415182119.4517-1-mike.kravetz@oracle.com \
--to=mike.kravetz@oracle.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dh.herrmann@gmail.com \
--cc=hughd@google.com \
--cc=khalid.aziz@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marcandre.lureau@gmail.com \
--cc=mhocko@kernel.org \
--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).