linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ming Lin <mlin@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Hugh Dickins <hughd@google.com>, Simon Ser <contact@emersion.fr>,
	Matthew Wilcox <willy@infradead.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org
Subject: [PATCH v2 0/2] mm: support NOSIGBUS on fault of mmap
Date: Fri,  4 Jun 2021 00:43:20 -0700	[thread overview]
Message-ID: <1622792602-40459-1-git-send-email-mlin@kernel.org> (raw)

These 2 patches are based on the discussion of "Sealed memfd & no-fault mmap"
at https://bit.ly/3pdwOGR

v2:
- make MAP_NOSIGBUS generic instead of being restricted to shmem
- use do_anonymous_page() to insert zero page
- fix build warnings/errors reported by LKP test robot

v1:
https://lkml.org/lkml/2021/6/1/1076

Ming Lin (2):
  mm: make "vm_flags" be an u64
  mm: adds NOSIGBUS extension to mmap()

 arch/arm64/Kconfig                           |   1 -
 arch/parisc/include/uapi/asm/mman.h          |   1 +
 arch/powerpc/Kconfig                         |   1 -
 arch/x86/Kconfig                             |   1 -
 drivers/android/binder.c                     |   6 +-
 drivers/gpu/drm/amd/amdkfd/kfd_chardev.c     |   2 +-
 drivers/gpu/drm/amd/amdkfd/kfd_doorbell.c    |   2 +-
 drivers/gpu/drm/amd/amdkfd/kfd_events.c      |   2 +-
 drivers/infiniband/hw/hfi1/file_ops.c        |   2 +-
 drivers/infiniband/hw/qib/qib_file_ops.c     |   4 +-
 fs/exec.c                                    |   2 +-
 fs/userfaultfd.c                             |   6 +-
 include/linux/huge_mm.h                      |   4 +-
 include/linux/ksm.h                          |   4 +-
 include/linux/mm.h                           | 108 +++++++++++++--------------
 include/linux/mm_types.h                     |   6 +-
 include/linux/mman.h                         |   5 +-
 include/uapi/asm-generic/mman-common.h       |   1 +
 mm/Kconfig                                   |   2 -
 mm/debug.c                                   |   4 +-
 mm/khugepaged.c                              |   2 +-
 mm/ksm.c                                     |   2 +-
 mm/madvise.c                                 |   2 +-
 mm/memory.c                                  |  15 +++-
 mm/mmap.c                                    |  14 ++--
 mm/mprotect.c                                |   4 +-
 mm/mremap.c                                  |   2 +-
 tools/include/uapi/asm-generic/mman-common.h |   1 +
 28 files changed, 108 insertions(+), 98 deletions(-)

-- 
1.8.3.1


             reply	other threads:[~2021-06-04  7:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-04  7:43 Ming Lin [this message]
2021-06-04  7:43 ` [PATCH v2 1/2] mm: make "vm_flags" be an u64 Ming Lin
2021-06-04  7:43 ` [PATCH v2 2/2] mm: adds NOSIGBUS extension to mmap() Ming Lin
2021-06-04 15:24   ` Kirill A. Shutemov
2021-06-04 16:22     ` Ming Lin
2021-06-28 14:27   ` Vivek Goyal
2021-06-30 16:37     ` Ming 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=1622792602-40459-1-git-send-email-mlin@kernel.org \
    --to=mlin@kernel.org \
    --cc=contact@emersion.fr \
    --cc=hughd@google.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=torvalds@linux-foundation.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).