From:   "Theodore Ts'o" <tytso@mit.edu>
To:     harshadshirwadkar@gmail.com, adilger.kernel@dilger.ca,
        Xin Yin <yinxin.x@bytedance.com>
Cc:     "Theodore Ts'o" <tytso@mit.edu>, linux-kernel@vger.kernel.org,
        linux-ext4@vger.kernel.org
Subject: Re: [PATCH v2] ext4: fix fast commit may miss tracking range for FALLOC_FL_ZERO_RANGE
Date:   Thu, 23 Dec 2021 19:27:51 -0500
Message-Id: <164030564165.2940033.13491679644853079214.b4-ty@mit.edu>
In-Reply-To: <20211221022839.374606-1-yinxin.x@bytedance.com>
References: <20211221022839.374606-1-yinxin.x@bytedance.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Tue, 21 Dec 2021 10:28:39 +0800, Xin Yin wrote:
> when call falloc with FALLOC_FL_ZERO_RANGE, to set an range to unwritten,
> which has been already initialized. If the range is align to blocksize,
> fast commit will not track range for this change.
> 
> Also track range for unwritten range in ext4_map_blocks().
> 
> 
> [...]

Applied, thanks!

[1/1] ext4: fix fast commit may miss tracking range for FALLOC_FL_ZERO_RANGE
      commit: f6c90a2bcabcfc56d91aa5091b76ce8082de7d68

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