[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cff8e035-b70a-4910-9af6-e62000c0b87e@linux.alibaba.com>
Date: Mon, 4 Mar 2024 18:51:26 +0800
From: Wen Gu <guwen@...ux.alibaba.com>
To: Dmitry Antipov <dmantipov@...dex.ru>, Jakub Kicinski <kuba@...nel.org>
Cc: Wenjia Zhang <wenjia@...ux.ibm.com>, Jan Karcher <jaka@...ux.ibm.com>,
"D. Wythe" <alibuda@...ux.alibaba.com>, linux-s390@...r.kernel.org,
netdev@...r.kernel.org, lvc-project@...uxtesting.org
Subject: Re: Reaching official SMC maintainers
On 2024/3/4 18:31, Dmitry Antipov wrote:
> Jakub,
>
> could you please check whether an official maintainers of net/smc are
> actually active? I'm interesting just because there was no feedback on
> [1]. After all, it's still a kernel memory leak, and IMO should not be
> silently ignored by the maintainers (if any).
>
> Thanks,
> Dmitry
>
> [1] https://lore.kernel.org/netdev/20240221051608.43241-1-dmantipov@yandex.ru/
Hi, Dmitry, I think I have given my feedback about this, see:
https://lore.kernel.org/netdev/819353f3-f5f9-4a15-96a1-4f3a7fd6b33e@linux.alibaba.com/
https://lore.kernel.org/netdev/19d7d71b-c911-45cc-9671-235d98720be6@linux.alibaba.com/
IMHO, if we want to address the problem of fasync_struct entries being
incorrectly inserted to old socket, we may have to change the general code.
Thanks.
Powered by blists - more mailing lists