From: kernel test robot <lkp@intel.com>
To: Mateusz Guzik <mjguzik@gmail.com>, dchinner@redhat.com
Cc: oe-kbuild-all@lists.linux.dev, cem@kernel.org, djwong@kernel.org,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
Mateusz Guzik <mjguzik@gmail.com>
Subject: Re: [PATCH] xfs: use inode_set_cached_link()
Date: Tue, 26 Nov 2024 02:36:51 +0800 [thread overview]
Message-ID: <202411260215.6DW8BfsK-lkp@intel.com> (raw)
In-Reply-To: <20241123075105.1082661-1-mjguzik@gmail.com>
Hi Mateusz,
kernel test robot noticed the following build errors:
[auto build test ERROR on xfs-linux/for-next]
[also build test ERROR on linus/master v6.12 next-20241125]
[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/Mateusz-Guzik/xfs-use-inode_set_cached_link/20241125-115441
base: https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git for-next
patch link: https://lore.kernel.org/r/20241123075105.1082661-1-mjguzik%40gmail.com
patch subject: [PATCH] xfs: use inode_set_cached_link()
config: i386-randconfig-001-20241125 (https://download.01.org/0day-ci/archive/20241126/202411260215.6DW8BfsK-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241126/202411260215.6DW8BfsK-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/202411260215.6DW8BfsK-lkp@intel.com/
All errors (new ones prefixed by >>):
fs/xfs/xfs_symlink.c: In function 'xfs_setup_cached_symlink':
>> fs/xfs/xfs_symlink.c:52:9: error: implicit declaration of function 'inode_set_cached_link' [-Werror=implicit-function-declaration]
52 | inode_set_cached_link(inode, ip->i_df.if_data, pathlen);
| ^~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/inode_set_cached_link +52 fs/xfs/xfs_symlink.c
30
31 void
32 xfs_setup_cached_symlink(
33 struct xfs_inode *ip)
34 {
35 struct inode *inode = &ip->i_vnode;
36 xfs_fsize_t pathlen;
37
38 /*
39 * If we have the symlink readily accessible let the VFS know where to
40 * find it. This avoids calls to xfs_readlink().
41 */
42 pathlen = ip->i_disk_size;
43 if (pathlen <= 0 || pathlen > XFS_SYMLINK_MAXLEN)
44 return;
45
46 if (ip->i_df.if_format != XFS_DINODE_FMT_LOCAL)
47 return;
48
49 if (XFS_IS_CORRUPT(ip->i_mount, !ip->i_df.if_data))
50 return;
51
> 52 inode_set_cached_link(inode, ip->i_df.if_data, pathlen);
53 }
54
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-11-25 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-23 7:51 [PATCH] xfs: use inode_set_cached_link() Mateusz Guzik
2024-11-23 16:19 ` Darrick J. Wong
2024-11-23 18:52 ` Mateusz Guzik
2024-11-25 13:37 ` kernel test robot
2024-11-25 18:36 ` kernel test robot [this message]
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=202411260215.6DW8BfsK-lkp@intel.com \
--to=lkp@intel.com \
--cc=cem@kernel.org \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mjguzik@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox