From: "Theodore Ts'o" <tytso@mit.edu>
To: zhanchengbin <zhanchengbin1@huawei.com>
Cc: linux-ext4@vger.kernel.org, linfeilong <linfeilong@huawei.com>,
liuzhiqiang26@huawei.com
Subject: Re: [bug report] e2fsck: The process is deadlocked
Date: Wed, 9 Nov 2022 10:43:42 -0500 [thread overview]
Message-ID: <Y2vKriGCf+qcOgoT@mit.edu> (raw)
In-Reply-To: <30ac384e-a015-259a-3efc-1c9f3ee1dabb@huawei.com>
On Wed, Nov 09, 2022 at 06:40:31PM +0800, zhanchengbin wrote:
> Hi Tytso,
> The process is deadlocked, and an I/O error occurs when logs
> are replayed. Because in the I/O error handling function, I/O
> is sent again and catch the mutexlock.
What version of e2fsprogs are you using, and do you have a reliable
reproducer?
Thanks,
- Ted
next prev parent reply other threads:[~2022-11-09 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 10:40 [bug report] e2fsck: The process is deadlocked zhanchengbin
2022-11-09 15:43 ` Theodore Ts'o [this message]
2022-11-10 3:39 ` zhanchengbin
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=Y2vKriGCf+qcOgoT@mit.edu \
--to=tytso@mit.edu \
--cc=linfeilong@huawei.com \
--cc=linux-ext4@vger.kernel.org \
--cc=liuzhiqiang26@huawei.com \
--cc=zhanchengbin1@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