From: kernel test robot <lkp@intel.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 3/5] exportfs: make ->encode_fh() a mandatory method for NFS export
Date: Sun, 22 Oct 2023 11:11:45 +0800 [thread overview]
Message-ID: <202310221030.mHFGcTOT-lkp@intel.com> (raw)
In-Reply-To: <20231018100000.2453965-4-amir73il@gmail.com>
Hi Amir,
kernel test robot noticed the following build errors:
[auto build test ERROR on jack-fs/fsnotify]
[also build test ERROR on trondmy-nfs/linux-next xiang-erofs/dev-test xiang-erofs/dev tytso-ext4/dev kleikamp-shaggy/jfs-next cifs/for-next v6.6-rc6]
[cannot apply to xiang-erofs/fixes jaegeuk-f2fs/dev-test jaegeuk-f2fs/dev mszeredi-fuse/for-next linus/master next-20231020]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Amir-Goldstein/fanotify-limit-reporting-of-event-with-non-decodeable-file-handles/20231018-180124
base: https://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git fsnotify
patch link: https://lore.kernel.org/r/20231018100000.2453965-4-amir73il%40gmail.com
patch subject: [PATCH 3/5] exportfs: make ->encode_fh() a mandatory method for NFS export
config: powerpc-randconfig-002-20231022 (https://download.01.org/0day-ci/archive/20231022/202310221030.mHFGcTOT-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231022/202310221030.mHFGcTOT-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/202310221030.mHFGcTOT-lkp@intel.com/
All errors (new ones prefixed by >>):
powerpc-linux-ld: warning: orphan section `.init.plt' from `drivers/mfd/rsmu_core.o' being placed in section `.init.plt'
>> powerpc-linux-ld: fs/ext4/super.o:(.rodata+0x1314): undefined reference to `generic_encode_ino32_fh'
>> powerpc-linux-ld: fs/squashfs/export.o:(.rodata+0x54): undefined reference to `generic_encode_ino32_fh'
>> powerpc-linux-ld: fs/fat/nfs.o:(.rodata+0x80): undefined reference to `generic_encode_ino32_fh'
>> powerpc-linux-ld: fs/ufs/super.o:(.rodata+0x224): undefined reference to `generic_encode_ino32_fh'
>> powerpc-linux-ld: fs/affs/namei.o:(.rodata+0x120): undefined reference to `generic_encode_ino32_fh'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-10-22 3:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 9:59 [PATCH 0/5] Support more filesystems with FAN_REPORT_FID Amir Goldstein
2023-10-18 9:59 ` [PATCH 1/5] fanotify: limit reporting of event with non-decodeable file handles Amir Goldstein
2023-10-19 14:22 ` Jan Kara
2023-10-18 9:59 ` [PATCH 2/5] exportfs: add helpers to check if filesystem can encode/decode " Amir Goldstein
2023-10-18 14:15 ` Jeff Layton
2023-10-19 14:23 ` Jan Kara
2023-10-18 9:59 ` [PATCH 3/5] exportfs: make ->encode_fh() a mandatory method for NFS export Amir Goldstein
2023-10-18 14:16 ` Jeff Layton
2023-10-18 14:53 ` Dave Kleikamp
2023-10-18 15:24 ` Amir Goldstein
2023-10-18 15:18 ` Chuck Lever
2023-10-18 15:26 ` Amir Goldstein
2023-10-18 15:36 ` Chuck Lever
2023-10-19 14:40 ` Jan Kara
2023-10-19 15:22 ` Amir Goldstein
2023-10-21 16:48 ` kernel test robot
2023-10-22 3:11 ` kernel test robot [this message]
2023-10-18 9:59 ` [PATCH 4/5] exportfs: define FILEID_INO64_GEN* file handle types Amir Goldstein
2023-10-18 14:18 ` Jeff Layton
2023-10-19 14:41 ` Jan Kara
2023-10-18 10:00 ` [PATCH 5/5] exportfs: support encoding non-decodeable file handles by default Amir Goldstein
2023-10-18 14:28 ` Jeff Layton
2023-10-18 15:11 ` Amir Goldstein
2023-10-18 15:27 ` Chuck Lever
2023-10-18 17:19 ` Amir Goldstein
2023-10-23 13:55 ` Amir Goldstein
2023-10-23 16:33 ` Jan Kara
2023-10-23 16:44 ` Amir Goldstein
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=202310221030.mHFGcTOT-lkp@intel.com \
--to=lkp@intel.com \
--cc=amir73il@gmail.com \
--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.