From: kernel test robot <lkp@intel.com>
To: Miklos Szeredi <mszeredi@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-unionfs@vger.kernel.org
Subject: [mszeredi-vfs:statmount-v2 2/3] fs/namespace.c:4869: undefined reference to `show_path'
Date: Thu, 21 Sep 2023 14:33:03 +0800 [thread overview]
Message-ID: <202309211427.pt52GuFm-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git statmount-v2
head: 9b5ff63d2b9b94298e6c9fbac4df9e77e6901fc9
commit: 43d6746354fa23a231946542c476e14f483c44c5 [2/3] add statmount(2) syscall
config: i386-buildonly-randconfig-001-20230921 (https://download.01.org/0day-ci/archive/20230921/202309211427.pt52GuFm-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230921/202309211427.pt52GuFm-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/202309211427.pt52GuFm-lkp@intel.com/
All errors (new ones prefixed by >>):
ld: fs/namespace.o: in function `stmt_mnt_root':
>> fs/namespace.c:4869: undefined reference to `show_path'
vim +4869 fs/namespace.c
4865
4866 static int stmt_mnt_root(struct stmt_state *s)
4867 {
4868 struct seq_file *seq = &s->seq;
> 4869 int err = show_path(seq, s->mnt->mnt_root);
4870
4871 if (!err && !seq_has_overflowed(seq)) {
4872 seq->buf[seq->count] = '\0';
4873 seq->count = string_unescape_inplace(seq->buf, UNESCAPE_OCTAL);
4874 }
4875 return err;
4876 }
4877
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-09-21 18:12 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=202309211427.pt52GuFm-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-unionfs@vger.kernel.org \
--cc=mszeredi@redhat.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).