From: Leon Romanovsky <leonro@nvidia.com>
To: Gal Pressman <galpress@amazon.com>
Cc: Avihai Horon <avihaih@nvidia.com>,
Maor Gottlieb <maorg@nvidia.com>,
Jason Gunthorpe <jgg@nvidia.com>,
linux-rdma@vger.kernel.org, "Leybovich,
Yossi" <sleybo@amazon.com>
Subject: Re: New GID query API broke EFA
Date: Thu, 22 Oct 2020 14:21:00 +0300 [thread overview]
Message-ID: <20201022112100.GE2611066@unreal> (raw)
In-Reply-To: <3e956560-3c76-5f4b-b8fa-ad96483cd042@amazon.com>
On Thu, Oct 22, 2020 at 01:58:29PM +0300, Gal Pressman wrote:
> Hi all,
>
> The new IOCTL query GID API 9f85cbe50aa0 ("RDMA/uverbs: Expose the new GID query
> API to user space") currently breaks EFA, as ibv_query_gid() no longer works.
>
> The problem is that the IOCTL call checks for:
> if (!rdma_ib_or_roce(ib_dev, port_num))
> return -EOPNOTSUPP;
>
> EFA is neither of these, but it uses GIDs.
>
> Any objections to remove the check? Any other solutions come to mind?
We added this check to protect access to rdma_get_gid_attr() for devices
without GID table.
1234 table = rdma_gid_table(device, port_num);
1235 if (index < 0 || index >= table->sz)
1236 return ERR_PTR(-EINVAL);
So you can extend that function to return for table == NULL an error and
remove rdma_ib_or_roce()
Thanks
>
> Gal
next prev parent reply other threads:[~2020-10-22 11:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 10:58 New GID query API broke EFA Gal Pressman
2020-10-22 11:21 ` Leon Romanovsky [this message]
2020-10-22 11:49 ` Gal Pressman
2020-10-22 12:10 ` Jason Gunthorpe
2020-10-22 12:12 ` Gal Pressman
2020-10-22 12:15 ` Gal Pressman
2020-10-22 12:23 ` Leon Romanovsky
2020-10-22 12:23 ` Leon Romanovsky
2020-10-22 16:37 ` Jason Gunthorpe
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=20201022112100.GE2611066@unreal \
--to=leonro@nvidia.com \
--cc=avihaih@nvidia.com \
--cc=galpress@amazon.com \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=maorg@nvidia.com \
--cc=sleybo@amazon.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 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.