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 05/16] zuf: zuf-core The ZTs
Date: Tue, 13 Aug 2019 11:24:04 +0800 [thread overview]
Message-ID: <201908131114.vDpupeQe%lkp@intel.com> (raw)
In-Reply-To: <20190812164244.15580-6-boazh@netapp.com>
[-- Attachment #1: Type: text/plain, Size: 4413 bytes --]
Hi Boaz,
I love your patch! Yet something to improve:
[auto build test ERROR 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-allmodconfig (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 errors (new ones prefixed by >>):
fs/zuf/zuf-core.c: In function '_r_zufs_dispatch':
>> fs/zuf/zuf-core.c:697:46: error: 'struct task_struct' has no member named 'cpus_allowed'; did you mean 'mems_allowed'?
cpumask_copy(&zt->relay.cpus_allowed, &app->cpus_allowed);
^~~~~~~~~~~~
mems_allowed
fs/zuf/zuf-core.c:698:21: error: 'struct task_struct' has no member named 'cpus_allowed'; did you mean 'mems_allowed'?
cpumask_copy(&app->cpus_allowed, cpumask_of(smp_processor_id()));
^~~~~~~~~~~~
mems_allowed
fs/zuf/zuf-core.c:721:22: error: 'struct task_struct' has no member named 'cpus_allowed'; did you mean 'mems_allowed'?
cpumask_copy(&app->cpus_allowed, &zt->relay.cpus_allowed);
^~~~~~~~~~~~
mems_allowed
vim +697 fs/zuf/zuf-core.c
643
644 int __zufc_dispatch(struct zuf_root_info *zri, struct zuf_dispatch_op *zdo)
645 #endif /* CONFIG_ZUF_DEBUG */
646 {
647 struct task_struct *app = get_current();
648 struct zufs_ioc_hdr *hdr = zdo->hdr;
649 int cpu;
650 struct zufc_thread *zt;
651
652 if (unlikely(hdr->out_len && !hdr->out_max)) {
653 /* TODO: Complain here and let caller code do this proper */
654 hdr->out_max = hdr->out_len;
655 }
656
657 if (unlikely(zdo->__locked_zt)) {
658 zt = zdo->__locked_zt;
659 zdo->__locked_zt = NULL;
660
661 cpu = get_cpu();
662 /* FIXME: Very Pedantic need it stay */
663 if (unlikely((zt->zdo != zdo) || cpu != zt->no)) {
664 zuf_warn("[%ld] __locked_zt but zdo(%p != %p) || cpu(%d != %d)\n",
665 _zt_pr_no(zt), zt->zdo, zdo, cpu, zt->no);
666 put_cpu();
667 goto channel_busy;
668 }
669 goto has_channel;
670 }
671 channel_busy:
672 cpu = get_cpu();
673
674 if (!_try_grab_zt_channel(zri, cpu, &zt)) {
675 put_cpu();
676
677 /* If channel was grabbed then maybe a break_all is in progress
678 * on a different CPU make sure zt->file on this core is
679 * updated
680 */
681 mb();
682 if (unlikely(!zt->hdr.file)) {
683 zuf_err("[%d] !zt->file\n", cpu);
684 return -EIO;
685 }
686 zuf_dbg_err("[%d] can this be\n", cpu);
687 /* FIXME: Do something much smarter */
688 msleep(10);
689 if (signal_pending(get_current())) {
690 zuf_dbg_err("[%d] => EINTR\n", cpu);
691 return -EINTR;
692 }
693 goto channel_busy;
694 }
695
696 /* lock app to this cpu while waiting */
> 697 cpumask_copy(&zt->relay.cpus_allowed, &app->cpus_allowed);
698 cpumask_copy(&app->cpus_allowed, cpumask_of(smp_processor_id()));
699
700 zt->zdo = zdo;
701
702 has_channel:
703 if (zdo->dh)
704 zdo->dh(zdo, zt, zt->opt_buff);
705 else
706 memcpy(zt->opt_buff, zt->zdo->hdr, zt->zdo->hdr->in_len);
707
708 put_cpu();
709
710 if (relay_fss_wakeup_app_wait(&zt->relay) == -ERESTARTSYS) {
711 struct zufs_ioc_hdr *opt_hdr = zt->opt_buff;
712
713 opt_hdr->flags |= ZUFS_H_INTR;
714
715 relay_fss_wakeup_app_wait_cont(&zt->relay);
716 }
717
718 /* __locked_zt must be kept on same cpu */
719 if (!zdo->__locked_zt)
720 /* restore cpu affinity after wakeup */
721 cpumask_copy(&app->cpus_allowed, &zt->relay.cpus_allowed);
722
723 DEBUG_CPU_SWITCH(cpu);
724
725 return zt->hdr.file ? hdr->err : -EIO;
726 }
727
---
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: 70142 bytes --]
next prev parent reply other threads:[~2019-08-13 3:25 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 [this message]
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
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
-- strict thread matches above, loose matches on Subject: below --
2019-08-12 16:47 [PATCHSET 00/16] zuf: ZUFS Zero-copy User-mode FileSystem Boaz Harrosh
2019-08-12 16:47 ` [PATCH 05/16] zuf: zuf-core The ZTs 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 05/16] zuf: zuf-core The ZTs 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=201908131114.vDpupeQe%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).