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:     Jeffle Xu <jefflexu@linux.alibaba.com>, adilger.kernel@dilger.ca
Cc:     "Theodore Ts'o" <tytso@mit.edu>, joseph.qi@linux.alibaba.com,
        linux-ext4@vger.kernel.org, hsiangkao@linux.alibaba.com,
        enwlinux@gmail.com
Subject: Re: [PATCH v2] ext4: fix reserved space counter leakage
Date:   Wed, 15 Sep 2021 23:01:12 -0400
Message-Id: <163176124738.2478144.17001941380733337.b4-ty@mit.edu>
In-Reply-To: <20210823061358.84473-1-jefflexu@linux.alibaba.com>
References: <20210823061358.84473-1-jefflexu@linux.alibaba.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Mon, 23 Aug 2021 14:13:58 +0800, Jeffle Xu wrote:
> When ext4_insert_delayed block receives and recovers from an error from
> ext4_es_insert_delayed_block(), e.g., ENOMEM, it does not release the
> space it has reserved for that block insertion as it should. One effect
> of this bug is that s_dirtyclusters_counter is not decremented and
> remains incorrectly elevated until the file system has been unmounted.
> This can result in premature ENOSPC returns and apparent loss of free
> space.
> 
> [...]

Applied, thanks!

[1/1] ext4: fix reserved space counter leakage
      commit: 8ec5146a46609a89658e5dc9bc40b70ce70ef43b

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