IPoIB: Fix ipoib_neigh hashing to use the correct daddr octets
authorShlomo Pongratz <shlomop@mellanox.com>
Tue, 19 Feb 2013 15:40:22 +0000 (15:40 +0000)
committerRoland Dreier <roland@purestorage.com>
Tue, 19 Feb 2013 16:21:35 +0000 (08:21 -0800)
commit9d1ad66e3eae0faf3f19a618da74b4c377474845
treede98249a872d731bb382d6e51575dfa77fd89694
parent836dc9e3fbbab0c30aa6e664417225f5c1fb1c39
IPoIB: Fix ipoib_neigh hashing to use the correct daddr octets

The hash function introduced in commit b63b70d877 ("IPoIB: Use a
private hash table for path lookup in xmit path") was designd to use
the 3 octets of the IPoIB HW address that holds the remote QPN.
However, this currently isn't the case on little-endian machines,
because the the code there uses the flags part (octet[0]) and not the
last octet of the QPN (octet[3]).  Fix this.

The fix caused a checkpatch warning on line over 80 characters, to
solve that changed the name of the temp variable that holds the daddr.

Signed-off-by: Shlomo Pongratz <shlomop@mellanox.com>
Signed-off-by: Or Gerlitz <ogerlitz@mellanox.com>
Signed-off-by: Roland Dreier <roland@purestorage.com>
drivers/infiniband/ulp/ipoib/ipoib.h
drivers/infiniband/ulp/ipoib/ipoib_main.c