[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9be49a5a-c87d-1630-3ff3-90e6a233d38b@linux.alibaba.com>
Date: Thu, 12 May 2022 11:51:22 +0800
From: Guangguan Wang <guangguan.wang@...ux.alibaba.com>
To: Tony Lu <tonylu@...ux.alibaba.com>
Cc: kgraul@...ux.ibm.com, davem@...emloft.net, kuba@...nel.org,
pabeni@...hat.com, linux-s390@...r.kernel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v2 1/2] net/smc: non blocking recvmsg() return
-EAGAIN when no data and signal_pending
On 2022/5/12 11:43, Tony Lu wrote:
> On Thu, May 12, 2022 at 11:11:55AM +0800, Guangguan Wang wrote:
>> Non blocking sendmsg will return -EAGAIN when any signal pending
>> and no send space left, while non blocking recvmsg return -EINTR
>> when signal pending and no data received. This may makes confused.
>> As TCP returns -EAGAIN in the conditions described above. Align the
>> behavior of smc with TCP.
>>
>> Fixes: 846e344eb722 ("net/smc: add receive timeout check")
>> Signed-off-by: Guangguan Wang <guangguan.wang@...ux.alibaba.com>
>> Reviewed-by: Tony Lu <tonylu@...ux.alibaba.com>
>
> I see that you have already sent this patch to net, so this patch is a
> duplicate. There is no need to send it again to net-next.
>
> Thanks,
> Tony Lu
Ok, just ignore it. Thanks!
Powered by blists - more mailing lists