From: Wang Zhaolong <wangzhaolong1@huawei.com>
To: Steve French <smfrench@gmail.com>, Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: <bharathsm@microsoft.com>, <ematsumiya@suse.de>,
<kuni1840@gmail.com>, <linux-cifs@vger.kernel.org>,
<pc@manguebit.com>, <samba-technical@lists.samba.org>,
<sprasad@microsoft.com>, <tom@talpey.com>,
<linux-net@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] cifs: Revert bogus fix for CVE-2024-54680 and its followup commit.
Date: Thu, 3 Apr 2025 18:14:19 +0800 [thread overview]
Message-ID: <0520d98d-8289-4cd8-bf37-57bf00750e63@huawei.com> (raw)
In-Reply-To: <CAH2r5mu7Wf0n9ZmnhAAWetKRiUczHv+odYHj5bBg6a=G1y2kcQ@mail.gmail.com>
> For a complex issue like this it is important to have at least some
> Tested-by or Reviewed-by for these two, because I was having trouble
> reproducing the various reported problems on Ubuntu (or our Fedora
> test VMs), and the refcount issues are more complicated they seem.
> Let me know if anyone has reviewed these two patches or tested them.
>
Hi Steve,
I can confirm these issues on my test environment. I'm currently using
Debian Testing (Trixie) for my development work. I've also observed the
unexpected phenomenon on Ubuntu 16.04 LTS when running the test cases.
I suspect the difficulty in reproducing might be related to rootfs image
versions - particularly with older distros like Ubuntu 16.04, as the
test case involves numerous dependent packages.
The issue of net_ns reference count leakage is not fully resolved yet.
Based on that use case, the net_ns count leakage problem can still be
constructed by adding various network faults.
I'm currently modernizing my development environment and working on
automating it. In the future, I will try to provide more comprehensive
reproduction steps when reporting problems, including detailed
instructions for setting up the environment.
Best regards,
Wang Zhaolong
next prev parent reply other threads:[~2025-04-03 10:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 20:02 [PATCH 0/2] cifs: Revert bogus fix for CVE-2024-54680 and its followup commit Kuniyuki Iwashima
2025-04-02 20:02 ` [PATCH 1/2] Revert "smb: client: Fix netns refcount imbalance causing leaks and use-after-free" Kuniyuki Iwashima
2025-04-03 3:16 ` Wang Zhaolong
2025-04-03 9:59 ` Wang Zhaolong
2025-04-03 17:26 ` Kuniyuki Iwashima
2025-04-03 17:32 ` Steve French
2025-04-03 17:46 ` Kuniyuki Iwashima
2025-04-02 20:02 ` [PATCH 2/2] Revert "smb: client: fix TCP timers deadlock after rmmod" Kuniyuki Iwashima
2025-04-03 3:12 ` Wang Zhaolong
2025-04-03 1:14 ` [PATCH 0/2] cifs: Revert bogus fix for CVE-2024-54680 and its followup commit Steve French
2025-04-03 2:18 ` Kuniyuki Iwashima
2025-04-03 3:19 ` Steve French
2025-04-03 10:14 ` Wang Zhaolong [this message]
2025-04-11 7:04 ` Kuniyuki Iwashima
2025-04-12 17:28 ` Steve French
2025-04-12 19:10 ` Kuniyuki Iwashima
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=0520d98d-8289-4cd8-bf37-57bf00750e63@huawei.com \
--to=wangzhaolong1@huawei.com \
--cc=bharathsm@microsoft.com \
--cc=ematsumiya@suse.de \
--cc=kuni1840@gmail.com \
--cc=kuniyu@amazon.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=pc@manguebit.com \
--cc=samba-technical@lists.samba.org \
--cc=smfrench@gmail.com \
--cc=sprasad@microsoft.com \
--cc=tom@talpey.com \
/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