Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   "Theodore Ts'o" <tytso@mit.edu>
To:     adilger.kernel@dilger.ca, Xin Yin <yinxin.x@bytedance.com>,
        harshadshirwadkar@gmail.com
Cc:     "Theodore Ts'o" <tytso@mit.edu>, riteshh@linux.ibm.com,
        dan.carpenter@oracle.com, linux-ext4@vger.kernel.org,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] ext4: fix issues when fast commit work with jbd
Date:   Thu, 20 Jan 2022 10:44:08 -0500
Message-Id: <164269344020.116615.10466472564814944952.b4-ty@mit.edu>
In-Reply-To: <20220117093655.35160-1-yinxin.x@bytedance.com>
References: <20220117093655.35160-1-yinxin.x@bytedance.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Mon, 17 Jan 2022 17:36:53 +0800, Xin Yin wrote:
> When test fast commit with xfstests generic/455, some logic issues were
> found. When a full commit is ongonig, the logic of fast commit tracking seems
> not correct. The first patch fix the ineligible commit case , and the
> second patch fix the common fast commit case.
> 
> After testing this patch set with xfstests log and quick group, no
> regressions were found, and the generic/455 can pass now.
> 
> [...]

Applied, thanks!

[1/2] ext4: fast commit may not fallback for ineligible commit
      commit: b4facf2d8a22262f945975d23e29bbfa94ab5d27
[2/2] ext4: fast commit may miss file actions
      commit: 4a404adb1978f0a3f2ec9ee6c257bcc5b2452ee3

Best regards,
-- 
Theodore Ts'o <tytso@mit.edu>