* [PATCH RESEND rdma-next] RDMA/cm: Trace icm_send_rej event before the cm state is reset
@ 2023-03-30 7:23 Mark Zhang
2023-03-30 7:37 ` Leon Romanovsky
2023-04-09 9:53 ` Leon Romanovsky
0 siblings, 2 replies; 4+ messages in thread
From: Mark Zhang @ 2023-03-30 7:23 UTC (permalink / raw)
To: jgg, leonro; +Cc: chuck.lever, linux-rdma, Mark Zhang
Trace icm_send_rej event before the cm state is reset to idle, so that
correct cm state will be logged. For example when an incoming request is
rejected, the old trace log was:
icm_send_rej: local_id=961102742 remote_id=3829151631 state=IDLE reason=REJ_CONSUMER_DEFINED
With this patch:
icm_send_rej: local_id=312971016 remote_id=3778819983 state=MRA_REQ_SENT reason=REJ_CONSUMER_DEFINED
Signed-off-by: Mark Zhang <markzhang@nvidia.com>
Fixes: 8dc105befe16 ("RDMA/cm: Add tracepoints to track MAD send operations")
---
drivers/infiniband/core/cm.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/infiniband/core/cm.c b/drivers/infiniband/core/cm.c
index 603c0aecc361..ff58058aeadc 100644
--- a/drivers/infiniband/core/cm.c
+++ b/drivers/infiniband/core/cm.c
@@ -2912,6 +2912,8 @@ static int cm_send_rej_locked(struct cm_id_private *cm_id_priv,
(ari && ari_length > IB_CM_REJ_ARI_LENGTH))
return -EINVAL;
+ trace_icm_send_rej(&cm_id_priv->id, reason);
+
switch (state) {
case IB_CM_REQ_SENT:
case IB_CM_MRA_REQ_RCVD:
@@ -2942,7 +2944,6 @@ static int cm_send_rej_locked(struct cm_id_private *cm_id_priv,
return -EINVAL;
}
- trace_icm_send_rej(&cm_id_priv->id, reason);
ret = ib_post_send_mad(msg, NULL);
if (ret) {
cm_free_msg(msg);
--
2.37.1
^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH RESEND rdma-next] RDMA/cm: Trace icm_send_rej event before the cm state is reset
2023-03-30 7:23 [PATCH RESEND rdma-next] RDMA/cm: Trace icm_send_rej event before the cm state is reset Mark Zhang
@ 2023-03-30 7:37 ` Leon Romanovsky
2023-03-30 7:39 ` Mark Zhang
2023-04-09 9:53 ` Leon Romanovsky
1 sibling, 1 reply; 4+ messages in thread
From: Leon Romanovsky @ 2023-03-30 7:37 UTC (permalink / raw)
To: Mark Zhang; +Cc: jgg, chuck.lever, linux-rdma
On Thu, Mar 30, 2023 at 10:23:51AM +0300, Mark Zhang wrote:
> Trace icm_send_rej event before the cm state is reset to idle, so that
> correct cm state will be logged. For example when an incoming request is
> rejected, the old trace log was:
> icm_send_rej: local_id=961102742 remote_id=3829151631 state=IDLE reason=REJ_CONSUMER_DEFINED
> With this patch:
> icm_send_rej: local_id=312971016 remote_id=3778819983 state=MRA_REQ_SENT reason=REJ_CONSUMER_DEFINED
>
> Signed-off-by: Mark Zhang <markzhang@nvidia.com>
> Fixes: 8dc105befe16 ("RDMA/cm: Add tracepoints to track MAD send operations")
> ---
> drivers/infiniband/core/cm.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
For future reference:
1. You sent new version, so your patch should have vXXX in subject and not RESEND.
2. Changelog is missing.
3. Signed-off-by should be last.
There is no need to resend this patch, we will fix when we will apply it.
Thanks
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH RESEND rdma-next] RDMA/cm: Trace icm_send_rej event before the cm state is reset
2023-03-30 7:37 ` Leon Romanovsky
@ 2023-03-30 7:39 ` Mark Zhang
0 siblings, 0 replies; 4+ messages in thread
From: Mark Zhang @ 2023-03-30 7:39 UTC (permalink / raw)
To: Leon Romanovsky; +Cc: jgg, chuck.lever, linux-rdma
On 3/30/2023 3:37 PM, Leon Romanovsky wrote:
> On Thu, Mar 30, 2023 at 10:23:51AM +0300, Mark Zhang wrote:
>> Trace icm_send_rej event before the cm state is reset to idle, so that
>> correct cm state will be logged. For example when an incoming request is
>> rejected, the old trace log was:
>> icm_send_rej: local_id=961102742 remote_id=3829151631 state=IDLE reason=REJ_CONSUMER_DEFINED
>> With this patch:
>> icm_send_rej: local_id=312971016 remote_id=3778819983 state=MRA_REQ_SENT reason=REJ_CONSUMER_DEFINED
>>
>> Signed-off-by: Mark Zhang <markzhang@nvidia.com>
>> Fixes: 8dc105befe16 ("RDMA/cm: Add tracepoints to track MAD send operations")
>> ---
>> drivers/infiniband/core/cm.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> For future reference:
> 1. You sent new version, so your patch should have vXXX in subject and not RESEND.
> 2. Changelog is missing.
> 3. Signed-off-by should be last.
>
> There is no need to resend this patch, we will fix when we will apply it.
>
Thank you Leon and sorry for the trouble:)
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH RESEND rdma-next] RDMA/cm: Trace icm_send_rej event before the cm state is reset
2023-03-30 7:23 [PATCH RESEND rdma-next] RDMA/cm: Trace icm_send_rej event before the cm state is reset Mark Zhang
2023-03-30 7:37 ` Leon Romanovsky
@ 2023-04-09 9:53 ` Leon Romanovsky
1 sibling, 0 replies; 4+ messages in thread
From: Leon Romanovsky @ 2023-04-09 9:53 UTC (permalink / raw)
To: Jason Gunthorpe, Leon Romanovsky, Mark Zhang; +Cc: chuck.lever, linux-rdma
On Thu, 30 Mar 2023 10:23:51 +0300, Mark Zhang wrote:
> Trace icm_send_rej event before the cm state is reset to idle, so that
> correct cm state will be logged. For example when an incoming request is
> rejected, the old trace log was:
> icm_send_rej: local_id=961102742 remote_id=3829151631 state=IDLE reason=REJ_CONSUMER_DEFINED
> With this patch:
> icm_send_rej: local_id=312971016 remote_id=3778819983 state=MRA_REQ_SENT reason=REJ_CONSUMER_DEFINED
>
> [...]
Applied, thanks!
[1/1] RDMA/cm: Trace icm_send_rej event before the cm state is reset
https://git.kernel.org/rdma/rdma/c/bd9de1badac7e4
Best regards,
--
Leon Romanovsky <leon@kernel.org>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2023-04-09 9:53 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-03-30 7:23 [PATCH RESEND rdma-next] RDMA/cm: Trace icm_send_rej event before the cm state is reset Mark Zhang
2023-03-30 7:37 ` Leon Romanovsky
2023-03-30 7:39 ` Mark Zhang
2023-04-09 9:53 ` Leon Romanovsky
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.