All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: Ye Bin <yebin@huaweicloud.com>,
Cc: jack@suse.cz, tytso@mit.edu, adilger.kernel@dilger.ca,
	linux-ext4@vger.kernel.org
Subject: Re: [PATCH v3 0/5] Fix some issues about ext4-test
Date: Sat, 14 Mar 2026 17:34:24 +0530	[thread overview]
Message-ID: <ldfuty5z.ritesh.list@gmail.com> (raw)
In-Reply-To: <20260314074903.1314851-1-yebin@huaweicloud.com>

Ye Bin <yebin@huaweicloud.com> writes:

> From: Ye Bin <yebin10@huawei.com>
>
> Diff v3 vs v2:
> 1. Remove three patches from this patchset:
>   ext4: fix mballoc-test.c is not compiled when EXT4_KUNIT_TESTS=M
>   ext4: introduce EXPORT_SYMBOL_FOR_EXT4_TEST() helper
>   ext4: fix extents-test.c is not compiled when EXT4_KUNIT_TESTS=M
> 2. Fix 'sbi' leak as no "sbi->s_sb->s_op->put_super()" registered.
>

...and that this patch series is based on top of [1]
[1]: https://lore.kernel.org/linux-ext4/5bb9041471dab8ce870c191c19cbe4df57473be8.1772381213.git.ritesh.list@gmail.com/

I think you also missed to take few RBs from previous version. But never
mind, thanks for sending the fixes :)

-ritesh

> Diff v2 vs v1:
> 1. Fix compile warning when disable EXT4_KUNIT_TESTS for patch[1][3];
> 2. Remove reviewed-by tag for patch[1];
>
> Patch [1]-[2]:
> Decoupled mballoc-test and extents-test from ext4. Patch [1] does not
> have any changes compared to the previously released version, so the
> reviewed-by is added.
> Patch [3-7]:
> Bugfix for extents-test.c.
> Patch [8]:
> Bugfix for mballoc-test.c.
>
> Ye Bin (5):
>   ext4: call deactivate_super() in extents_kunit_exit()
>   ext4: fix miss unlock 'sb->s_umount' in extents_kunit_init()
>   ext4: fix the error handling process in extents_kunit_init).
>   ext4: fix possible null-ptr-deref in extents_kunit_exit()
>   ext4: fix possible null-ptr-deref in mbt_kunit_exit()
>
>  fs/ext4/extents-test.c | 54 +++++++++++++++++++++++++++++++-----------
>  fs/ext4/mballoc-test.c |  6 ++++-
>  2 files changed, 45 insertions(+), 15 deletions(-)
>
> -- 
> 2.34.1

      parent reply	other threads:[~2026-03-14 12:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-14  7:48 [PATCH v3 0/5] Fix some issues about ext4-test Ye Bin
2026-03-14  7:48 ` [PATCH v3 1/5] ext4: call deactivate_super() in extents_kunit_exit() Ye Bin
2026-03-14 12:19   ` Ritesh Harjani
2026-03-15  5:39   ` Ojaswin Mujoo
2026-03-18  2:21     ` yebin (H)
2026-03-14  7:49 ` [PATCH v3 2/5] ext4: fix miss unlock 'sb->s_umount' in extents_kunit_init() Ye Bin
2026-03-14 12:21   ` Ritesh Harjani
2026-03-15  5:40   ` Ojaswin Mujoo
2026-03-14  7:49 ` [PATCH v3 3/5] ext4: fix the error handling process in extents_kunit_init) Ye Bin
2026-03-14 12:29   ` Ritesh Harjani
2026-03-16  1:36     ` yebin (H)
2026-03-15  6:12   ` Ojaswin Mujoo
2026-03-14  7:49 ` [PATCH v3 4/5] ext4: fix possible null-ptr-deref in extents_kunit_exit() Ye Bin
2026-03-14 12:35   ` Ritesh Harjani
2026-03-15  6:13   ` Ojaswin Mujoo
2026-03-14  7:49 ` [PATCH v3 5/5] ext4: fix possible null-ptr-deref in mbt_kunit_exit() Ye Bin
2026-03-14 12:36   ` Ritesh Harjani
2026-03-15  6:23   ` Ojaswin Mujoo
2026-03-14 12:04 ` Ritesh Harjani [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=ldfuty5z.ritesh.list@gmail.com \
    --to=ritesh.list@gmail.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=yebin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.