msg/async/rdma: use wr_id address to check valid chunk

[rosinL]

CQE's wr_id could be:
1)BEACON_WRID
2)&RDMAConnectedSocketImpl::qp
3)Chunks address start from Cluster::chunk_base
When assuming qp as Chunk through CQE's wr_id, it's possible to misjudge
&(qp->ib_physical_port) into Cluster::[base, end) because there're 4 bytes
random data filled in the higher 4 bytes address around ib_pysical_port due
to the address alignement requirement of structure member.
Fix this case by checking whether wr_id value is in the allocated Chunk space.
Fixes: https://tracker.ceph.com/issues/44346

Signed-off-by: Chunsong Feng fengchunsong@huawei.com
Signed-off-by: luo rixin luorixin@huawei.com

Checklist

• References tracker ticket
• Updates documentation if necessary
• Includes tests for new functionality or reproducer for bug

---

Show available Jenkins commands

• jenkins retest this please
• jenkins test classic perf
• jenkins test crimson perf
• jenkins test signed
• jenkins test make check
• jenkins test make check arm64
• jenkins test submodules
• jenkins test dashboard
• jenkins test api
• jenkins test docs
• jenkins render docs
• jenkins test ceph-volume all
• jenkins test ceph-volume tox

[fengchunsong]

@tchaikov @liupengs @changchengx please help to review,thanks

[changchengx]

The function of this PR is right.

Suggestions:
Commit message isn't clear, especially the offsetof(chunk->buffer)'s address map to the Infiniband :: QueuePair address,
What's about the below commit message?

CQE's wr_id could be: 
  1)BEACON_WRID
  2)&RDMAConnectedSocketImpl::qp
  3)Chunks address start from Cluster::chunk_base
When assuming qp as Chunk through CQE's wr_id, it's possible to misjudge
&(qp->ib_physical_port) into Cluster::[base, end) because there're 4 bytes
random data filled in the higher 4 bytes address around ib_pysical_port due 
to the address alignement requirement of structure member.
Fix this case by checking whether wr_id value is in the allocated Chunk space.

[fengchunsong]

The function of this PR is right.

Suggestions:
Commit message isn't clear, especially the offsetof(chunk->buffer)'s address map to the Infiniband :: QueuePair address,
What's about the below commit message?

CQE's wr_id could be: 
  1)BEACON_WRID
  2)&RDMAConnectedSocketImpl::qp
  3)Chunks address start from Cluster::chunk_base
When assuming qp as Chunk through CQE's wr_id, it's possible to misjudge
&(qp->ib_physical_port) into Cluster::[base, end) because there're 4 bytes
random data filled in the higher 4 bytes address around ib_pysical_port due 
to the address alignement requirement of structure member.
Fix this case by checking whether wr_id value is in the allocated Chunk space.

It is a good suggestion. Add the description of the wr_id application scenario and describe the root cause of the problem based on the exception scenario to help readers better understand the patch.Thanks

[fengchunsong]

@changchengx If there is no problem,please help to approve,thanks

[changchengx]

@tchaikov GO
I've confirmed the function is right in this PR.