From: Wang Zhaolong <wangzhaolong1@huawei.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: David Howells <dhowells@redhat.com>,
Steve French <smfrench@gmail.com>, <stable@vger.kernel.org>,
<linux-cifs@vger.kernel.org>, yangerkun <yangerkun@huawei.com>,
yi zhang <yi.zhang@huawei.com>,
Paulo Alcantara <pc@manguebit.com>
Subject: Re: [BUG REPORT] cifs: Deadlock due to network reconnection during file writing
Date: Wed, 19 Mar 2025 09:25:43 +0800 [thread overview]
Message-ID: <10823e8a-8569-80e9-cea0-d8d7ac32a54d@huawei.com> (raw)
In-Reply-To: <2025031821-ominous-sappy-18ad@gregkh>
Apologies for the earlier context-less ping 🙏. Here's the
situation:
I have been tracking the latest progress on fixing an issue
involving a deadlock in the CIFS write file process caused by
a network interruption. This problem affects LTS Linux kernel
versions 5.4.y through 6.6.y. The reason it is limited to LTS
versions is that the issue was avoided in the mainline 6.9
version due to the netns-based code restructuring in the CIFS.
In my previous email, I provided the code call flow of the issue,
as well as the invasive method to modify the kernel for reproduction.
If there is anything else I can provide to help move this
forward, please let me know.
Thank you for your time and support!
Best regards,
Wang Zhaolong
> On Tue, Mar 18, 2025 at 09:50:25PM +0800, Wang Zhaolong wrote:
>> Friendly ping.
>
> Empty pings with no context are not good :(
prev parent reply other threads:[~2025-03-19 1:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-26 7:36 [BUG REPORT] cifs: Deadlock due to network reconnection during file writing Wang Zhaolong
2025-02-07 1:08 ` Wang Zhaolong
2025-02-07 1:30 ` Steve French
2025-02-10 13:05 ` David Howells
2025-02-18 1:05 ` Wang Zhaolong
2025-03-18 13:50 ` Wang Zhaolong
2025-03-18 14:37 ` Greg KH
2025-03-19 1:25 ` Wang Zhaolong [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=10823e8a-8569-80e9-cea0-d8d7ac32a54d@huawei.com \
--to=wangzhaolong1@huawei.com \
--cc=dhowells@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-cifs@vger.kernel.org \
--cc=pc@manguebit.com \
--cc=smfrench@gmail.com \
--cc=stable@vger.kernel.org \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.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