From: Chesnokov Gleb <Chesnokov.G@raidix.com>
To: Sagi Grimberg <sagi@grimberg.me>,
Jason Gunthorpe <jgg@nvidia.com>,
"lanevdenoche@gmail.com" <lanevdenoche@gmail.com>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"dledford@redhat.com" <dledford@redhat.com>
Subject: Re: [PATCH 1/1] iser-target: Fix handling of RDMA_CV_EVENT_ADDR_CHANGE
Date: Mon, 19 Jul 2021 20:47:31 +0000 [thread overview]
Message-ID: <1a74041f62f3489b814ce88f8f7f3d73@raidix.com> (raw)
In-Reply-To: <0e6e8da9-5d14-92ef-39d9-99d7a0792f62@grimberg.me>
> (I also have some vague memory that some bonding events mapped to this
> cma event although the address was still available but that was a long
> time ago so I'm not sure, and the change log says nothing about it...)
The test case where I reproduced the problem with processing RDMA_CM_EVENT_ADDR_CHANGE
is the disconnection of the active link from bonding under load (through pull out the cable).
With my patch, the bug is not reproduced, the load is not interrupted.
Best regards,
Chesnokov Gleb
next prev parent reply other threads:[~2021-07-19 23:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 18:26 [PATCH 1/1] iser-target: Fix handling of RDMA_CV_EVENT_ADDR_CHANGE lanevdenoche
2021-07-18 8:50 ` Leon Romanovsky
[not found] ` <9e97e113abb64952a22430462310ca83@raidix.com>
2021-07-19 6:40 ` Leon Romanovsky
2021-07-19 12:13 ` Jason Gunthorpe
2021-07-19 16:07 ` Chesnokov Gleb
2021-07-19 17:09 ` Jason Gunthorpe
2021-07-19 18:27 ` Sagi Grimberg
2021-07-19 18:29 ` Sagi Grimberg
2021-07-19 20:47 ` Chesnokov Gleb [this message]
2021-07-22 14:23 ` Jason Gunthorpe
2021-07-22 19:54 ` Sagi Grimberg
2021-07-27 17:37 ` Jason Gunthorpe
2021-08-06 20:14 ` Sagi Grimberg
2021-08-17 8:30 ` Chesnokov Gleb
2021-08-17 21:27 ` Sagi Grimberg
2021-09-01 11:43 ` Chesnokov Gleb
2021-09-01 11:56 ` Jason Gunthorpe
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=1a74041f62f3489b814ce88f8f7f3d73@raidix.com \
--to=chesnokov.g@raidix.com \
--cc=dledford@redhat.com \
--cc=jgg@nvidia.com \
--cc=lanevdenoche@gmail.com \
--cc=linux-rdma@vger.kernel.org \
--cc=sagi@grimberg.me \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).