linux-kernel - Re: [PATCH RESEND] infiniband:core:Add needed error path in cm_init_av_by

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20151215173022.GB25965@obsidianresearch.com>
Date:	Tue, 15 Dec 2015 10:30:22 -0700
From:	Jason Gunthorpe <jgunthorpe@...idianresearch.com>
To:	Michael Wang <yun.wang@...fitbricks.com>
Cc:	Nicholas Krause <xerofoify@...il.com>, dledford@...hat.com,
	sean.hefty@...el.com, hal.rosenstock@...il.com,
	haggaie@...lanox.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 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.

Jason
--
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/