From: Leon Romanovsky <leon@kernel.org>
To: Parav Pandit <parav@nvidia.com>
Cc: Etienne AUJAMES <eaujames@ddn.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Romain Fihue <romain.fihue@cea.fr>,
Gael Delbary <gdelbary@ddn.com>
Subject: Re: [PATCH] IB/cache: update gid cache on client reregister event
Date: Sun, 4 Jan 2026 16:37:16 +0200 [thread overview]
Message-ID: <20260104143716.GD27868@unreal> (raw)
In-Reply-To: <SJ0PR12MB680626630DE34A9FDA4DE8C2DCB8A@SJ0PR12MB6806.namprd12.prod.outlook.com>
On Sat, Jan 03, 2026 at 02:11:49PM +0000, Parav Pandit wrote:
>
> > From: Etienne AUJAMES <eaujames@ddn.com>
> > Sent: 31 December 2025 06:38 PM
> >
> > Some HCAs (e.g: ConnectX4) do not trigger a IB_EVENT_GID_CHANGE on
> > subnet prefix update from SM (PortInfo).
> >
> > Since the d58c23c92548, the GID cache is updated exclusively on
> > IB_EVENT_GID_CHANGE. If this event is not emitted, the subnet prefix
> > in the IPoIB interface’s hardware address remains set to its default
> > value (0xfe80000000000000).
> > Then rdma_bind_addr() failed because it relies on hardware address to
> > find the port GID (subnet_prefix + port GUID).
> >
> Commit message should be referenced as d58c23c92548 ("IB/core: Only update PKEY and GID caches onrespective events").
> (instead of just above commit id).
> Please change the reference to full.
I fixed it and applied.
Thanks
next prev parent reply other threads:[~2026-01-04 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 13:07 [PATCH] IB/cache: update gid cache on client reregister event Etienne AUJAMES
2026-01-03 14:11 ` Parav Pandit
2026-01-04 14:37 ` Leon Romanovsky [this message]
2026-01-04 14:24 ` Leon Romanovsky
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=20260104143716.GD27868@unreal \
--to=leon@kernel.org \
--cc=eaujames@ddn.com \
--cc=gdelbary@ddn.com \
--cc=linux-rdma@vger.kernel.org \
--cc=parav@nvidia.com \
--cc=romain.fihue@cea.fr \
/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