lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4058292e-aa1f-465b-9bf3-9b674cbb0654@linux.ibm.com>
Date: Mon, 4 Mar 2024 13:35:07 +0100
From: Wenjia Zhang <wenjia@...ux.ibm.com>
To: Dmitry Antipov <dmantipov@...dex.ru>, Jakub Kicinski <kuba@...nel.org>
Cc: Jan Karcher <jaka@...ux.ibm.com>, Wen Gu <guwen@...ux.alibaba.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 04.03.24 11: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'm on the way to answering you. I understand your worry and appreciate 
your sugguestion on the improvement. Since I'm not the original author, 
either, I also need to undestand what was the original intention. i.e. 
Why should the fasync_list of the smc socket be handed over to the clc 
socket? Is there a way to deal with the list prior to the fallback?

AIU, the syzbot's reports on whichever the original fixed or your last 
patch fixed are about the same issue. And both of the fixes seem not to 
solve the problem.  Instead of patches on patches, I'd prefer to find 
the root problem and solve it.

Thus, to the proposed patches from you guys (and back to the question at 
the beginning), if the fasyn_list should be handed over, I like the Wen 
Gu's patch more. Otherwise, I'd like yours more, but as you already 
underlied, it should be done in some other way

Thanks,
Wenjia

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ