From: jackm <jackm@dev.mellanox.co.il>
To: Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>,
Jason Gunthorpe <jgg@nvidia.com>, Mark Bloch <markb@mellanox.com>,
Eli Cohen <eli@mellanox.co.il>,
linux-rdma@vger.kernel.org, Maor Gottlieb <maorg@nvidia.com>,
Roland Dreier <rolandd@cisco.com>,
Yishai Hadas <yishaih@nvidia.com>
Subject: Re: [PATCH rdma-rc] RDMA/mlx4: Read pkey table length instead of hardcoded value
Date: Sun, 23 Aug 2020 14:27:39 +0300 [thread overview]
Message-ID: <20200823142739.0000447e@dev.mellanox.co.il> (raw)
In-Reply-To: <20200823061754.573919-1-leon@kernel.org>
On Sun, 23 Aug 2020 09:17:54 +0300
Leon Romanovsky <leon@kernel.org> wrote:
> From: Mark Bloch <markb@mellanox.com>
>
> The driver shouldn't assume that a pkey table is available, this
> can happen if RoCE isn't supported by the device.
>
> Use the pkey table length reported by the device. This together with
> the cited commit from Jack caused a regression where mlx4 devices
> without RoCE aren't created.
I don't understand. Do you mean that WITH this patch there is a
regression, or do you mean that this patch FIXES the regression?
If this patch fixes the regression, I suggest the following replacement
text for the last paragraph:
If the pkey_table is not available (which is the case when RoCE is not
supported), the cited commit caused a regression where mlx4_devices
without RoCE are not created.
Fix this by returning a pkey table length of zero in procedure
eth_link_query_port() if the pkey-table length reported by the device
is zero.
>
> Cc: <stable@vger.kernel.org>
> Cc: Long Li <longli@microsoft.com>
> Fixes: 1901b91f9982 ("IB/core: Fix potential NULL pointer dereference
> in pkey cache") Fixes: fa417f7b520e ("IB/mlx4: Add support for IBoE")
> Signed-off-by: Mark Bloch <markb@mellanox.com>
> Reviewed-by: Maor Gottlieb <maorg@nvidia.com>
> Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
> ---
> drivers/infiniband/hw/mlx4/main.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/infiniband/hw/mlx4/main.c
> b/drivers/infiniband/hw/mlx4/main.c index 5e7910a517da..bd4f975e7f9a
> 100644 --- a/drivers/infiniband/hw/mlx4/main.c
> +++ b/drivers/infiniband/hw/mlx4/main.c
> @@ -784,7 +784,8 @@ static int eth_link_query_port(struct ib_device
> *ibdev, u8 port, props->ip_gids = true;
> props->gid_tbl_len =
> mdev->dev->caps.gid_table_len[port]; props->max_msg_sz =
> mdev->dev->caps.max_msg_sz;
> - props->pkey_tbl_len = 1;
I don't like depending on the caller to provide a zeroed-out props
structure.
I think it is better to do:
props->pkey_tbl_len = mdev->dev->caps.pkey_table_len[port] ? 1 : 0 ;
so that the pkey_table_len value is set no matter what.
> + if (mdev->dev->caps.pkey_table_len[port])
> + props->pkey_tbl_len = 1;
> props->max_mtu = IB_MTU_4096;
> props->max_vl_num = 2;
> props->state = IB_PORT_DOWN;
-Jack
next prev parent reply other threads:[~2020-08-23 11:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-23 6:17 [PATCH rdma-rc] RDMA/mlx4: Read pkey table length instead of hardcoded value Leon Romanovsky
2020-08-23 11:27 ` jackm [this message]
2020-08-23 12:33 ` Leon Romanovsky
2020-08-23 14:06 ` jackm
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=20200823142739.0000447e@dev.mellanox.co.il \
--to=jackm@dev.mellanox.co.il \
--cc=dledford@redhat.com \
--cc=eli@mellanox.co.il \
--cc=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=maorg@nvidia.com \
--cc=markb@mellanox.com \
--cc=rolandd@cisco.com \
--cc=yishaih@nvidia.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