From: "Theodore Ts'o" <tytso@mit.edu>
To: adilger.kernel@dilger.ca, Kemeng Shi <shikemeng@huaweicloud.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
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: Re: [PATCH v4 0/3] Fix crashes and warnings in ext4 unit test
Date: Wed, 13 Mar 2024 23:54:44 -0400 [thread overview]
Message-ID: <171038847844.855927.13599974785439810131.b4-ty@mit.edu> (raw)
In-Reply-To: <20240304163543.6700-1-shikemeng@huaweicloud.com>
On Tue, 05 Mar 2024 00:35:40 +0800, Kemeng Shi wrote:
> 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.
>
> [...]
Applied, thanks!
[1/3] ext4: alloc test super block from sget
commit: 8ffc0cd24c2a3ea340743db18b1a1e999176fbd3
[2/3] ext4: hold group lock in ext4 kunit test
commit: ad943758e0ebd881d031b657a3f389315bf3a101
[3/3] ext4: initialize sbi->s_freeclusters_counter and sbi->s_dirtyclusters_counter before use in kunit test
commit: 0ecae5410ab526225293d2591ca4632b22c2fd8c
Best regards,
--
Theodore Ts'o <tytso@mit.edu>
prev parent reply other threads:[~2024-03-14 3:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 16:35 [PATCH v4 0/3] Fix crashes and warnings in ext4 unit test Kemeng Shi
2024-03-04 16:35 ` [PATCH v4 1/3] ext4: alloc test super block from sget Kemeng Shi
2024-03-04 18:55 ` Guenter Roeck
2024-03-04 16:35 ` [PATCH v4 2/3] ext4: hold group lock in ext4 kunit test Kemeng Shi
2024-03-04 18:55 ` Guenter Roeck
2024-03-04 16:35 ` [PATCH v4 3/3] ext4: initialize sbi->s_freeclusters_counter and sbi->s_dirtyclusters_counter before use in " Kemeng Shi
2024-03-04 18:55 ` Guenter Roeck
2024-03-04 18:55 ` [PATCH v4 0/3] Fix crashes and warnings in ext4 unit test Guenter Roeck
2024-03-05 7:14 ` Kemeng Shi
2024-03-05 7:32 ` Guenter Roeck
2024-03-14 3:54 ` Theodore Ts'o [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=171038847844.855927.13599974785439810131.b4-ty@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=brauner@kernel.org \
--cc=daniel.diaz@linaro.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=naresh.kamboju@linaro.org \
--cc=shikemeng@huaweicloud.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).