public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Lidong Chen <jemmy858585@gmail.com>
Cc: dledford@redhat.com, akpm@linux-foundation.org,
	qing.huang@oracle.com, leon@kernel.org, artemyko@mellanox.com,
	dan.j.williams@intel.com, linux-rdma@vger.kernel.org,
	linux-kernel@vger.kernel.org, adido@mellanox.com,
	galsha@mellanox.com, aviadye@mellanox.com,
	Lidong Chen <lidongchen@tencent.com>
Subject: Re: [PATCH v2] IB/umem: ib_ucontext already have tgid, remove pid from ib_umem structure
Date: Tue, 15 May 2018 17:14:45 -0600	[thread overview]
Message-ID: <20180515231445.GA15921@ziepe.ca> (raw)
In-Reply-To: <1525769416-14596-1-git-send-email-lidongchen@tencent.com>

On Tue, May 08, 2018 at 04:50:16PM +0800, Lidong Chen wrote:
> The userspace may invoke ibv_reg_mr and ibv_dereg_mr by different threads.
> If when ibv_dereg_mr invoke and the thread which invoked ibv_reg_mr has
> exited, get_pid_task will return NULL, ib_umem_release does not decrease
> mm->pinned_vm. This patch fixes it by use tgid in ib_ucontext struct.
> 
> Signed-off-by: Lidong Chen <lidongchen@tencent.com>
> ---
>  [v2]
>  - use ib_ucontext tgid instread of tgid in ib_umem structure
>  
>  drivers/infiniband/core/umem.c | 7 +------
>  include/rdma/ib_umem.h         | 1 -
>  2 files changed, 1 insertion(+), 7 deletions(-)

Applied to for-rc, thanks.

It would be nice to send a cleanup to have all the users of tgid doing
this pattern

	task = get_pid_task(umem->context->tgid, PIDTYPE_PID);
  	if (!task)
  		goto out;
  	mm = get_task_mm(task);

To call some kind of common function like ib_get_mr_mm(), just to make
it really clear what is happening. 

Jason

  reply	other threads:[~2018-05-15 23:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-08  8:50 [PATCH v2] IB/umem: ib_ucontext already have tgid, remove pid from ib_umem structure Lidong Chen
2018-05-15 23:14 ` Jason Gunthorpe [this message]
2018-05-16  7:32   ` 858585 jemmy
2018-06-13  4:36 ` Jason Gunthorpe
2018-06-13  9:25   ` 858585 jemmy

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=20180515231445.GA15921@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=adido@mellanox.com \
    --cc=akpm@linux-foundation.org \
    --cc=artemyko@mellanox.com \
    --cc=aviadye@mellanox.com \
    --cc=dan.j.williams@intel.com \
    --cc=dledford@redhat.com \
    --cc=galsha@mellanox.com \
    --cc=jemmy858585@gmail.com \
    --cc=leon@kernel.org \
    --cc=lidongchen@tencent.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=qing.huang@oracle.com \
    /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