From: "Theodore Ts'o" <tytso@mit.edu>
To: Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org, Wenchao Hao <haowenchao2@huawei.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>, louhongxiang@huawei.com
Subject: Re: [PATCH] debugfs: Fix infinite loop when dump log
Date: Wed, 17 Apr 2024 00:33:41 -0400 [thread overview]
Message-ID: <171332777784.2749069.11433721296273612273.b4-ty@mit.edu> (raw)
In-Reply-To: <20231117102315.2431846-1-haowenchao2@huawei.com>
On Fri, 17 Nov 2023 18:23:15 +0800, Wenchao Hao wrote:
> There are 2 scenarios which would trigger infinite loop:
>
> 1. None log is recorded, then dumplog with "-n", for example:
> debugfs -R "logdump -O -n 10" /dev/xxx
> while /dev/xxx has no valid log recorded.
> 2. The log area is full and cycle write is triggered, then dumplog with
> debugfs -R "logdump -aOS" /dev/xxx
>
> [...]
Applied, thanks!
[1/1] debugfs: Fix infinite loop when dump log
commit: 272173a300822b5cfe19bef597609523baab0c66
(I renamed reverse_flag to wrapped_flag to make things clearer.)
Best regards,
--
Theodore Ts'o <tytso@mit.edu>
prev parent reply other threads:[~2024-04-17 4:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 10:23 [PATCH] debugfs: Fix infinite loop when dump log Wenchao Hao
2023-11-27 6:54 ` Wenchao Hao
2024-04-17 4:33 ` Theodore Ts'o [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=171332777784.2749069.11433721296273612273.b4-ty@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=haowenchao2@huawei.com \
--cc=linux-ext4@vger.kernel.org \
--cc=louhongxiang@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).