From: kernel test robot <lkp@intel.com>
To: Benjamin Coddington <bcodding@redhat.com>,
trond.myklebust@hammerspace.com, anna@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 2/2] NFSv4: Allow per-mount tuning of READDIR attrs
Date: Thu, 19 Oct 2023 20:06:18 +0800 [thread overview]
Message-ID: <202310191902.6BOby9rI-lkp@intel.com> (raw)
In-Reply-To: <bd900de1d19bc56e6df5b44379f373617acc894e.1697577945.git.bcodding@redhat.com>
Hi Benjamin,
kernel test robot noticed the following build errors:
[auto build test ERROR on trondmy-nfs/linux-next]
[also build test ERROR on linus/master v6.6-rc6 next-20231019]
[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/Benjamin-Coddington/NFSv4-Always-ask-for-type-with-READDIR/20231018-053217
base: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git linux-next
patch link: https://lore.kernel.org/r/bd900de1d19bc56e6df5b44379f373617acc894e.1697577945.git.bcodding%40redhat.com
patch subject: [PATCH 2/2] NFSv4: Allow per-mount tuning of READDIR attrs
config: nios2-defconfig (https://download.01.org/0day-ci/archive/20231019/202310191902.6BOby9rI-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231019/202310191902.6BOby9rI-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/202310191902.6BOby9rI-lkp@intel.com/
All errors (new ones prefixed by >>):
fs/nfs/client.c: In function 'nfs_server_copy_userdata':
>> fs/nfs/client.c:925:22: error: 'struct nfs_server' has no member named 'readdir_attrs'
925 | memcpy(target->readdir_attrs, source->readdir_attrs,
| ^~
fs/nfs/client.c:925:45: error: 'struct nfs_server' has no member named 'readdir_attrs'
925 | memcpy(target->readdir_attrs, source->readdir_attrs,
| ^~
fs/nfs/client.c:926:38: error: 'struct nfs_server' has no member named 'readdir_attrs'
926 | sizeof(target->readdir_attrs));
| ^~
--
fs/nfs/sysfs.c: In function 'v4_readdir_attrs_show':
>> fs/nfs/sysfs.c:281:31: error: 'struct nfs_server' has no member named 'readdir_attrs'
281 | server->readdir_attrs[0],
| ^~
fs/nfs/sysfs.c:282:31: error: 'struct nfs_server' has no member named 'readdir_attrs'
282 | server->readdir_attrs[1],
| ^~
fs/nfs/sysfs.c:283:31: error: 'struct nfs_server' has no member named 'readdir_attrs'
283 | server->readdir_attrs[2]);
| ^~
fs/nfs/sysfs.c: In function 'v4_readdir_attrs_store':
fs/nfs/sysfs.c:338:23: error: 'struct nfs_server' has no member named 'readdir_attrs'
338 | server->readdir_attrs[0] = attrs[0];
| ^~
fs/nfs/sysfs.c:340:23: error: 'struct nfs_server' has no member named 'readdir_attrs'
340 | server->readdir_attrs[1] = attrs[1];
| ^~
fs/nfs/sysfs.c:342:23: error: 'struct nfs_server' has no member named 'readdir_attrs'
342 | server->readdir_attrs[2] = attrs[2];
| ^~
fs/nfs/sysfs.c: In function 'v4_readdir_attrs_show':
>> fs/nfs/sysfs.c:284:1: error: control reaches end of non-void function [-Werror=return-type]
284 | }
| ^
cc1: some warnings being treated as errors
vim +925 fs/nfs/client.c
908
909 /*
910 * Copy useful information when duplicating a server record
911 */
912 void nfs_server_copy_userdata(struct nfs_server *target, struct nfs_server *source)
913 {
914 target->flags = source->flags;
915 target->rsize = source->rsize;
916 target->wsize = source->wsize;
917 target->acregmin = source->acregmin;
918 target->acregmax = source->acregmax;
919 target->acdirmin = source->acdirmin;
920 target->acdirmax = source->acdirmax;
921 target->caps = source->caps;
922 target->options = source->options;
923 target->auth_info = source->auth_info;
924 target->port = source->port;
> 925 memcpy(target->readdir_attrs, source->readdir_attrs,
926 sizeof(target->readdir_attrs));
927 }
928 EXPORT_SYMBOL_GPL(nfs_server_copy_userdata);
929
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-10-19 12:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 21:30 [PATCH 0/2] NFSv4 READDIR d_type fixup Benjamin Coddington
2023-10-17 21:30 ` [PATCH 1/2] NFSv4: Always ask for type with READDIR Benjamin Coddington
2023-10-17 21:30 ` [PATCH 2/2] NFSv4: Allow per-mount tuning of READDIR attrs Benjamin Coddington
2023-10-18 12:56 ` Chuck Lever
2023-10-18 13:33 ` Jeff Layton
2023-10-18 14:24 ` Benjamin Coddington
2023-10-18 14:33 ` Chuck Lever
2023-10-18 14:25 ` Chuck Lever
2023-10-18 18:38 ` Anna Schumaker
2023-10-18 19:08 ` Benjamin Coddington
2023-10-18 19:17 ` Benjamin Coddington
2023-10-19 12:06 ` kernel test robot [this message]
2023-10-19 12:52 ` Benjamin Coddington
2023-10-19 12:18 ` kernel test robot
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=202310191902.6BOby9rI-lkp@intel.com \
--to=lkp@intel.com \
--cc=anna@kernel.org \
--cc=bcodding@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=trond.myklebust@hammerspace.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox