From: Boaz Harrosh <ooo@electrozaur.com>
To: kbuild test robot <lkp@intel.com>, Boaz Harrosh <boaz@plexistor.com>
Cc: kbuild-all@01.org, linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Boaz Harrosh <boazh@netapp.com>
Subject: Re: [PATCH 06/16] zuf: Multy Devices
Date: Tue, 13 Aug 2019 13:25:09 +0300 [thread overview]
Message-ID: <a4127b90-e22c-4ed7-4d98-e4c304e4f943@electrozaur.com> (raw)
In-Reply-To: <201908131625.nH4peW0F%lkp@intel.com>
On 13/08/2019 11:11, kbuild test robot wrote:
> 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 >>):
>
> In file included from include/linux/kernel.h:15:0,
> from include/asm-generic/bug.h:18,
> from arch/x86/include/asm/bug.h:83,
> from include/linux/bug.h:5,
> from include/linux/mmdebug.h:5,
> from include/linux/mm.h:9,
> from fs/zuf/t1.c:15:
> fs/zuf/t1.c: In function 't1_fault':
> include/linux/printk.h:304:2: warning: this statement may fall through [-Wimplicit-fallthrough=]
> printk(KERN_ERR pr_fmt(fmt), ##__VA_ARGS__)
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> fs/zuf/_pr.h:23:31: note: in expansion of macro 'pr_err'
> #define zuf_err(s, args ...) pr_err("[%s:%d] " s, __func__, \
> ^~~~~~
>>> fs/zuf/t1.c:75:3: note: in expansion of macro 'zuf_err'
> zuf_err("[%ld] PTE fault not expected pgoff=0x%lx addr=0x%lx\n",
> ^~~~~~~
I do not understand how to fix this problem.
There is an explicit comment that says this is an intentional fall through.
here is the complete code:
switch (pe_size) {
case PE_SIZE_PTE:
zuf_err("[%ld] PTE fault not expected pgoff=0x%lx addr=0x%lx\n",
inode->i_ino, vmf->pgoff, addr);
/* fall through do PMD insert anyway */
case PE_SIZE_PMD:
bn = linear_page_index(vma, addr & PMD_MASK);
pfn = md_pfn(z_pmem->md, bn);
....
Please advise on how to make your compiler happy?
Thanks
Boaz
> fs/zuf/t1.c:78:2: note: here
> case PE_SIZE_PMD:
> ^~~~
>
> vim +/pr_err +23 fs/zuf/_pr.h
>
> f577115420e717 Boaz Harrosh 2019-08-12 19
> f577115420e717 Boaz Harrosh 2019-08-12 20 /*
> f577115420e717 Boaz Harrosh 2019-08-12 21 * Debug code
> f577115420e717 Boaz Harrosh 2019-08-12 22 */
> f577115420e717 Boaz Harrosh 2019-08-12 @23 #define zuf_err(s, args ...) pr_err("[%s:%d] " s, __func__, \
> f577115420e717 Boaz Harrosh 2019-08-12 24 __LINE__, ## args)
> f577115420e717 Boaz Harrosh 2019-08-12 25 #define zuf_err_cnd(silent, s, args ...) \
> f577115420e717 Boaz Harrosh 2019-08-12 26 do {if (!silent) \
> f577115420e717 Boaz Harrosh 2019-08-12 27 pr_err("[%s:%d] " s, __func__, __LINE__, ## args); \
> f577115420e717 Boaz Harrosh 2019-08-12 28 } while (0)
> f577115420e717 Boaz Harrosh 2019-08-12 29 #define zuf_warn(s, args ...) pr_warn("[%s:%d] " s, __func__, \
> f577115420e717 Boaz Harrosh 2019-08-12 30 __LINE__, ## args)
> f577115420e717 Boaz Harrosh 2019-08-12 31 #define zuf_warn_cnd(silent, s, args ...) \
> f577115420e717 Boaz Harrosh 2019-08-12 32 do {if (!silent) \
> f577115420e717 Boaz Harrosh 2019-08-12 33 pr_warn("[%s:%d] " s, __func__, __LINE__, ## args); \
> f577115420e717 Boaz Harrosh 2019-08-12 34 } while (0)
> f577115420e717 Boaz Harrosh 2019-08-12 35 #define zuf_info(s, args ...) pr_info("~info~ " s, ## args)
> f577115420e717 Boaz Harrosh 2019-08-12 36
>
> :::::: The code at line 23 was first introduced by commit
> :::::: f577115420e717e536986a2e6055c584ec2f6829 zuf: zuf-rootfs
>
> :::::: TO: Boaz Harrosh <boaz@plexistor.com>
> :::::: CC: 0day robot <lkp@intel.com>
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
>
next prev parent reply other threads:[~2019-08-13 10: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
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 [this message]
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
2019-08-12 16:47 [PATCHSET 00/16] zuf: ZUFS Zero-copy User-mode FileSystem Boaz Harrosh
2019-08-12 16:47 ` [PATCH 06/16] zuf: Multy Devices 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 06/16] zuf: Multy Devices 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=a4127b90-e22c-4ed7-4d98-e4c304e4f943@electrozaur.com \
--to=ooo@electrozaur.com \
--cc=boaz@plexistor.com \
--cc=boazh@netapp.com \
--cc=kbuild-all@01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lkp@intel.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).