From: kbuild test robot <lkp@intel.com>
To: Boaz Harrosh <boaz@plexistor.com>
Cc: kbuild-all@01.org, Boaz Harrosh <boaz@plexistor.com>,
Boaz Harrosh <ooo@electrozaur.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Boaz Harrosh <boazh@netapp.com>
Subject: Re: [PATCH 07/16] zuf: mounting
Date: Tue, 13 Aug 2019 16:58:05 +0800 [thread overview]
Message-ID: <201908131636.YCcvbjVD%lkp@intel.com> (raw)
In-Reply-To: <20190812164244.15580-8-boazh@netapp.com>
[-- Attachment #1: Type: text/plain, Size: 2816 bytes --]
Hi Boaz,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[cannot apply to v5.3-rc4]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Boaz-Harrosh/zuf-ZUFS-Zero-copy-User-mode-FileSystem/20190813-074124
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-7 (Debian 7.4.0-10) 7.4.0
reproduce:
# 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 warnings (new ones prefixed by >>):
fs/zuf/zuf-core.c: In function '_r_zufs_dispatch':
fs/zuf/zuf-core.c:860:46: error: 'struct task_struct' has no member named 'cpus_allowed'; did you mean 'nr_cpus_allowed'?
cpumask_copy(&zt->relay.cpus_allowed, &app->cpus_allowed);
^~~~~~~~~~~~
nr_cpus_allowed
fs/zuf/zuf-core.c:861:21: error: 'struct task_struct' has no member named 'cpus_allowed'; did you mean 'nr_cpus_allowed'?
cpumask_copy(&app->cpus_allowed, cpumask_of(smp_processor_id()));
^~~~~~~~~~~~
nr_cpus_allowed
fs/zuf/zuf-core.c:884:22: error: 'struct task_struct' has no member named 'cpus_allowed'; did you mean 'nr_cpus_allowed'?
cpumask_copy(&app->cpus_allowed, &zt->relay.cpus_allowed);
^~~~~~~~~~~~
nr_cpus_allowed
fs/zuf/zuf-core.c: In function 'zufc_release':
>> fs/zuf/zuf-core.c:1078:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
_zu_private_mounter_release(file);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
fs/zuf/zuf-core.c:1079:2: note: here
case zlfs_e_pmem:
^~~~
vim +1078 fs/zuf/zuf-core.c
1062
1063 int zufc_release(struct inode *inode, struct file *file)
1064 {
1065 struct zuf_special_file *zsf = file->private_data;
1066
1067 if (!zsf)
1068 return 0;
1069
1070 switch (zsf->type) {
1071 case zlfs_e_zt:
1072 zufc_zt_release(file);
1073 return 0;
1074 case zlfs_e_mout_thread:
1075 zufc_mounter_release(file);
1076 return 0;
1077 case zlfs_e_private_mount:
> 1078 _zu_private_mounter_release(file);
1079 case zlfs_e_pmem:
1080 /* NOTHING to clean for pmem file yet */
1081 /* zuf_pmem_release(file);*/
1082 return 0;
1083 case zlfs_e_dpp_buff:
1084 zufc_ebuff_release(file);
1085 return 0;
1086 default:
1087 return 0;
1088 }
1089 }
1090
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 69489 bytes --]
next prev parent reply other threads:[~2019-08-13 8:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 16:42 [PATCHSET 00/16] zuf: ZUFS Zero-copy User-mode FileSystem Boaz Harrosh
2019-08-12 16:42 ` [PATCH 01/16] fs: Add the ZUF filesystem to the build + License Boaz Harrosh
2019-08-12 16:42 ` [PATCH 02/16] MAINTAINERS: Add the ZUFS maintainership Boaz Harrosh
2019-08-12 16:42 ` [PATCH 03/16] zuf: Preliminary Documentation Boaz Harrosh
2019-08-12 16:42 ` [PATCH 04/16] zuf: zuf-rootfs Boaz Harrosh
2019-08-12 16:42 ` [PATCH 05/16] zuf: zuf-core The ZTs Boaz Harrosh
2019-08-13 3:24 ` kbuild test robot
2019-08-13 10:18 ` Boaz Harrosh
2019-08-13 5:06 ` kbuild test robot
2019-08-12 16:42 ` [PATCH 06/16] zuf: Multy Devices Boaz Harrosh
2019-08-13 8:11 ` kbuild test robot
2019-08-13 10:25 ` Boaz Harrosh
2019-08-12 16:42 ` [PATCH 07/16] zuf: mounting Boaz Harrosh
2019-08-13 8:58 ` kbuild test robot [this message]
2019-08-12 16:42 ` [PATCH 08/16] zuf: Namei and directory operations Boaz Harrosh
2019-08-12 16:42 ` [PATCH 09/16] zuf: readdir operation Boaz Harrosh
[not found] ` <201908131749.N9ibirdS%lkp@intel.com>
2019-08-13 10:26 ` Boaz Harrosh
2019-08-12 16:42 ` [PATCH 10/16] zuf: symlink Boaz Harrosh
2019-08-12 16:42 ` [PATCH 11/16] zuf: Write/Read implementation Boaz Harrosh
2019-08-13 10:23 ` kbuild test robot
2019-08-13 10:28 ` Boaz Harrosh
2019-08-12 16:42 ` [PATCH 12/16] zuf: mmap & sync Boaz Harrosh
2019-08-12 16:42 ` [PATCH 13/16] zuf: More file operation Boaz Harrosh
2019-08-13 11:32 ` kbuild test robot
2019-08-12 16:42 ` [PATCH 14/16] zuf: ioctl implementation Boaz Harrosh
2019-08-12 16:42 ` [PATCH 15/16] zuf: xattr && acl implementation Boaz Harrosh
2019-08-12 16:42 ` [PATCH 16/16] zuf: Support for dynamic-debug of zusFSs Boaz Harrosh
2019-08-12 16:47 [PATCHSET 00/16] zuf: ZUFS Zero-copy User-mode FileSystem Boaz Harrosh
2019-08-12 16:47 ` [PATCH 07/16] zuf: mounting Boaz Harrosh
2019-09-26 2:07 [PATCHSET v02 00/16] zuf: ZUFS Zero-copy User-mode FileSystem Boaz Harrosh
2019-09-26 2:07 ` [PATCH 07/16] zuf: mounting Boaz Harrosh
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=201908131636.YCcvbjVD%lkp@intel.com \
--to=lkp@intel.com \
--cc=boaz@plexistor.com \
--cc=boazh@netapp.com \
--cc=kbuild-all@01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ooo@electrozaur.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).