From: Simon Ser <contact@emersion.fr>
To: Ming Lin <mlin@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Hugh Dickins <hughd@google.com>, Peter Xu <peterx@redhat.com>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
Matthew Wilcox <willy@infradead.org>,
Dan Williams <dan.j.williams@intel.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Will Deacon <will@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Herrmann <dh.herrmann@gmail.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Greg Kroah-Hartman <greg@kroah.com>,
"tytso@mit.edu" <tytso@mit.edu>
Subject: Re: Sealed memfd & no-fault mmap
Date: Thu, 03 Jun 2021 20:49:10 +0000 [thread overview]
Message-ID: <IGhZyUzuyCCNa4ps92NEd37xL_9W5DZnA9lyO9FGO5sxo5U2hxrgcPhQWY_HB0guIjYotTWILfa6VwXOz2SVY7bOf2rz89gpdNdXAxKeshA=@emersion.fr> (raw)
In-Reply-To: <ca7afd0e-4fea-4601-6c06-36e0e3664945@kernel.org>
On Thursday, June 3rd, 2021 at 10:07 PM, Ming Lin <mlin@kernel.org> wrote:
> In the new version of the patches, MAP_NOSIGBUS is not restricted to shmem.
> It can be used on ordinary files.
Oh, cool!
FWIW, if I had to choose between "MAP_NOSIGBUS not restricted to shm"
and "MAP_NOSIGBUS not restricted to MAP_PRIVATE", I'd probably choose
the latter. But of course the former is better than nothing at all.
next prev parent reply other threads:[~2021-06-03 20:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 8:24 Sealed memfd & no-fault mmap Simon Ser
2021-04-27 16:51 ` Linus Torvalds
2021-04-27 16:51 ` Linus Torvalds
2021-04-29 15:48 ` Kirill A. Shutemov
2021-04-29 18:38 ` Peter Xu
2021-05-04 9:29 ` Simon Ser
2021-05-04 16:08 ` Linus Torvalds
2021-05-04 16:08 ` Linus Torvalds
2021-05-05 10:21 ` Simon Ser
2021-05-05 18:42 ` Linus Torvalds
2021-05-05 18:42 ` Linus Torvalds
2021-05-28 17:07 ` Lin, Ming
2021-05-29 1:03 ` Linus Torvalds
2021-05-29 1:03 ` Linus Torvalds
2021-05-29 7:31 ` Lin, Ming
2021-05-29 15:44 ` Linus Torvalds
2021-05-29 15:44 ` Linus Torvalds
2021-05-29 20:15 ` Hugh Dickins
2021-05-29 20:15 ` Hugh Dickins
2021-05-29 23:36 ` Ming Lin
2021-05-31 21:13 ` Ming Lin
2021-06-01 6:24 ` Linus Torvalds
2021-06-01 6:24 ` Linus Torvalds
2021-06-01 7:08 ` Ming Lin
2021-06-03 13:01 ` Simon Ser
2021-06-03 20:07 ` Ming Lin
2021-06-03 20:49 ` Simon Ser [this message]
2021-06-03 13:14 ` Simon Ser
2021-06-03 13:57 ` Matthew Wilcox
2021-06-03 14:48 ` Simon Ser
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='IGhZyUzuyCCNa4ps92NEd37xL_9W5DZnA9lyO9FGO5sxo5U2hxrgcPhQWY_HB0guIjYotTWILfa6VwXOz2SVY7bOf2rz89gpdNdXAxKeshA=@emersion.fr' \
--to=contact@emersion.fr \
--cc=dan.j.williams@intel.com \
--cc=dh.herrmann@gmail.com \
--cc=greg@kroah.com \
--cc=hughd@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mlin@kernel.org \
--cc=peterx@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.