From: swise@opengridcomputing.com (Steve Wise)
Subject: [PATCH 6/6] nvme/rdma: Make nvme_rdma_conn_rejected() more informative
Date: Thu, 20 Oct 2016 09:35:54 -0500 [thread overview]
Message-ID: <00bf01d22adf$43370ac0$c9a52040$@opengridcomputing.com> (raw)
In-Reply-To: <66e66d19-5a2a-e867-401a-1ede0c845b3e@sandisk.com>
>
> While I was figuring out how to make the nvme-rdma driver log in to
> the nvmet-rdma driver, the following message appeared in the system
> log:
>
> nvme nvme0: Connect rejected, status 0.
>
> That message is not very helpful. Hence this patch that makes the
> messages reported by nvme_rdma_conn_rejected() more informative.
>
> Signed-off-by: Bart Van Assche <bart.vanassche at sandisk.com>
> ---
> drivers/nvme/host/rdma.c | 39 +++++++++++++++++++++++++++++----------
> 1 file changed, 29 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/nvme/host/rdma.c b/drivers/nvme/host/rdma.c
> index 9612ea0..df7f599 100644
> --- a/drivers/nvme/host/rdma.c
> +++ b/drivers/nvme/host/rdma.c
> @@ -1207,20 +1207,39 @@ static int nvme_rdma_conn_established(struct
> nvme_rdma_queue *queue)
> }
>
> static int nvme_rdma_conn_rejected(struct nvme_rdma_queue *queue,
> - struct rdma_cm_event *ev)
> + const struct rdma_cm_event *ev)
> {
> - if (ev->param.conn.private_data_len) {
> - struct nvme_rdma_cm_rej *rej =
> - (struct nvme_rdma_cm_rej *)ev-
> >param.conn.private_data;
> + char reason[32];
>
> - dev_err(queue->ctrl->ctrl.device,
> - "Connect rejected, status %d.", le16_to_cpu(rej->sts));
> - /* XXX: Think of something clever to do here... */
> - } else {
> - dev_err(queue->ctrl->ctrl.device,
> - "Connect rejected, no private data.\n");
> + switch (ev->status) {
> + case IB_CM_REJ_DUPLICATE_LOCAL_COMM_ID:
> + strlcpy(reason, "duplicate local comm id", sizeof(reason));
> + break;
> + case IB_CM_REJ_CONSUMER_DEFINED:
> + if (ev->param.conn.private_data_len) {
> + const struct nvme_rdma_cm_rej *rej =
> + (const void *)ev->param.conn.private_data;
> +
> + snprintf(reason, sizeof(reason), "status %d",
> + le16_to_cpu(rej->sts));
> + /* XXX: Think of something clever to do here... */
> + } else {
> + strlcpy(reason, "no private data", sizeof(reason));
> + }
> + break;
> + case IB_CM_REJ_INVALID_SERVICE_ID:
> + strlcpy(reason, "invalid service ID", sizeof(reason));
> + break;
> + case IB_CM_REJ_STALE_CONN:
> + strlcpy(reason, "stale connection", sizeof(reason));
> + break;
> + default:
> + snprintf(reason, sizeof(reason), "REJ reason %#x", ev->status);
> + break;
Hey Bart,
iWARP RDMA_CM_EVENT_REJECTED events have a -errno as the event status. Perhaps
you could at the very least dump the error as an integer here? But an errno
string would be ideal. :)
Steve.
next prev parent reply other threads:[~2016-10-20 14:35 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 20:09 [PATCH 0/6] Six NVMeOF-related patches Bart Van Assche
2016-10-18 20:10 ` [PATCH 1/6] nvme/scsi: Remove set-but-not-used variables Bart Van Assche
2016-10-19 7:26 ` Johannes Thumshirn
2016-10-19 10:31 ` Christoph Hellwig
2016-10-18 20:10 ` [PATCH 2/6] nvme-fabrics: Adjust source code indentation Bart Van Assche
2016-10-19 7:26 ` Johannes Thumshirn
2016-10-19 10:31 ` Christoph Hellwig
2016-10-18 20:10 ` [PATCH 3/6] nvme-fabrics: Fix memory leaks in nvmf_parse_options() Bart Van Assche
2016-10-19 7:27 ` Johannes Thumshirn
2016-10-19 10:37 ` Christoph Hellwig
2016-10-18 20:11 ` [PATCH 4/6] nvme-fabrics: Fix a memory leak in an nvmf_create_ctrl() error path Bart Van Assche
2016-10-19 7:27 ` Johannes Thumshirn
2016-10-19 10:37 ` Christoph Hellwig
2016-10-18 20:11 ` [PATCH 5/6] nvme-fabrics: Print network address if address resolution fails Bart Van Assche
2016-10-19 7:27 ` Johannes Thumshirn
2016-10-19 10:39 ` Christoph Hellwig
2016-10-19 17:02 ` Bart Van Assche
2016-10-20 7:54 ` Sagi Grimberg
2016-10-18 20:12 ` [PATCH 6/6] nvme/rdma: Make nvme_rdma_conn_rejected() more informative Bart Van Assche
2016-10-19 7:29 ` Johannes Thumshirn
2016-10-19 10:41 ` Christoph Hellwig
2016-10-19 17:08 ` Bart Van Assche
2016-10-20 7:57 ` Sagi Grimberg
2016-10-20 14:35 ` Steve Wise [this message]
2016-10-20 17:34 ` Bart Van Assche
2016-10-20 17:45 ` Steve Wise
2016-10-20 18:05 ` Bart Van Assche
2016-10-20 18:11 ` Steve Wise
[not found] ` <012601d22afd$5a310460$0e930d20$@opengridcomputing.com>
2016-10-20 19:51 ` Steve Wise
[not found] ` <015201d22b0b$4f526440$edf72cc0$@opengridcomputing.com>
2016-10-20 20:41 ` Steve Wise
2016-10-20 21:08 ` Bart Van Assche
2016-10-20 21:12 ` Steve Wise
[not found] ` <018701d22b16$b4927e20$1db77a60$@opengridcomputing.com>
2016-10-20 21:35 ` Steve Wise
2016-10-18 22:16 ` [PATCH 0/6] Six NVMeOF-related patches Keith Busch
2016-10-20 8:02 ` Sagi Grimberg
2016-10-20 17:38 ` Bart Van Assche
2016-10-21 13:32 ` Christoph Hellwig
2016-10-21 15:08 ` Keith Busch
2016-10-21 21:33 ` Sagi Grimberg
2016-10-25 16:48 ` Sagi Grimberg
2016-10-25 16:48 ` Sagi Grimberg
2016-10-25 16:55 ` Steve Wise
2016-10-25 16:55 ` Steve Wise
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00bf01d22adf$43370ac0$c9a52040$@opengridcomputing.com' \
--to=swise@opengridcomputing.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.