From: kernel test robot <lkp@intel.com>
To: Christian Brauner <brauner@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Vlastimil Babka <vbabka@suse.cz>
Subject: [linux-next:master 6694/7693] mm/slab_common.c:373: warning: Excess function parameter 'freeptr_offset' description in 'kmem_cache_create_usercopy'
Date: Thu, 29 Aug 2024 22:07:35 +0800 [thread overview]
Message-ID: <202408292249.5oUpnCbS-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: b18bbfc14a38b5234e09c2adcf713e38063a7e6e
commit: 18dc9b3951080f2aefb63112b99cd6c95357a8d8 [6694/7693] mm: add kmem_cache_create_rcu()
config: microblaze-randconfig-r032-20221121 (https://download.01.org/0day-ci/archive/20240829/202408292249.5oUpnCbS-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240829/202408292249.5oUpnCbS-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/202408292249.5oUpnCbS-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> mm/slab_common.c:373: warning: Excess function parameter 'freeptr_offset' description in 'kmem_cache_create_usercopy'
vim +373 mm/slab_common.c
338
339 /**
340 * kmem_cache_create_usercopy - Create a cache with a region suitable
341 * for copying to userspace
342 * @name: A string which is used in /proc/slabinfo to identify this cache.
343 * @size: The size of objects to be created in this cache.
344 * @freeptr_offset: Custom offset for the free pointer in RCU caches
345 * @align: The required alignment for the objects.
346 * @flags: SLAB flags
347 * @useroffset: Usercopy region offset
348 * @usersize: Usercopy region size
349 * @ctor: A constructor for the objects.
350 *
351 * Cannot be called within a interrupt, but can be interrupted.
352 * The @ctor is run when new pages are allocated by the cache.
353 *
354 * The flags are
355 *
356 * %SLAB_POISON - Poison the slab with a known test pattern (a5a5a5a5)
357 * to catch references to uninitialised memory.
358 *
359 * %SLAB_RED_ZONE - Insert `Red` zones around the allocated memory to check
360 * for buffer overruns.
361 *
362 * %SLAB_HWCACHE_ALIGN - Align the objects in this cache to a hardware
363 * cacheline. This can be beneficial if you're counting cycles as closely
364 * as davem.
365 *
366 * Return: a pointer to the cache on success, NULL on failure.
367 */
368 struct kmem_cache *
369 kmem_cache_create_usercopy(const char *name, unsigned int size,
370 unsigned int align, slab_flags_t flags,
371 unsigned int useroffset, unsigned int usersize,
372 void (*ctor)(void *))
> 373 {
374 return do_kmem_cache_create_usercopy(name, size, UINT_MAX, align, flags,
375 useroffset, usersize, ctor);
376 }
377 EXPORT_SYMBOL(kmem_cache_create_usercopy);
378
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-08-29 14:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202408292249.5oUpnCbS-lkp@intel.com \
--to=lkp@intel.com \
--cc=brauner@kernel.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vbabka@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).