From: kernel test robot <lkp@intel.com>
To: Chris von Recklinghausen <crecklin@redhat.com>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, crecklin@redhat.com
Subject: Re: [PATCH] don't record leak information on allocations done between kmemleak_init and kmemleak_late_init
Date: Wed, 3 Jan 2024 11:08:56 +0800 [thread overview]
Message-ID: <202401031015.xJOsS8Nv-lkp@intel.com> (raw)
In-Reply-To: <20240102153428.139984-1-crecklin@redhat.com>
Hi Chris,
kernel test robot noticed the following build errors:
[auto build test ERROR on v6.7-rc8]
[also build test ERROR on linus/master]
[cannot apply to akpm-mm/mm-everything next-20240102]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Chris-von-Recklinghausen/don-t-record-leak-information-on-allocations-done-between-kmemleak_init-and-kmemleak_late_init/20240102-233553
base: v6.7-rc8
patch link: https://lore.kernel.org/r/20240102153428.139984-1-crecklin%40redhat.com
patch subject: [PATCH] don't record leak information on allocations done between kmemleak_init and kmemleak_late_init
config: i386-randconfig-141-20240103 (https://download.01.org/0day-ci/archive/20240103/202401031015.xJOsS8Nv-lkp@intel.com/config)
compiler: ClangBuiltLinux clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240103/202401031015.xJOsS8Nv-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/202401031015.xJOsS8Nv-lkp@intel.com/
All errors (new ones prefixed by >>):
>> mm/kmemleak.c:1194:26: error: use of undeclared identifier 'kmamleak_late_initialized'; did you mean 'kmemleak_late_initialized'?
1194 | if (kmemleak_enabled && kmamleak_late_initialized && ptr &&
| ^~~~~~~~~~~~~~~~~~~~~~~~~
| kmemleak_late_initialized
mm/kmemleak.c:221:12: note: 'kmemleak_late_initialized' declared here
221 | static int kmemleak_late_initialized;
| ^
mm/kmemleak.c:1213:26: error: use of undeclared identifier 'kmamleak_late_initialized'; did you mean 'kmemleak_late_initialized'?
1213 | if (kmemleak_enabled && kmamleak_late_initialized && ptr &&
| ^~~~~~~~~~~~~~~~~~~~~~~~~
| kmemleak_late_initialized
mm/kmemleak.c:221:12: note: 'kmemleak_late_initialized' declared here
221 | static int kmemleak_late_initialized;
| ^
2 errors generated.
vim +1194 mm/kmemleak.c
1182
1183 /**
1184 * kmemleak_not_leak - mark an allocated object as false positive
1185 * @ptr: pointer to beginning of the object
1186 *
1187 * Calling this function on an object will cause the memory block to no longer
1188 * be reported as leak and always be scanned.
1189 */
1190 void __ref kmemleak_not_leak(const void *ptr)
1191 {
1192 pr_debug("%s(0x%px)\n", __func__, ptr);
1193
> 1194 if (kmemleak_enabled && kmamleak_late_initialized && ptr &&
1195 !IS_ERR(ptr))
1196 make_gray_object((unsigned long)ptr);
1197 }
1198 EXPORT_SYMBOL(kmemleak_not_leak);
1199
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-01-03 3:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 15:34 Chris von Recklinghausen
2024-01-02 20:07 ` Catalin Marinas
[not found] ` <5d979584-a168-4594-af19-93af6bc0ae5a@redhat.com>
2024-01-03 12:25 ` Catalin Marinas
2024-01-03 3:08 ` kernel test robot [this message]
2024-01-03 10:51 ` kernel test robot
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=202401031015.xJOsS8Nv-lkp@intel.com \
--to=lkp@intel.com \
--cc=catalin.marinas@arm.com \
--cc=crecklin@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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
all inboxes | Powered by JetHome®