[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <5670420A.7040202@profitbricks.com>
Date: Tue, 15 Dec 2015 17:38:34 +0100
From: Michael Wang <yun.wang@...fitbricks.com>
To: Nicholas Krause <xerofoify@...il.com>, dledford@...hat.com
Cc: sean.hefty@...el.com, hal.rosenstock@...il.com,
haggaie@...lanox.com, jgunthorpe@...idianresearch.com,
matanb@...lanox.com, doront@...lanox.com, david.ahern@...cle.com,
erezsh@...lanox.com, linux-rdma@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH RESEND] infiniband:core:Add needed error path in
cm_init_av_by_path
On 12/15/2015 04:52 PM, Nicholas Krause wrote:
> This adds a needed error path in the function, cm_init_av_by_path
> after the call to ib_init_ah_from_path in order to avoid incorrectly
> accessing the path pointer of structure type ib_sa_path_rec if this
> function call fails to complete its intended work successfully by
> returning a error code.
>
> Signed-off-by: Nicholas Krause <xerofoify@...il.com>
> ---
> drivers/infiniband/core/cm.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/infiniband/core/cm.c b/drivers/infiniband/core/cm.c
> index 0a26dd6..e9b36ea 100644
> --- a/drivers/infiniband/core/cm.c
> +++ b/drivers/infiniband/core/cm.c
> @@ -383,8 +383,11 @@ static int cm_init_av_by_path(struct ib_sa_path_rec *path, struct cm_av *av)
> return ret;
>
> av->port = port;
> - ib_init_ah_from_path(cm_dev->ib_device, port->port_num, path,
> - &av->ah_attr);
> + ret = ib_init_ah_from_path(cm_dev->ib_device, port->port_num, path,
> + &av->ah_attr);
..Just wondering what if the transport don't require GRH?
eg inside the same subnet?
The hop_limit is only suggest that the package allowed to be
routed, not have to, correct?
Regards,
Michael Wang
> + if (ret)
> + return ret;
> +
> av->timeout = path->packet_life_time + 1;
>
> return 0;
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists