[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241209214449.0bb5afce.pasic@linux.ibm.com>
Date: Mon, 9 Dec 2024 21:44:49 +0100
From: Halil Pasic <pasic@...ux.ibm.com>
To: Guangguan Wang <guangguan.wang@...ux.alibaba.com>
Cc: Wenjia Zhang <wenjia@...ux.ibm.com>, jaka@...ux.ibm.com,
alibuda@...ux.alibaba.com, tonylu@...ux.alibaba.com,
guwen@...ux.alibaba.com, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, horms@...nel.org,
linux-rdma@...r.kernel.org, linux-s390@...r.kernel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
Dust Li
<dust.li@...ux.alibaba.com>,
Halil Pasic <pasic@...ux.ibm.com>
Subject: Re: [PATCH net-next v2 2/2] net/smc: support ipv4 mapped ipv6 addr
client for smc-r v2
On Mon, 9 Dec 2024 20:36:45 +0800
Guangguan Wang <guangguan.wang@...ux.alibaba.com> wrote:
> > I believe we would like to have a v3 here. Also I'm not sure
> > checking on saddr is sufficient, but I didn't do my research on
> > that question yet.
> >
> > Regards,
> > Halil
>
> Did you mean to research whether the daddr should be checked too?
Right! Or is it implied that if saddr is a ipv4 mapped ipv6 addr
then the daddr must be ipv4 mapped ipv6 addr as well?
Regards,
Halil
Powered by blists - more mailing lists