[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ffe855d4-982b-25e6-a901-747095364bd0@linux.ibm.com>
Date: Thu, 6 Jan 2022 10:54:02 +0100
From: Karsten Graul <kgraul@...ux.ibm.com>
To: "D. Wythe" <alibuda@...ux.alibaba.com>
Cc: dust.li@...ux.alibaba.com, kuba@...nel.org, davem@...emloft.net,
netdev@...r.kernel.org, linux-s390@...r.kernel.org,
linux-rdma@...r.kernel.org
Subject: Re: [PATCH net-next v2] net/smc: Reduce overflow of smc clcsock
listen queue
On 06/01/2022 04:51, D. Wythe wrote:
>
> One problem for the fallback scenario is that server must actively send decline message to client and wait for the clc proposal message that client may already sent, otherwise the message of SMC handshake may be read by user space application, which will also lead to OOM conditions caused by infinite amount of dangling sockets.
>
> In that case, we have to make restrictions on 'SMC fallback ing', which makes things more complicated.
Thats a good point, I need to think about this ....
Powered by blists - more mailing lists