All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Chao Yu <yuchao0@huawei.com>, Chao Yu <chao@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, Chao Yu <yuchao0@huawei.com>,
	Chao Yu <chao@kernel.org>
Subject: [chao:bugfix/syzbot 40/42] fs/f2fs/f2fs.h:4607: multiple definition of `f2fs_build_fault_attr'; fs/f2fs/dir.o:fs/f2fs/f2fs.h:4607: first defined here
Date: Tue, 7 May 2024 06:08:23 +0800	[thread overview]
Message-ID: <202405070649.jVUhtxD4-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git bugfix/syzbot
head:   6fd891b7248d0b825dbff6454be21f60c7ba1fb0
commit: 28a4fc03f837d64c67eeeba5ef226dbed4b369dc [40/42] f2fs: check validation of fault attrs in f2fs_build_fault_attr()
config: i386-randconfig-014-20240507 (https://download.01.org/0day-ci/archive/20240507/202405070649.jVUhtxD4-lkp@intel.com/config)
compiler: gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240507/202405070649.jVUhtxD4-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/202405070649.jVUhtxD4-lkp@intel.com/

All errors (new ones prefixed by >>):

   ld: fs/f2fs/file.o: in function `f2fs_build_fault_attr':
>> fs/f2fs/f2fs.h:4607: multiple definition of `f2fs_build_fault_attr'; fs/f2fs/dir.o:fs/f2fs/f2fs.h:4607: first defined here
   ld: fs/f2fs/inode.o: in function `f2fs_build_fault_attr':
>> fs/f2fs/f2fs.h:4607: multiple definition of `f2fs_build_fault_attr'; fs/f2fs/dir.o:fs/f2fs/f2fs.h:4607: first defined here
   ld: fs/f2fs/namei.o: in function `f2fs_build_fault_attr':
>> fs/f2fs/f2fs.h:4607: multiple definition of `f2fs_build_fault_attr'; fs/f2fs/dir.o:fs/f2fs/f2fs.h:4607: first defined here
   ld: fs/f2fs/hash.o: in function `f2fs_build_fault_attr':
   fs/f2fs/hash.c:4607: multiple definition of `f2fs_build_fault_attr'; fs/f2fs/dir.o:fs/f2fs/f2fs.h:4607: first defined here
   ld: fs/f2fs/super.o: in function `f2fs_build_fault_attr':
>> fs/f2fs/f2fs.h:4607: multiple definition of `f2fs_build_fault_attr'; fs/f2fs/dir.o:fs/f2fs/f2fs.h:4607: first defined here
   ld: fs/f2fs/inline.o: in function `f2fs_build_fault_attr':
>> fs/f2fs/f2fs.h:4607: multiple definition of `f2fs_build_fault_attr'; fs/f2fs/dir.o:fs/f2fs/f2fs.h:4607: first defined here
   ld: fs/f2fs/checkpoint.o: in function `f2fs_build_fault_attr':
>> fs/f2fs/f2fs.h:4607: multiple definition of `f2fs_build_fault_attr'; fs/f2fs/dir.o:fs/f2fs/f2fs.h:4607: first defined here
   ld: fs/f2fs/gc.o: in function `f2fs_build_fault_attr':
>> fs/f2fs/f2fs.h:4607: multiple definition of `f2fs_build_fault_attr'; fs/f2fs/dir.o:fs/f2fs/f2fs.h:4607: first defined here
   ld: fs/f2fs/data.o: in function `f2fs_build_fault_attr':
>> fs/f2fs/f2fs.h:4607: multiple definition of `f2fs_build_fault_attr'; fs/f2fs/dir.o:fs/f2fs/f2fs.h:4607: first defined here
   ld: fs/f2fs/node.o: in function `f2fs_build_fault_attr':
>> fs/f2fs/f2fs.h:4607: multiple definition of `f2fs_build_fault_attr'; fs/f2fs/dir.o:fs/f2fs/f2fs.h:4607: first defined here
   ld: fs/f2fs/segment.o: in function `f2fs_build_fault_attr':
>> fs/f2fs/f2fs.h:4607: multiple definition of `f2fs_build_fault_attr'; fs/f2fs/dir.o:fs/f2fs/f2fs.h:4607: first defined here
   ld: fs/f2fs/recovery.o: in function `f2fs_build_fault_attr':
>> fs/f2fs/f2fs.h:4607: multiple definition of `f2fs_build_fault_attr'; fs/f2fs/dir.o:fs/f2fs/f2fs.h:4607: first defined here
   ld: fs/f2fs/shrinker.o: in function `f2fs_build_fault_attr':
   fs/f2fs/shrinker.c:4607: multiple definition of `f2fs_build_fault_attr'; fs/f2fs/dir.o:fs/f2fs/f2fs.h:4607: first defined here
   ld: fs/f2fs/extent_cache.o: in function `f2fs_build_fault_attr':
>> fs/f2fs/f2fs.h:4607: multiple definition of `f2fs_build_fault_attr'; fs/f2fs/dir.o:fs/f2fs/f2fs.h:4607: first defined here
   ld: fs/f2fs/sysfs.o: in function `f2fs_build_fault_attr':
>> fs/f2fs/f2fs.h:4607: multiple definition of `f2fs_build_fault_attr'; fs/f2fs/dir.o:fs/f2fs/f2fs.h:4607: first defined here
   ld: fs/f2fs/xattr.o: in function `f2fs_build_fault_attr':
>> fs/f2fs/f2fs.h:4607: multiple definition of `f2fs_build_fault_attr'; fs/f2fs/dir.o:fs/f2fs/f2fs.h:4607: first defined here
   ld: fs/f2fs/acl.o: in function `f2fs_build_fault_attr':
>> fs/f2fs/f2fs.h:4607: multiple definition of `f2fs_build_fault_attr'; fs/f2fs/dir.o:fs/f2fs/f2fs.h:4607: first defined here
   ld: fs/f2fs/verity.o: in function `f2fs_build_fault_attr':
>> fs/f2fs/f2fs.h:4607: multiple definition of `f2fs_build_fault_attr'; fs/f2fs/dir.o:fs/f2fs/f2fs.h:4607: first defined here


vim +4607 fs/f2fs/f2fs.h

  4600	
  4601	#ifdef CONFIG_F2FS_FAULT_INJECTION
  4602	extern int f2fs_build_fault_attr(struct f2fs_sb_info *sbi, unsigned long rate,
  4603								unsigned long type);
  4604	#else
  4605	int f2fs_build_fault_attr(struct f2fs_sb_info *sbi, unsigned long rate,
  4606								unsigned long type)
> 4607	{
  4608		return 0;
  4609	}
  4610	#endif
  4611	

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

                 reply	other threads:[~2024-05-06 22: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=202405070649.jVUhtxD4-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=chao@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=yuchao0@huawei.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 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.