linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Doug Ledford <dledford@redhat.com>,
	Avihai Horon <avihaih@nvidia.com>,
	linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
	Mark Zhang <markzhang@nvidia.com>,
	"Michael S. Tsirkin" <mst@dev.mellanox.co.il>
Subject: Re: [PATCH rdma-next 2/3] RDMA/core: Let ib_find_gid() continue search even after empty entry
Date: Wed, 8 Dec 2021 08:51:59 +0200	[thread overview]
Message-ID: <YbBWD5rDm+wBxVjU@unreal> (raw)
In-Reply-To: <20211207184304.GB114160@nvidia.com>

On Tue, Dec 07, 2021 at 02:43:04PM -0400, Jason Gunthorpe wrote:
> On Mon, Nov 22, 2021 at 01:53:57PM +0200, Leon Romanovsky wrote:
> > From: Avihai Horon <avihaih@nvidia.com>
> > 
> > Currently, ib_find_gid() will stop searching after encountering the
> > first empty GID table entry. This behavior is wrong since neither IB
> > nor RoCE spec enforce tightly packed GID tables.
> > 
> > For example, when a valid GID entry exists at index N, and if a GID
> > entry is empty at index N-1, ib_find_gid() will fail to find the valid
> > entry.
> > 
> > Fix it by making ib_find_gid() continue searching even after
> > encountering missing entries.
> > 
> > Fixes: 5eb620c81ce3 ("IB/core: Add helpers for uncached GID and P_Key searches")
> > Signed-off-by: Avihai Horon <avihaih@nvidia.com>
> > Reviewed-by: Mark Zhang <markzhang@nvidia.com>
> > Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
> >  drivers/infiniband/core/device.c | 3 +++
> >  1 file changed, 3 insertions(+)
> > 
> > diff --git a/drivers/infiniband/core/device.c b/drivers/infiniband/core/device.c
> > index 22a4adda7981..b5d8443030d4 100644
> > +++ b/drivers/infiniband/core/device.c
> > @@ -2460,8 +2460,11 @@ int ib_find_gid(struct ib_device *device, union ib_gid *gid,
> >  		for (i = 0; i < device->port_data[port].immutable.gid_tbl_len;
> >  		     ++i) {
> >  			ret = rdma_query_gid(device, port, i, &tmp_gid);
> > +			if (ret == -ENOENT)
> > +				continue;
> >  			if (ret)
> >  				return ret;
> 
> There is no return code from rdma_query_gid that means stop searching,

In rdma_query_gid() any error stopped searching, and here we continue
same behaviour as before. You can argue that this function can't really
get illegal parameters and it never returns -EINVAL, but someone needs
to check all callers that this is true.

> so just write
> 
> if (ret)
>    continue

As long as we don't delete input validity checks, it is not correct.

Thanks

> 
> Jason

  reply	other threads:[~2021-12-08  6:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22 11:53 [PATCH rdma-next 0/3] Skip holes in GID tables Leon Romanovsky
2021-11-22 11:53 ` [PATCH rdma-next 1/3] RDMA/core: Modify rdma_query_gid() to return accurate error codes Leon Romanovsky
2021-12-07 18:41   ` Jason Gunthorpe
2021-11-22 11:53 ` [PATCH rdma-next 2/3] RDMA/core: Let ib_find_gid() continue search even after empty entry Leon Romanovsky
2021-12-07 18:43   ` Jason Gunthorpe
2021-12-08  6:51     ` Leon Romanovsky [this message]
2021-12-09  0:13       ` Jason Gunthorpe
2021-11-22 11:53 ` [PATCH rdma-next 3/3] RDMA/cma: Let cma_resolve_ib_dev() " Leon Romanovsky
2021-12-07 18:44   ` 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=YbBWD5rDm+wBxVjU@unreal \
    --to=leon@kernel.org \
    --cc=avihaih@nvidia.com \
    --cc=dledford@redhat.com \
    --cc=jgg@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=markzhang@nvidia.com \
    --cc=mst@dev.mellanox.co.il \
    /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;
as well as URLs for NNTP newsgroup(s).