From: Christian Brauner <christian.brauner@ubuntu.com>
To: "Adalbert Lazăr" <alazar@bitdefender.com>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Alexander Graf <graf@amazon.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Jerome Glisse <jglisse@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Andy Lutomirski <luto@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Sargun Dhillon <sargun@sargun.me>,
Aleksa Sarai <cyphar@cyphar.com>, Oleg Nesterov <oleg@redhat.com>,
Jann Horn <jannh@google.com>, Kees Cook <keescook@chromium.org>,
Matthew Wilcox <willy@infradead.org>,
linux-api@vger.kernel.org
Subject: Re: [RFC PATCH 0/5] Remote mapping
Date: Fri, 4 Sep 2020 11:54:38 +0200 [thread overview]
Message-ID: <20200904095438.q3vuihvfivhdjvxs@wittgenstein> (raw)
In-Reply-To: <20200903174730.2685-1-alazar@bitdefender.com>
On Thu, Sep 03, 2020 at 08:47:25PM +0300, Adalbert Lazăr wrote:
> This patchset adds support for the remote mapping feature.
> Remote mapping, as its name suggests, is a means for transparent and
> zero-copy access of a remote process' address space.
> access of a remote process' address space.
Hey Adalbert,
Thanks for the patch. When you resend this patch series, could you
please make sure that everyone Cced on any individual patch receives the
full patch series? I only got patch 5/5 and it's a bit annoying because
one completely lacks context of what's going on. I first thought "did
someone just add a syscall with 3 lines of commit message?". :)
Could you please resend the patch series with linux-api, me and the
following people Cced:
Andy Lutomirski <luto@kernel.org>
Arnd Bergmann <arnd@arndb.de>
Sargun Dhillon <sargun@sargun.me>
Aleksa Sarai <cyphar@cyphar.com>
Oleg Nesterov <oleg@redhat.com>
Jann Horn <jannh@google.com>
Kees Cook <keescook@chromium.org>
Matthew Wilcox <willy@infradead.org>
linux-api@vger.kernel.org
Christian
next prev parent reply other threads:[~2020-09-04 9:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 17:47 Adalbert Lazăr
2020-09-03 17:47 ` [RFC PATCH 1/5] mm: add atomic capability to zap_details Adalbert Lazăr
2020-09-03 17:47 ` [RFC PATCH 2/5] mm: let the VMA decide how zap_pte_range() acts on mapped pages Adalbert Lazăr
2020-09-03 17:47 ` [RFC PATCH 3/5] mm/mmu_notifier: remove lockdep map, allow mmu notifier to be used in nested scenarios Adalbert Lazăr
2020-09-03 17:47 ` [RFC PATCH 4/5] mm/remote_mapping: use a pidfd to access memory belonging to unrelated process Adalbert Lazăr
2020-09-03 17:47 ` [RFC PATCH 5/5] pidfd_mem: implemented remote memory mapping system call Adalbert Lazăr
2020-09-03 18:08 ` [RFC PATCH 0/5] Remote mapping Adalbert Lazăr
2020-09-04 9:54 ` Christian Brauner [this message]
2020-09-04 11:34 ` Adalbert Lazăr
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=20200904095438.q3vuihvfivhdjvxs@wittgenstein \
--to=christian.brauner@ubuntu.com \
--cc=akpm@linux-foundation.org \
--cc=alazar@bitdefender.com \
--cc=arnd@arndb.de \
--cc=cyphar@cyphar.com \
--cc=graf@amazon.com \
--cc=jannh@google.com \
--cc=jglisse@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=oleg@redhat.com \
--cc=pbonzini@redhat.com \
--cc=sargun@sargun.me \
--cc=stefanha@redhat.com \
--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