From: kbuild test robot <lkp@intel.com>
To: Trond Myklebust <trond.myklebust@hammerspace.com>
Cc: kbuild-all@lists.01.org, linux-nfs@vger.kernel.org
Subject: [nfs:testing 36/54] fs/nfs/direct.c:308:32: error: 'struct pnfs_ds_commit_info' has no member named 'commits'
Date: Wed, 25 Mar 2020 23:47:29 +0800 [thread overview]
Message-ID: <202003252323.dvAfCCUb%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1670 bytes --]
tree: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git testing
head: 21b71e249eabc75f6db7fb1ff83ce9fc34b09828
commit: cd21157690af4193233d71828cac656f316a35f9 [36/54] NFSv4/pnfs: Support a list of commit arrays in struct pnfs_ds_commit_info
config: x86_64-defconfig (attached as .config)
compiler: gcc-7 (Debian 7.5.0-5) 7.5.0
reproduce:
git checkout cd21157690af4193233d71828cac656f316a35f9
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
fs/nfs/direct.c: In function 'nfs_direct_req_alloc':
>> fs/nfs/direct.c:308:32: error: 'struct pnfs_ds_commit_info' has no member named 'commits'
INIT_LIST_HEAD(&dreq->ds_cinfo.commits);
^
vim +308 fs/nfs/direct.c
295
296 static inline struct nfs_direct_req *nfs_direct_req_alloc(void)
297 {
298 struct nfs_direct_req *dreq;
299
300 dreq = kmem_cache_zalloc(nfs_direct_cachep, GFP_KERNEL);
301 if (!dreq)
302 return NULL;
303
304 kref_init(&dreq->kref);
305 kref_get(&dreq->kref);
306 init_completion(&dreq->completion);
307 INIT_LIST_HEAD(&dreq->mds_cinfo.list);
> 308 INIT_LIST_HEAD(&dreq->ds_cinfo.commits);
309 dreq->verf.committed = NFS_INVALID_STABLE_HOW; /* not set yet */
310 INIT_WORK(&dreq->work, nfs_direct_write_schedule_work);
311 spin_lock_init(&dreq->lock);
312
313 return dreq;
314 }
315
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 28985 bytes --]
reply other threads:[~2020-03-25 15:48 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=202003252323.dvAfCCUb%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-nfs@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).