On Fri, 30 May 2014 15:43:39 -0700
Roland Dreier rol...@purestorage.com wrote:
Looks like this is actually a bug... assuming you guys agree the patch
is correct, I'll add the following:
commit 165cb465f73c (HEAD, mlx4)
Author: Roland Dreier rol...@purestorage.com
Date: Fri May 30
From: Jack Morgenstein ja...@dev.mellanox.co.il
Secure-host is the general term for the capability of a device
to protect itself and the subnet from malicious host software.
This is achieved by:
1. Not allowing un-trusted entities to access device configuration registers,
directly (through
From: Tomer Cohen tome...@mellanox.com
PathQuery is received during heavy-sweep caused by just rebooted node.
The PathQuery is received for the new node during discovery stage
when no LID is still assigned to the node.
Fix: change from using OSM_LOG_ERROR to OSM_LOG_DEBUG for ERR 1F20 and 1F21
From: Tomer Cohen tome...@mellanox.com
In vl15_send_mad, there is a use in the function osm_vendor_send that could
free the p_madw and after the use of that function we use another function
the need p_madw.
Fix: save the parameters needed beforehand.
Signed-off-by: Tomer Cohen
At the SCSI transport level, there is no distinction between
user data and protection information. Thus, iscsi header field
expected data transfer length should include protection
information.
This set modifies both the iscsi initiator (patch #1), and
target (patch #2) to expect data length which
In various areas of the code, it is assumed that
se_cmd-data_length describes pure data. In case
that protection information exists over the wire
(protect bits is are on) the target core decrease
the protection length from the data length (instead
of each transport peeking in the cdb).
Modify
Hi all,
Today's linux-next merge of the infiniband tree got a conflict in
drivers/net/ethernet/mellanox/mlx4/cmd.c between commit 1a91de28831a
(mellanox: Logging message cleanups) from the net-next tree and
commit 97982f5a91e9 (IB/mlx4: Preparation for VFs to issue/receive SMI
(QP0)
