Version: 1
-Previous: ca1e622129c0fb7b89b427c4d6f7874610981cae
-Head: b39623bafe64454772c2a82b4136aa82a11f1fea
+Previous: 9b11c328af0cc377e7868a12046557b5f78162fb
+Head: f41f55208635f9c56f53f7e227ecf9dec0ada6df
Applied:
- sgid: 78bd3e7da18bedf817dfc9711df6dbd6a5b11827
- refresh-temp: b39623bafe64454772c2a82b4136aa82a11f1fea
+ sgid: f41f55208635f9c56f53f7e227ecf9dec0ada6df
Unapplied:
v1.1make: 97cdca7d9a0224cc251d4edf06b5425fa9eb4575
v1.1: ee76313542729235d4ba51aa3d012ea29a996ab8
+++ /dev/null
-Bottom: 4df8fa519baf0e24c5af25c6000d5277b1798cff
-Top: 4df8fa519baf0e24c5af25c6000d5277b1798cff
-Author: Sean Hefty <sean.hefty@intel.com>
-Date: 2015-07-29 16:56:58 -0700
-
-Refresh of sgid
-
----
-
-
If a PR query is issued with the DGID set, but the SGID not set,
then opensm version 3.3.19 (and likely others) will return a PR
-with the SGID set to that of the SM. This is a change from
-previous versions of opensm, which used the SGID of the requesting
-port.
+with the SGID set to that of the SM. This appears to be a bug
+with the SM, as an SLID is provided.
-In order to be safe, specify the source address as part of the
-PR query, so that we get a PR that's usable for connecting to
-the source.
+In order to be safe, specify the SGID with the PR query, so that
+we get a PR that's usable.
Signed-off-by: Sean Hefty <sean.hefty@intel.com>