From: kernel test robot <lkp@intel.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: oe-kbuild-all@lists.linux.dev, linux-fsdevel@vger.kernel.org
Subject: [viro-vfs:work.debugfs 17/18] mm/slub.c:7576:70: error: macro "debugfs_create_file" passed 6 arguments, but takes just 5
Date: Thu, 26 Dec 2024 10:03:22 +0800 [thread overview]
Message-ID: <202412260912.PLXDHzVz-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.debugfs
head: e98a67d7c1e4a22fa9b851507e25ecdc5b8cea6d
commit: 3c2d1b64cb4320860923a2097f5891efa2d7060e [17/18] slub: don't mess with ->d_name
config: arc-randconfig-001-20241226 (https://download.01.org/0day-ci/archive/20241226/202412260912.PLXDHzVz-lkp@intel.com/config)
compiler: arceb-elf-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241226/202412260912.PLXDHzVz-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/202412260912.PLXDHzVz-lkp@intel.com/
All errors (new ones prefixed by >>):
mm/slub.c: In function 'debugfs_slab_add':
>> mm/slub.c:7576:70: error: macro "debugfs_create_file" passed 6 arguments, but takes just 5
7576 | (void *)(unsigned long)TRACK_FREE, &slab_debugfs_fops);
| ^
In file included from mm/slub.c:46:
include/linux/debugfs.h:125: note: macro "debugfs_create_file" defined here
125 | #define debugfs_create_file(name, mode, parent, data, fops) \
|
>> mm/slub.c:7575:9: error: 'debugfs_create_file' undeclared (first use in this function); did you mean 'debugfs_create_xul'?
7575 | debugfs_create_file("free_traces", 0400, slab_cache_dir, s,
| ^~~~~~~~~~~~~~~~~~~
| debugfs_create_xul
mm/slub.c:7575:9: note: each undeclared identifier is reported only once for each function it appears in
vim +/debugfs_create_file +7576 mm/slub.c
7562
7563 static void debugfs_slab_add(struct kmem_cache *s)
7564 {
7565 struct dentry *slab_cache_dir;
7566
7567 if (unlikely(!slab_debugfs_root))
7568 return;
7569
7570 slab_cache_dir = debugfs_create_dir(s->name, slab_debugfs_root);
7571
7572 debugfs_create_file_aux("alloc_traces", 0400, slab_cache_dir, s,
7573 (void *)(unsigned long)TRACK_ALLOC, &slab_debugfs_fops);
7574
> 7575 debugfs_create_file("free_traces", 0400, slab_cache_dir, s,
> 7576 (void *)(unsigned long)TRACK_FREE, &slab_debugfs_fops);
7577 }
7578
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-12-26 2:03 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=202412260912.PLXDHzVz-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.