From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Michael Wang <yun.wang@profitbricks.com>
Cc: Nicholas Krause <xerofoify@gmail.com>,
dledford@redhat.com, sean.hefty@intel.com,
hal.rosenstock@gmail.com, haggaie@mellanox.com,
matanb@mellanox.com, doront@mellanox.com, david.ahern@oracle.com,
erezsh@mellanox.com, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] infiniband:core:Add needed error path in cm_init_av_by_path
Date: Wed, 16 Dec 2015 11:16:44 -0700 [thread overview]
Message-ID: <20151216181644.GF32594@obsidianresearch.com> (raw)
In-Reply-To: <56713C5F.5020507@profitbricks.com>
On Wed, Dec 16, 2015 at 11:26:39AM +0100, Michael Wang wrote:
>
> On 12/15/2015 06:30 PM, Jason Gunthorpe wrote:
> > On Tue, Dec 15, 2015 at 05:38:34PM +0100, Michael Wang wrote:
> >> The hop_limit is only suggest that the package allowed to be
> >> routed, not have to, correct?
> >
> > If the hop limit is >= 2 (?) then the GRH is mandatory. The
> > SM will return this information in the PathRecord if it determines a
> > GRH is required. The whole stack follows this protocol.
> >
> > The GRH is optional for in-subnet communications.
>
> Thanks for the explain :-)
>
> I've rechecked the ib_init_ah_from_path() again, and found it
> still set IB_AH_GRH when the GID cache missing, but with:
How do you mean?
ah_attr->ah_flags = IB_AH_GRH;
ah_attr->grh.dgid = rec->dgid;
ret = ib_find_cached_gid(device, &rec->sgid, ndev, &port_num,
&gid_index);
if (ret) {
if (ndev)
dev_put(ndev);
return ret;
}
If find_cached_gid fails then ib_init_ah_from_path also fails.
Is there a case where ib_find_cached_gid can succeed but not return
good data?
I agree it would read nicer if the ah_flags and gr.dgid was moved
after the ib_find_cached_gid
> BTW, cma_sidr_rep_handler() also call ib_init_ah_from_path() with out
> a check on return.
That sounds like a problem.
Jason
next prev parent reply other threads:[~2015-12-16 18:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1450194724-7107-1-git-send-email-xerofoify@gmail.com>
2015-12-15 16:38 ` [PATCH RESEND] infiniband:core:Add needed error path in cm_init_av_by_path Michael Wang
2015-12-15 17:30 ` Jason Gunthorpe
2015-12-16 6:52 ` ira.weiny
2015-12-16 10:26 ` Michael Wang
2015-12-16 18:16 ` Jason Gunthorpe [this message]
2015-12-17 8:43 ` Michael Wang
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=20151216181644.GF32594@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=david.ahern@oracle.com \
--cc=dledford@redhat.com \
--cc=doront@mellanox.com \
--cc=erezsh@mellanox.com \
--cc=haggaie@mellanox.com \
--cc=hal.rosenstock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=matanb@mellanox.com \
--cc=sean.hefty@intel.com \
--cc=xerofoify@gmail.com \
--cc=yun.wang@profitbricks.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