[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <64c2d755-eb4b-42fa-befb-c4afd7e95f03@linux.ibm.com>
Date: Wed, 14 Aug 2024 15:21:58 +0200
From: Alexandra Winter <wintera@...ux.ibm.com>
To: "D. Wythe" <alibuda@...ux.alibaba.com>,
Jeongjun Park <aha310510@...il.com>, wenjia@...ux.ibm.com,
jaka@...ux.ibm.com, tonylu@...ux.alibaba.com, guwen@...ux.alibaba.com,
gbayer@...ux.ibm.com
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, dust.li@...ux.alibaba.com,
linux-s390@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net,v4] net/smc: prevent NULL pointer dereference in
txopt_get
On 14.08.24 15:11, D. Wythe wrote:
> struct smc_sock { /* smc sock container */
> - struct sock sk;
> + union {
> + struct sock sk;
> + struct inet_sock inet;
> + };
I don't see a path where this breaks, but it looks risky to me.
Is an smc_sock always an inet_sock as well? Then can't you go with smc_sock->inet_sock->sk ?
Or only in the IPPROTO SMC case, and in the AF_SMC case it is not an inet_sock?
Powered by blists - more mailing lists