[lkml]   [2019]   [Jan]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 0/5] RDMA: reg_remote_mr
Steve Wise <> wrote on 01/29/2019 06:44:48 PM:

> On 1/29/2019 7:26 AM, Joel Nider wrote:
> > As discussed at LPC'18, there is a need to be able to register a
> > region (MR) on behalf of another process. One example is the case of
> > post-copy container migration, in which CRIU is responsible for
> > up the migration, but the contents of the memory are from the
> > process. In this case, we want all RDMA READ requests to be served by
> > the address space of the migration process directly (not by CRIU).
> > patchset implements a new uverbs command which allows an application
> > register a memory region in the address space of another process.
> Hey Joel,
> Dumb question:
> Doesn't this open a security hole by allowing any process to register
> memory in any other process?

Not a dumb question - there is a security problem. Jason just suggested
I look at how ptrace solves the problem, so that's my best option at the
moment. Still, I figured it was a good idea to let everyone take a look
at what I have so far, and start to get feedback.

> Steve.

 \ /
  Last update: 2019-01-30 09:23    [W:0.171 / U:24.332 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site