From: kernel test robot <lkp@intel.com>
To: Fangzheng Zhang <fangzheng.zhang@unisoc.com>,
Christoph Lameter <cl@linux-foundation.org>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
Roman Gushchin <roman.gushchin@linux.dev>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>, Greg KH <greg@kroah.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
linux-kernel@vger.kernel.org, tkjos@google.com,
Fangzheng Zhang <fangzheng.zhang@unisoc.com>,
Yuming Han <yuming.han@unisoc.com>
Subject: Re: [PATCH 1/2] mm/slub: Add panic function when slub leaks
Date: Wed, 25 Sep 2024 19:39:03 +0800 [thread overview]
Message-ID: <202409251901.XFGbDalC-lkp@intel.com> (raw)
In-Reply-To: <20240925032256.1782-2-fangzheng.zhang@unisoc.com>
Hi Fangzheng,
kernel test robot noticed the following build errors:
[auto build test ERROR on akpm-mm/mm-everything]
[also build test ERROR on linus/master v6.11 next-20240925]
[cannot apply to vbabka-slab/for-next]
[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/Fangzheng-Zhang/mm-slub-Add-panic-function-when-slub-leaks/20240925-112601
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link: https://lore.kernel.org/r/20240925032256.1782-2-fangzheng.zhang%40unisoc.com
patch subject: [PATCH 1/2] mm/slub: Add panic function when slub leaks
config: alpha-allnoconfig (https://download.01.org/0day-ci/archive/20240925/202409251901.XFGbDalC-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240925/202409251901.XFGbDalC-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/202409251901.XFGbDalC-lkp@intel.com/
All errors (new ones prefixed by >>):
>> mm/slub.c:7354: error: unterminated #ifdef
7354 | #ifdef CONFIG_SLUB_LEAK_PANIC
|
vim +7354 mm/slub.c
7350
7351 /*
7352 * The /sys/module/slub ABI
7353 */
> 7354 #ifdef CONFIG_SLUB_LEAK_PANIC
7355 /*
7356 * What: /sys/module/slub/parameters/leak_panic
7357 * /sys/module/slub/parameters/leak_panic_threshold
7358 * Date: Sep 2024
7359 * KernelVersion: v6.6+
7360 * Description: Used for slub memory leak check. When the user
7361 * successfully allocates the slub page, it also performs
7362 * statistics on the total slub usage in the system.
7363 * When the usage exceeds the set value
7364 * (threshold * memtotal / 100), it is considered that
7365 * there is a risk of slub leakage in the system at this time.
7366 * A panic operation will be triggered.
7367 * Users: userspace
7368 */
7369 MODULE_PARM_DESC(leak_panic, "Disable/Enable slub_leak_panic");
7370 module_param_named(leak_panic, slub_leak_panic_enabled, bool, 0644);
7371
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-09-25 11:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 3:22 [PATCH 0/2] Introduce " Fangzheng Zhang
2024-09-25 3:22 ` [PATCH 1/2] mm/slub: Add " Fangzheng Zhang
2024-09-25 8:10 ` Greg KH
2024-09-25 12:45 ` zhang fangzheng
2024-09-25 8:10 ` Greg KH
2024-09-25 11:39 ` kernel test robot [this message]
2024-09-25 12:10 ` kernel test robot
2024-09-25 3:22 ` [PATCH 2/2] Documentation: admin-guide: kernel-parameters: Add parameter description for slub_leak_panic function Fangzheng Zhang
2024-09-25 13:18 ` [PATCH 0/2] Introduce panic function when slub leaks Hyeonggon Yoo
2024-09-26 12:30 ` Vlastimil Babka
2024-09-27 7:28 ` zhang fangzheng
2024-09-27 8:01 ` Hyeonggon Yoo
2024-10-09 1:25 ` 答复: " 韩玉明 (Yuming Han)
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=202409251901.XFGbDalC-lkp@intel.com \
--to=lkp@intel.com \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=fangzheng.zhang@unisoc.com \
--cc=greg@kroah.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=tkjos@google.com \
--cc=vbabka@suse.cz \
--cc=yuming.han@unisoc.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