Received-SPF: pass (google.com: domain of linux-ext4+bounces-1494-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
From: Kemeng Shi <shikemeng@huaweicloud.com>
To: tytso@mit.edu,
	adilger.kernel@dilger.ca
Cc: linux-ext4@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	naresh.kamboju@linaro.org,
	daniel.diaz@linaro.org,
	linux@roeck-us.net,
	brauner@kernel.org
Subject: [PATCH v4 0/3] Fix crashes and warnings in ext4 unit test
Date: Tue,  5 Mar 2024 00:35:40 +0800
Message-Id: <20240304163543.6700-1-shikemeng@huaweicloud.com>
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

v3->v4:
-fix that sbi->s_dirtyclusters_counter is used before
initialization.

v2->v3:
-fix warning that sb->s_umount is still held when unit test finishs
-fix warning that sbi->s_freeclusters_counter is used before
initialization.

v1->v2:
-properly handle error from sget()

Previously, the new mballoc unit tests are only tested by running
"./tools/testing/kunit/kunit.py run ..." in which case only rare configs
are enabled.
This series fixes issues when more debug configs are enabled. Fixes are
tested with and without kunit_tool [1].

[1] https://docs.kernel.org/dev-tools/kunit/run_manual.html

Kemeng Shi (3):
  ext4: alloc test super block from sget
  ext4: hold group lock in ext4 kunit test
  ext4: initialize sbi->s_freeclusters_counter and
    sbi->s_dirtyclusters_counter before use in kunit test

 fs/ext4/mballoc-test.c | 85 +++++++++++++++++++++++++++++++++---------
 1 file changed, 68 insertions(+), 17 deletions(-)

-- 
2.30.0