From: Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>
To: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
RDMA mailing list
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Mark Bloch <markb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
Leon Romanovsky <leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH rdma-next v2 7/7] RDMA/nldev: Provide detailed QP information
Date: Tue, 9 Jan 2018 13:09:17 -0700 [thread overview]
Message-ID: <20180109200917.GF4518@ziepe.ca> (raw)
In-Reply-To: <20180102081832.5264-8-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
On Tue, Jan 02, 2018 at 10:18:32AM +0200, Leon Romanovsky wrote:
> + /* PID == 0 means that this QP was created by kernel */
> + if (qp->res.pid && nla_put_u32(msg,
> + RDMA_NLDEV_ATTR_RES_PID, qp->res.pid))
This is returning a pid in the init name space, obtained here:
+ res->pid = task_pid_nr(current);
And since the netlink user is not running in the init name space this
will return the wrong pid #, and worse potentially pids the current
name space should not see.
This API also needs to filter the results and only return pids
visible, and translate the pids as well..
I also suspsect this needs to be a netlink array of pids for future,
as we have hope someday to have RDMA uobjects shared between multiple
processes?
> + if (nla_put_string(msg,
> + RDMA_NLDEV_ATTR_RES_PID_COMM, qp->res.task_comm))
> + goto err;
Feels odd to return the content of /proc/XX/comm in netlink?
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-01-09 20:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 8:18 [PATCH rdma-next v2 0/7] RDMA resource tracking Leon Romanovsky
[not found] ` <20180102081832.5264-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2018-01-02 8:18 ` [PATCH rdma-next v2 1/7] RDMA/restrack: Add general infrastructure to track RDMA resources Leon Romanovsky
2018-01-02 8:18 ` [PATCH rdma-next v2 2/7] RDMA/core: Add helper function to create named QPs Leon Romanovsky
2018-01-02 8:18 ` [PATCH rdma-next v2 3/7] RDMA: Annotate create QP callers Leon Romanovsky
2018-01-02 8:18 ` [PATCH rdma-next v2 4/7] RDMA/core: Add resource tracking for create and destroy CQs Leon Romanovsky
2018-01-02 8:18 ` [PATCH rdma-next v2 5/7] RDMA/core: Add resource tracking for create and destroy PDs Leon Romanovsky
2018-01-02 8:18 ` [PATCH rdma-next v2 6/7] RDMA/nldev: Provide global resource utilization Leon Romanovsky
2018-01-02 8:18 ` [PATCH rdma-next v2 7/7] RDMA/nldev: Provide detailed QP information Leon Romanovsky
[not found] ` <20180102081832.5264-8-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2018-01-09 20:09 ` Jason Gunthorpe [this message]
[not found] ` <20180109200917.GF4518-uk2M96/98Pc@public.gmane.org>
2018-01-09 21:46 ` Parav Pandit
2018-01-10 7:17 ` Leon Romanovsky
[not found] ` <20180110071722.GF7368-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2018-01-10 22:56 ` Jason Gunthorpe
[not found] ` <20180110225622.GQ4518-uk2M96/98Pc@public.gmane.org>
2018-01-10 23:28 ` Steve Wise
2018-01-11 5:41 ` Leon Romanovsky
[not found] ` <20180111054141.GM7368-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2018-01-11 15:17 ` Steve Wise
2018-01-11 15:47 ` Leon Romanovsky
2018-01-11 5:37 ` Leon Romanovsky
2018-01-08 20:53 ` [PATCH rdma-next v2 0/7] RDMA resource tracking Steve Wise
2018-01-09 7:53 ` Leon Romanovsky
[not found] ` <20180109075344.GD6823-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2018-01-09 15:24 ` Steve Wise
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=20180109200917.GF4518@ziepe.ca \
--to=jgg-uk2m96/98pc@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=markb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.