From: kernel test robot <lkp@intel.com>
To: Ren Yu <renyu@nfschina.com>, cl@linux.com
Cc: kbuild-all@lists.01.org, penberg@kernel.org, rientjes@google.com,
iamjoonsoo.kim@lge.com, akpm@linux-foundation.org,
vbabka@suse.cz, roman.gushchin@linux.dev, 42.hyeyoo@gmail.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
liqiong@nfschina.com, qixu@nfschina.com, hukun@nfschina.com,
yuzhe@nfschina.com, Ren Yu <renyu@nfschina.com>
Subject: Re: [PATCH] mm: check the function kmalloc_slab return value
Date: Mon, 13 Jun 2022 21:37:48 +0800 [thread overview]
Message-ID: <202206132134.VtqdhH9v-lkp@intel.com> (raw)
In-Reply-To: <20220613102438.27723-1-renyu@nfschina.com>
Hi Ren,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on akpm-mm/mm-everything]
url: https://github.com/intel-lab-lkp/linux/commits/Ren-Yu/mm-check-the-function-kmalloc_slab-return-value/20220613-182849
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
config: um-i386_defconfig (https://download.01.org/0day-ci/archive/20220613/202206132134.VtqdhH9v-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
reproduce (this is a W=1 build):
# https://github.com/intel-lab-lkp/linux/commit/5ba2024be9e85177c986e9078e903798cac72f74
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Ren-Yu/mm-check-the-function-kmalloc_slab-return-value/20220613-182849
git checkout 5ba2024be9e85177c986e9078e903798cac72f74
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=um SUBARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
mm/slab.c: In function '__kmem_cache_create':
>> mm/slab.c:2068:38: warning: returning 'struct kmem_cache *' from a function with return type 'int' makes integer from pointer without a cast [-Wint-conversion]
2068 | return cachep->freelist_cache;
| ~~~~~~^~~~~~~~~~~~~~~~
vim +2068 mm/slab.c
2063
2064 if (OFF_SLAB(cachep)) {
2065 cachep->freelist_cache =
2066 kmalloc_slab(cachep->freelist_size, 0u);
2067 if (unlikely(ZERO_OR_NULL_PTR(cachep->freelist_cache)))
> 2068 return cachep->freelist_cache;
2069 }
2070
2071 err = setup_cpu_cache(cachep, gfp);
2072 if (err) {
2073 __kmem_cache_release(cachep);
2074 return err;
2075 }
2076
2077 return 0;
2078 }
2079
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-06-13 14:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 10:24 Ren Yu
2022-06-13 13:37 ` kernel test robot [this message]
2022-06-14 8:39 ` Ren Yu
2022-06-14 8:48 ` Vlastimil Babka
2022-06-14 9:26 ` tury
2022-06-14 11:47 ` Vlastimil Babka
2022-06-14 9:23 ` [PATCH v2] mm, slab: " Ren Yu
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=202206132134.VtqdhH9v-lkp@intel.com \
--to=lkp@intel.com \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=hukun@nfschina.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liqiong@nfschina.com \
--cc=penberg@kernel.org \
--cc=qixu@nfschina.com \
--cc=renyu@nfschina.com \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=vbabka@suse.cz \
--cc=yuzhe@nfschina.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