From: Wenjia Zhang <wenjia@linux.ibm.com>
To: Dmitry Antipov <dmantipov@yandex.ru>, Jakub Kicinski <kuba@kernel.org>
Cc: Jan Karcher <jaka@linux.ibm.com>,
Wen Gu <guwen@linux.alibaba.com>,
"D. Wythe" <alibuda@linux.alibaba.com>,
linux-s390@vger.kernel.org, netdev@vger.kernel.org,
lvc-project@linuxtesting.org
Subject: Re: Reaching official SMC maintainers
Date: Mon, 4 Mar 2024 13:35:07 +0100 [thread overview]
Message-ID: <4058292e-aa1f-465b-9bf3-9b674cbb0654@linux.ibm.com> (raw)
In-Reply-To: <dacadaef-4fec-4d5e-8b91-1a292ab43b37@yandex.ru>
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
prev parent reply other threads:[~2024-03-04 12:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 10:31 Reaching official SMC maintainers Dmitry Antipov
2024-03-04 10:51 ` Wen Gu
2024-03-05 16:39 ` Dmitry Antipov
2024-03-06 10:36 ` Jan Karcher
2024-03-04 12:35 ` Wenjia Zhang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4058292e-aa1f-465b-9bf3-9b674cbb0654@linux.ibm.com \
--to=wenjia@linux.ibm.com \
--cc=alibuda@linux.alibaba.com \
--cc=dmantipov@yandex.ru \
--cc=guwen@linux.alibaba.com \
--cc=jaka@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).