linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Chengguang Xu <cgxu519@mykernel.net>
To: linux-unionfs@vger.kernel.org, linux-mm@kvack.org
Cc: miklos@szeredi.hu, akpm@linux-foundation.org, amir73il@gmail.com,
	riteshh@linux.ibm.com, Chengguang Xu <cgxu519@mykernel.net>
Subject: [RFC PATCH 0/3] ovl: stacked mmap for shared map
Date: Sat, 29 Aug 2020 17:50:58 +0800	[thread overview]
Message-ID: <20200829095101.25350-1-cgxu519@mykernel.net> (raw)

Currently, there is still ro/rw inconsistency related to shared mmap
in overlayfs, this patch set implements stacked mmap for shared map
and transfer necessary operations to upper inode, so that we can keep
data consistency in any kind of mmap. 

Patch 1 exports necessary functions from kernel to module.
Patch 2 introduces struct ovl_file_entry to store real vm_ops.
Patch 3 implements stacked mmap for shared map to keep data
consistency.

Chengguang Xu (3):
  mm: mmap: export necessary functions for overlayfs' mmap
  ovl: introduce struct ovl_file_entry
  ovl: implement stacked mmap for shared map

 fs/overlayfs/file.c | 178 ++++++++++++++++++++++++++++++++++++++++----
 include/linux/mm.h  |   2 +
 mm/filemap.c        |  28 +++++++
 mm/internal.h       |  22 ------
 4 files changed, 195 insertions(+), 35 deletions(-)

-- 
2.20.1




             reply	other threads:[~2020-08-29  9:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-29  9:50 Chengguang Xu [this message]
2020-08-29  9:50 ` [RFC PATCH 1/3] mm: mmap: export necessary functions for overlayfs' mmap Chengguang Xu
2020-08-29  9:51 ` [RFC PATCH 2/3] ovl: introduce struct ovl_file_entry Chengguang Xu
2020-08-29  9:51 ` [RFC PATCH 3/3] ovl: implement stacked mmap for shared map Chengguang Xu
2020-08-30 11:33   ` Amir Goldstein
2020-08-31 13:47     ` cgxu
2020-08-31 15:51       ` Amir Goldstein
2020-09-01  7:44         ` Miklos Szeredi
2020-09-01 13:20         ` cgxu

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=20200829095101.25350-1-cgxu519@mykernel.net \
    --to=cgxu519@mykernel.net \
    --cc=akpm@linux-foundation.org \
    --cc=amir73il@gmail.com \
    --cc=linux-mm@kvack.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=riteshh@linux.ibm.com \
    /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