IB/srpt: Log private data associated with REJ

To make it possible to determine why an initiator sent a REJ,
log the private data associated with the received REJ packet.

Signed-off-by: Bart Van Assche <bart.vanassche@sandisk.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Cc: Sagi Grimberg <sagig@mellanox.com>
Cc: Alex Estrin <alex.estrin@intel.com>
Signed-off-by: Doug Ledford <dledford@redhat.com>

diff --git a/drivers/infiniband/ulp/srpt/ib_srpt.c b/drivers/infiniband/ulp/srpt/ib_srpt.c
index 10bc1333a62c9613004025009e6d9d60b895d175..0bf204ec443e864e2c845ba2b111c7d6f70852d8 100644 (file)
--- a/drivers/infiniband/ulp/srpt/ib_srpt.c
+++ b/drivers/infiniband/ulp/srpt/ib_srpt.c
@@ -2252,8 +2252,18 @@ static void srpt_cm_rej_recv(struct srpt_rdma_ch *ch,
                             const u8 *private_data,
                             u8 private_data_len)
 {
-       pr_info("Received CM REJ for ch %s-%d; reason %d.\n",
-               ch->sess_name, ch->qp->qp_num, reason);
+       char *priv = NULL;
+       int i;
+
+       if (private_data_len && (priv = kmalloc(private_data_len * 3 + 1,
+                                               GFP_KERNEL))) {
+               for (i = 0; i < private_data_len; i++)
+                       sprintf(priv + 3 * i, " %02x", private_data[i]);
+       }
+       pr_info("Received CM REJ for ch %s-%d; reason %d%s%s.\n",
+               ch->sess_name, ch->qp->qp_num, reason, private_data_len ?
+               "; private data" : "", priv ? priv : " (?)");
+       kfree(priv);
        srpt_drain_channel(ch);
 }