All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Chao Yu <chao@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, Chao Yu <chao@kernel.org>
Subject: [chao:bugfix/syzbot 5/5] fs/f2fs/xattr.h:156:13: warning: 'f2fs_destroy_xattr_cache' defined but not used
Date: Tue, 14 Oct 2025 01:24:55 +0800	[thread overview]
Message-ID: <202510140134.TvEMgTHM-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git bugfix/syzbot
head:   519a1cbfb1f287de5edded596f01a41af0cf25ec
commit: 519a1cbfb1f287de5edded596f01a41af0cf25ec [5/5] f2fs: use global inline_xattr_slab instead of per-sb slab cache
config: sparc-randconfig-002-20251013 (https://download.01.org/0day-ci/archive/20251014/202510140134.TvEMgTHM-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251014/202510140134.TvEMgTHM-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/202510140134.TvEMgTHM-lkp@intel.com/

All warnings (new ones prefixed by >>):

   In file included from fs/f2fs/file.c:31:
>> fs/f2fs/xattr.h:156:13: warning: 'f2fs_destroy_xattr_cache' defined but not used [-Wunused-function]
    static void f2fs_destroy_xattr_cache(void) { }
                ^~~~~~~~~~~~~~~~~~~~~~~~
>> fs/f2fs/xattr.h:155:19: warning: 'f2fs_init_xattr_cache' defined but not used [-Wunused-function]
    static int __init f2fs_init_xattr_cache(void) { return 0; }
                      ^~~~~~~~~~~~~~~~~~~~~


vim +/f2fs_destroy_xattr_cache +156 fs/f2fs/xattr.h

   140	
   141	#define f2fs_xattr_handlers	NULL
   142	#define f2fs_listxattr		NULL
   143	static inline int f2fs_setxattr(struct inode *inode, int index,
   144			const char *name, const void *value, size_t size,
   145			struct folio *folio, int flags)
   146	{
   147		return -EOPNOTSUPP;
   148	}
   149	static inline int f2fs_getxattr(struct inode *inode, int index,
   150				const char *name, void *buffer,
   151				size_t buffer_size, struct folio *dfolio)
   152	{
   153		return -EOPNOTSUPP;
   154	}
 > 155	static int __init f2fs_init_xattr_cache(void) { return 0; }
 > 156	static void f2fs_destroy_xattr_cache(void) { }
   157	#endif
   158	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2025-10-13 17:25 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=202510140134.TvEMgTHM-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=chao@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 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.