From: "Steve Wise" <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: 'Jason Gunthorpe' <jgg-uk2M96/98Pc@public.gmane.org>
Cc: dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: RE: [PATCH v2 rdma-rc] RDMA/restrack: don't use uaccess_kernel()
Date: Fri, 16 Feb 2018 13:23:10 -0600 [thread overview]
Message-ID: <03ee01d3a75b$951f37f0$bf5da7d0$@opengridcomputing.com> (raw)
In-Reply-To: <20180216172537.GA10123-uk2M96/98Pc@public.gmane.org>
>
> On Wed, Feb 14, 2018 at 06:43:36PM -0800, Steve Wise wrote:
> > uaccess_kernel() isn't sufficient to determine if an rdma resource is
> > user-mode or not. For example, resources allocated in the add_one()
> > function of an ib_client get falsely labeled as user mode, when they
> > are kernel mode allocations. EG: mad qps.
> >
> > The result is that these qps are skipped over during a nldev query
> > because of an erroneous namespace mismatch.
> >
> > So now we determine if the resource is user-mode by looking at the
object
> > struct's uobject or similar pointer to know if it was allocated for user
> > mode applications.
> >
> > Fixes: 02d8883f520e ("RDMA/restrack: Add general infrastructure to track
> RDMA resources")
> > Signed-off-by: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
> >
> >
> > Changes since v1:
> >
> > changed _create_qp() to take the qp ib_uobject ptr so it is availble to
> > rdma_restrack_add()
> >
> > drivers/infiniband/core/core_priv.h | 4 +++-
> > drivers/infiniband/core/restrack.c | 35
> +++++++++++++++++++++++++++++++++--
> > drivers/infiniband/core/uverbs_cmd.c | 4 ++--
> > drivers/infiniband/core/verbs.c | 3 +--
> > 4 files changed, 39 insertions(+), 7 deletions(-)
>
> I took this to for-rc, but when I fixed the XRCD conflict with Leon's
> patch I ended up retyping it to this - don't really need all rambly
> boilerplate. Someone should fix the other one too..
I don't know what you mean by 'rambly boilerplate'?
>
> static bool res_is_user(struct rdma_restrack_entry *res)
> {
> switch (res->type) {
> case RDMA_RESTRACK_PD:
> return container_of(res, struct ib_pd, res)->uobject;
> case RDMA_RESTRACK_CQ:
> return container_of(res, struct ib_cq, res)->uobject;
> case RDMA_RESTRACK_QP:
> return container_of(res, struct ib_qp, res)->uobject;
> default:
> WARN_ONCE(true, "Wrong resource tracking type %u\n",
> res->type);
> return false;
> }
> }
This looks clean to me. Thanks.
--
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-02-16 19:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 2:43 [PATCH v2 rdma-rc] RDMA/restrack: don't use uaccess_kernel() Steve Wise
[not found] ` <20180216165919.997D72BB6D-ff04S8wfc4plDsoTORJclLwze2ij/50Q0E9HWUfgJXw@public.gmane.org>
2018-02-16 17:25 ` Jason Gunthorpe
[not found] ` <20180216172537.GA10123-uk2M96/98Pc@public.gmane.org>
2018-02-16 19:23 ` Steve Wise [this message]
2018-02-16 20:00 ` Jason Gunthorpe
2018-02-16 17:35 ` Leon Romanovsky
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='03ee01d3a75b$951f37f0$bf5da7d0$@opengridcomputing.com' \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=jgg-uk2M96/98Pc@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox