RDMA/umem: Do not use current->tgid to track the mm_struct

Browse source

This is just wrong, the process that calls into the reg_mr is the process
associated with the umem, and that does not have to be the same process
that created the context.

When this code was first written mmgrab() didn't exist, however these days
we can just directly hold the mm_struct pointer in the umem and have no
ambiguity when it comes to releasing the umem as to which mm it was
associated with.

Signed-off-by: Jason Gunthorpe <jgg@mellanox.com>
Signed-off-by: Leon Romanovsky <leonro@mellanox.com>
Signed-off-by: Doug Ledford <dledford@redhat.com>

...

This commit is contained in:

Jason Gunthorpe 2018-09-16 20:44:45 +03:00 • committed by Doug Ledford

parent ce92db1ca8

commit d4b4dd1b97

2 changed files with 37 additions and 43 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

77

drivers/infiniband/core/umem.c

View file

3

include/rdma/ib_umem.h

View file