From: kernel test robot <lkp@intel.com>
To: Ye Bin <yebin@huaweicloud.com>,
tytso@mit.edu, adilger.kernel@dilger.ca,
linux-ext4@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, jack@suse.cz
Subject: Re: [PATCH -next 3/8] ext4: fix extents-test.c is not compiled when EXT4_KUNIT_TESTS=M
Date: Wed, 11 Mar 2026 14:32:12 +0800 [thread overview]
Message-ID: <202603111416.j2HqVIhj-lkp@intel.com> (raw)
In-Reply-To: <20260310130412.3156753-4-yebin@huaweicloud.com>
Hi Ye,
kernel test robot noticed the following build warnings:
[auto build test WARNING on next-20260309]
url: https://github.com/intel-lab-lkp/linux/commits/Ye-Bin/ext4-fix-mballoc-test-c-is-not-compiled-when-EXT4_KUNIT_TESTS-M/20260310-225016
base: next-20260309
patch link: https://lore.kernel.org/r/20260310130412.3156753-4-yebin%40huaweicloud.com
patch subject: [PATCH -next 3/8] ext4: fix extents-test.c is not compiled when EXT4_KUNIT_TESTS=M
config: sh-defconfig (https://download.01.org/0day-ci/archive/20260311/202603111416.j2HqVIhj-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260311/202603111416.j2HqVIhj-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202603111416.j2HqVIhj-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> fs/ext4/extents.c:187:5: warning: no previous prototype for '__ext4_ext_dirty' [-Wmissing-prototypes]
187 | int __ext4_ext_dirty(const char *where, unsigned int line,
| ^~~~~~~~~~~~~~~~
>> fs/ext4/extents.c:3147:5: warning: no previous prototype for 'ext4_ext_zeroout' [-Wmissing-prototypes]
3147 | int ext4_ext_zeroout(struct inode *inode, struct ext4_extent *ex)
| ^~~~~~~~~~~~~~~~
vim +/__ext4_ext_dirty +187 fs/ext4/extents.c
180
181 /*
182 * could return:
183 * - EROFS
184 * - ENOMEM
185 * - EIO
186 */
> 187 int __ext4_ext_dirty(const char *where, unsigned int line,
188 handle_t *handle, struct inode *inode,
189 struct ext4_ext_path *path)
190 {
191 int err;
192
193 KUNIT_STATIC_STUB_REDIRECT(__ext4_ext_dirty, where, line, handle, inode,
194 path);
195
196 WARN_ON(!rwsem_is_locked(&EXT4_I(inode)->i_data_sem));
197 if (path->p_bh) {
198 ext4_extent_block_csum_set(inode, ext_block_hdr(path->p_bh));
199 /* path points to block */
200 err = __ext4_handle_dirty_metadata(where, line, handle,
201 inode, path->p_bh);
202 /* Extents updating done, re-set verified flag */
203 if (!err)
204 set_buffer_verified(path->p_bh);
205 } else {
206 /* path points to leaf/index in inode body */
207 err = ext4_mark_inode_dirty(handle, inode);
208 }
209 return err;
210 }
211
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-03-11 6:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 13:04 [PATCH -next 0/8] Fix some issues about ext4-test Ye Bin
2026-03-10 13:04 ` [PATCH -next 1/8] ext4: fix mballoc-test.c is not compiled when EXT4_KUNIT_TESTS=M Ye Bin
2026-03-11 2:44 ` kernel test robot
2026-03-11 3:26 ` kernel test robot
2026-03-10 13:04 ` [PATCH -next 2/8] ext4: introduce EXPORT_SYMBOL_FOR_EXT4_TEST() helper Ye Bin
2026-03-10 13:04 ` [PATCH -next 3/8] ext4: fix extents-test.c is not compiled when EXT4_KUNIT_TESTS=M Ye Bin
2026-03-11 6:32 ` kernel test robot [this message]
2026-03-10 13:04 ` [PATCH -next 4/8] ext4: fix miss unlock 'sb->s_umount' in extents_kunit_init() Ye Bin
2026-03-13 11:32 ` Ritesh Harjani
2026-03-10 13:04 ` [PATCH -next 5/8] ext4: fix miss free super_block in extents_kunit_exit() Ye Bin
2026-03-13 12:03 ` Ritesh Harjani
2026-03-13 14:03 ` Ojaswin Mujoo
2026-03-10 13:04 ` [PATCH -next 6/8] ext4: fix the error handling process in extents_kunit_init) Ye Bin
2026-03-13 12:15 ` Ritesh Harjani
2026-03-14 2:21 ` yebin (H)
2026-03-10 13:04 ` [PATCH -next 7/8] ext4: fix possible null-ptr-deref in extents_kunit_exit() Ye Bin
2026-03-13 12:27 ` Ritesh Harjani
2026-03-10 13:04 ` [PATCH -next 8/8] ext4: fix possible null-ptr-deref in mbt_kunit_exit() Ye Bin
2026-03-13 12:33 ` Ritesh Harjani
2026-03-13 7:16 ` [PATCH -next 0/8] Fix some issues about ext4-test Ojaswin Mujoo
2026-03-13 10:34 ` 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=202603111416.j2HqVIhj-lkp@intel.com \
--to=lkp@intel.com \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--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