Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:3 as permitted sender) client-ip=2620:137:e000::3:3;
From:   "Theodore Ts'o" <tytso@mit.edu>
To:     adilger.kernel@dilger.ca, yi.zhang@huawei.com, djwong@kernel.org,
        zhangshida <starzhangzsd@gmail.com>
Cc:     "Theodore Ts'o" <tytso@mit.edu>, linux-ext4@vger.kernel.org,
        linux-kernel@vger.kernel.org, zhangshida@kylinos.cn,
        stable@kernel.org, Andreas Dilger <adilger@dilger.ca>
Subject: Re: [PATCH v4] ext4: Fix rec_len verify error
Date:   Fri, 15 Sep 2023 11:06:19 -0400
Message-Id: <169479037020.1500633.4914927617396834377.b4-ty@mit.edu>
In-Reply-To: <20230803060938.1929759-1-zhangshida@kylinos.cn>
References: <20230803060938.1929759-1-zhangshida@kylinos.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk


On Thu, 03 Aug 2023 14:09:38 +0800, zhangshida wrote:
> With the configuration PAGE_SIZE 64k and filesystem blocksize 64k,
> a problem occurred when more than 13 million files were directly created
> under a directory:
> 
> EXT4-fs error (device xx): ext4_dx_csum_set:492: inode #xxxx: comm xxxxx: dir seems corrupt?  Run e2fsck -D.
> EXT4-fs error (device xx): ext4_dx_csum_verify:463: inode #xxxx: comm xxxxx: dir seems corrupt?  Run e2fsck -D.
> EXT4-fs error (device xx): dx_probe:856: inode #xxxx: block 8188: comm xxxxx: Directory index failed checksum
> 
> [...]

Applied, thanks!

[1/1] ext4: Fix rec_len verify error
      (no commit info)

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