From: Peter Xu <peterx@redhat.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Matthew Wilcox <willy@infradead.org>,
Dan Williams <dan.j.williams@intel.com>,
Simon Ser <contact@emersion.fr>,
"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, 29 Apr 2021 14:38:36 -0400 [thread overview]
Message-ID: <20210429183836.GF8339@xz-x1> (raw)
In-Reply-To: <20210429154807.hptls4vnmq2svuea@box>
On Thu, Apr 29, 2021 at 06:48:07PM +0300, Kirill A. Shutemov wrote:
> > Side note: this will only ever work for non-shared mappings.
>
> I think it's show-stopper for the use-case, no? IIUC, the mappings is used
> for communication between a compositor and a client and has to be shared.
Yes I had the same doubt.. Besides, we probably don't want to convert all
VM_FAULT_SIGBUS to fallback to anonymous pages, as I see that vmf_error()
converts mostly everything besides -ENOMEM to VM_FAULT_SIGBUS. Thanks,
--
Peter Xu
next prev parent reply other threads:[~2021-04-29 18:38 UTC|newest]
Thread overview: 23+ 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-29 15:48 ` Kirill A. Shutemov
2021-04-29 18:38 ` Peter Xu [this message]
2021-05-04 9:29 ` Simon Ser
2021-05-04 16:08 ` Linus Torvalds
2021-05-05 10:21 ` Simon Ser
2021-05-05 18:42 ` Linus Torvalds
2021-05-28 17:07 ` Lin, Ming
2021-05-29 1:03 ` Linus Torvalds
2021-05-29 7:31 ` Lin, Ming
2021-05-29 15:44 ` Linus Torvalds
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 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
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=20210429183836.GF8339@xz-x1 \
--to=peterx@redhat.com \
--cc=contact@emersion.fr \
--cc=dan.j.williams@intel.com \
--cc=dh.herrmann@gmail.com \
--cc=greg@kroah.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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 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).