From: "yebin (H)" <yebin10@huawei.com>
To: Ojaswin Mujoo <ojaswin@linux.ibm.com>, Ye Bin <yebin@huaweicloud.com>
Cc: <tytso@mit.edu>, <adilger.kernel@dilger.ca>,
<linux-ext4@vger.kernel.org>, <jack@suse.cz>
Subject: Re: [PATCH v3] ext4: fix mballoc-test.c is not compiled when EXT4_KUNIT_TESTS=M
Date: Sat, 7 Mar 2026 08:02:53 +0800 [thread overview]
Message-ID: <69AB6B2D.6070006@huawei.com> (raw)
In-Reply-To: <aaqkoSTFyYzxxYRI@li-dc0c254c-257c-11b2-a85c-98b6c1322444.ibm.com>
On 2026/3/6 17:55, Ojaswin Mujoo wrote:
> On Fri, Feb 27, 2026 at 02:55:14PM +0800, Ye Bin wrote:
>> From: Ye Bin <yebin10@huawei.com>
>>
>> Now, only EXT4_KUNIT_TESTS=Y testcase will be compiled in 'mballoc.c'.
>> To solve this issue, the ext4 test code needs to be decoupled. The ext4
>> test module is compiled into a separate module.
>>
>> Reported-by: ChenXiaoSong <chenxiaosong@kylinos.cn>
>> Closes: https://patchwork.kernel.org/project/cifs-client/patch/20260118091313.1988168-2-chenxiaosong.chenxiaosong@linux.dev/
>> Fixes: 7c9fa399a369 ("ext4: add first unit test for ext4_mb_new_blocks_simple in mballoc")
>> Signed-off-by: Ye Bin <yebin10@huawei.com>
>
> Hi Ye,
>
>>From my testing I can see that EXPORT_SYMBOL_FOR_MODULE() doesn't
> resepect the namespace restriction if EXT4_KUNIT_TESTS=y but I think
> that should be okay.
>
> The patch otherwise looks good. Feel free to add:
>
> Reviewed-by: Ojaswin Mujoo <ojaswin@linux.ibm.com>
>
> One thing, recently added extents-test.c is also having the same issue where
> it doesn't work when compiled as module. Would you be willing to fix it
> as well?
>
No problem, I will fix this issue.
> Regards,
> ojaswin
>
>
>
> .
>
next prev parent reply other threads:[~2026-03-07 0:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 6:55 [PATCH v3] ext4: fix mballoc-test.c is not compiled when EXT4_KUNIT_TESTS=M Ye Bin
2026-02-27 15:53 ` Jan Kara
2026-03-06 9:55 ` Ojaswin Mujoo
2026-03-07 0:02 ` yebin (H) [this message]
2026-03-07 6:25 ` Ojaswin Mujoo
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=69AB6B2D.6070006@huawei.com \
--to=yebin10@huawei.com \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox