public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Wenjia Zhang <wenjia@linux.ibm.com>
To: Wen Gu <guwen@linux.alibaba.com>,
	jaka@linux.ibm.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com
Cc: alibuda@linux.alibaba.com, tonylu@linux.alibaba.com,
	linux-s390@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net/smc: use new helper to get the netdev associated to an ibdev
Date: Thu, 24 Oct 2024 12:00:38 +0200	[thread overview]
Message-ID: <61cf578f-020e-4e0d-a551-98df5367ee27@linux.ibm.com> (raw)
In-Reply-To: <20241024054456.37124-1-guwen@linux.alibaba.com>



On 24.10.24 07:44, Wen Gu wrote:
> Patch [1] provides common interfaces to store and get net devices
> associated to an IB device port and removes the ops->get_netdev()
> callback of mlx5 driver. So use the new interface in smc.
> 
> [1]: 8d159eb2117b ("RDMA/mlx5: Use IB set_netdev and get_netdev functions")
> 
> Reported-by: D. Wythe <alibuda@linux.alibaba.com>
> Signed-off-by: Wen Gu <guwen@linux.alibaba.com>
> ---
[...]

We detected the problem as well, and I already sent a patch with the 
same code change in our team internally these. Because some agreement 
issues on the commit message, it is still not sent out externally. Now 
we (our team) have almost an agreement, I'd like to attach it here. 
Please have a look if it is also for you to use:

"
[PATCH net] net/smc: Fix lookup of netdev by using ib_device_get_netdev()

Since/Although commit c2261dd76b54 ("RDMA/device: Add 
ib_device_set_netdev() as an alternative to get_netdev") introduced an 
API ib_device_get_netdev, the SMC-R variant of the SMC protocol 
continued to use the old API ib_device_ops.get_netdev() to lookup 
netdev. As commit 8d159eb2117b ("RDMA/mlx5: Use IB set_netdev and 
get_netdev functions") removed the get_netdev callback from 
mlx5_ib_dev_common_roce_ops, calling ib_device_ops.get_netdev didn't 
work any more at least by using a mlx5 device driver. Thus, using 
ib_device_set_netdev() now became mandatory.

Replace ib_device_ops.get_netdev() with ib_device_get_netdev().

Fixes: 54903572c23c ("net/smc: allow pnetid-less configuration")
Fixes: 8d159eb2117b ("RDMA/mlx5: Use IB set_netdev and get_netdev 
functions")
"
My main points are:
- This patch should go to net, not net-next. Because it can result in 
malfunction. e.g. if the RoCE devices are used as both handshake device 
and RDMA device without any PNET_ID, it would be failed to find SMC-R 
device, then fallback.
- We need the both fixes, which would help us for the backport


Thanks,
Wenjia


  reply	other threads:[~2024-10-24 10:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-24  5:44 [PATCH net-next] net/smc: use new helper to get the netdev associated to an ibdev Wen Gu
2024-10-24 10:00 ` Wenjia Zhang [this message]
2024-10-24 11:06   ` Wen Gu
2024-10-24 11:31     ` Wenjia Zhang

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=61cf578f-020e-4e0d-a551-98df5367ee27@linux.ibm.com \
    --to=wenjia@linux.ibm.com \
    --cc=alibuda@linux.alibaba.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=guwen@linux.alibaba.com \
    --cc=jaka@linux.ibm.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=tonylu@linux.alibaba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox