linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Damien Le Moal <damien.lemoal@wdc.com>
Cc: kbuild-all@01.org, linux-fsdevel@vger.kernel.org,
	linux-xfs@vger.kernel.org,
	Johannes Thumshirn <jthumshirn@suse.de>,
	Naohiro Aota <naohiro.aota@wdc.com>,
	Dave Chinner <david@fromorbit.com>,
	"Darrick J . Wong" <darrick.wong@oracle.com>,
	Hannes Reinecke <hare@suse.de>,
	Matias Bjorling <matias.bjorling@wdc.com>
Subject: Re: [PATCH V4] fs: New zonefs file system
Date: Sat, 31 Aug 2019 04:12:55 +0800	[thread overview]
Message-ID: <201908310444.szHT6ZbB%lkp@intel.com> (raw)
In-Reply-To: <20190826065750.11674-1-damien.lemoal@wdc.com>

[-- Attachment #1: Type: text/plain, Size: 5509 bytes --]

Hi Damien,

I love your patch! Yet something to improve:

[auto build test ERROR on linus/master]
[cannot apply to v5.3-rc6 next-20190830]
[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/Damien-Le-Moal/fs-New-zonefs-file-system/20190826-212833
config: s390-allmodconfig (attached as .config)
compiler: s390-linux-gcc (GCC) 7.4.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        GCC_VERSION=7.4.0 make.cross ARCH=s390 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   fs//zonefs/super.c:84:37: warning: 'struct iomap_writepage_ctx' declared inside parameter list will not be visible outside of this definition or declaration
    static int zonefs_map_blocks(struct iomap_writepage_ctx *wpc,
                                        ^~~~~~~~~~~~~~~~~~~
   fs//zonefs/super.c: In function 'zonefs_map_blocks':
>> fs//zonefs/super.c:87:19: error: dereferencing pointer to incomplete type 'struct iomap_writepage_ctx'
     if (offset >= wpc->iomap.offset &&
                      ^~
   fs//zonefs/super.c: At top level:
>> fs//zonefs/super.c:96:21: error: variable 'zonefs_writeback_ops' has initializer but incomplete type
    static const struct iomap_writeback_ops zonefs_writeback_ops = {
                        ^~~~~~~~~~~~~~~~~~~
>> fs//zonefs/super.c:97:3: error: 'const struct iomap_writeback_ops' has no member named 'map_blocks'
     .map_blocks  = zonefs_map_blocks,
      ^~~~~~~~~~
   fs//zonefs/super.c:97:17: warning: excess elements in struct initializer
     .map_blocks  = zonefs_map_blocks,
                    ^~~~~~~~~~~~~~~~~
   fs//zonefs/super.c:97:17: note: (near initialization for 'zonefs_writeback_ops')
   fs//zonefs/super.c: In function 'zonefs_writepage':
>> fs//zonefs/super.c:102:9: error: variable 'wpc' has initializer but incomplete type
     struct iomap_writepage_ctx wpc = { };
            ^~~~~~~~~~~~~~~~~~~
>> fs//zonefs/super.c:102:29: error: storage size of 'wpc' isn't known
     struct iomap_writepage_ctx wpc = { };
                                ^~~
>> fs//zonefs/super.c:104:9: error: implicit declaration of function 'iomap_writepage'; did you mean 'iomap_readpage'? [-Werror=implicit-function-declaration]
     return iomap_writepage(page, wbc, &wpc, &zonefs_writeback_ops);
            ^~~~~~~~~~~~~~~
            iomap_readpage
   fs//zonefs/super.c:102:29: warning: unused variable 'wpc' [-Wunused-variable]
     struct iomap_writepage_ctx wpc = { };
                                ^~~
   fs//zonefs/super.c: In function 'zonefs_writepages':
   fs//zonefs/super.c:110:9: error: variable 'wpc' has initializer but incomplete type
     struct iomap_writepage_ctx wpc = { };
            ^~~~~~~~~~~~~~~~~~~
   fs//zonefs/super.c:110:29: error: storage size of 'wpc' isn't known
     struct iomap_writepage_ctx wpc = { };
                                ^~~
>> fs//zonefs/super.c:112:9: error: implicit declaration of function 'iomap_writepages'; did you mean 'do_writepages'? [-Werror=implicit-function-declaration]
     return iomap_writepages(mapping, wbc, &wpc, &zonefs_writeback_ops);
            ^~~~~~~~~~~~~~~~
            do_writepages
   fs//zonefs/super.c:110:29: warning: unused variable 'wpc' [-Wunused-variable]
     struct iomap_writepage_ctx wpc = { };
                                ^~~
   fs//zonefs/super.c: At top level:
>> fs//zonefs/super.c:96:41: error: storage size of 'zonefs_writeback_ops' isn't known
    static const struct iomap_writeback_ops zonefs_writeback_ops = {
                                            ^~~~~~~~~~~~~~~~~~~~
   fs//zonefs/super.c: In function 'zonefs_writepage':
   fs//zonefs/super.c:105:1: warning: control reaches end of non-void function [-Wreturn-type]
    }
    ^
   fs//zonefs/super.c: In function 'zonefs_writepages':
   fs//zonefs/super.c:113:1: warning: control reaches end of non-void function [-Wreturn-type]
    }
    ^
   cc1: some warnings being treated as errors

vim +87 fs//zonefs/super.c

    83	
  > 84	static int zonefs_map_blocks(struct iomap_writepage_ctx *wpc,
    85				     struct inode *inode, loff_t offset)
    86	{
  > 87		if (offset >= wpc->iomap.offset &&
    88		    offset < wpc->iomap.offset + wpc->iomap.length)
    89			return 0;
    90	
    91		memset(&wpc->iomap, 0, sizeof(wpc->iomap));
    92		return zonefs_iomap_begin(inode, offset, zonefs_file_max_size(inode),
    93					  0, &wpc->iomap);
    94	}
    95	
  > 96	static const struct iomap_writeback_ops zonefs_writeback_ops = {
  > 97		.map_blocks		= zonefs_map_blocks,
    98	};
    99	
   100	static int zonefs_writepage(struct page *page, struct writeback_control *wbc)
   101	{
 > 102		struct iomap_writepage_ctx wpc = { };
   103	
 > 104		return iomap_writepage(page, wbc, &wpc, &zonefs_writeback_ops);
   105	}
   106	
   107	static int zonefs_writepages(struct address_space *mapping,
   108				     struct writeback_control *wbc)
   109	{
 > 110		struct iomap_writepage_ctx wpc = { };
   111	
 > 112		return iomap_writepages(mapping, wbc, &wpc, &zonefs_writeback_ops);
   113	}
   114	

---
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: 55876 bytes --]

  reply	other threads:[~2019-08-30 20:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-26  6:57 [PATCH V4] fs: New zonefs file system Damien Le Moal
2019-08-30 20:12 ` kbuild test robot [this message]
2019-09-03  0:59 ` Damien Le Moal
2019-09-03  3:26   ` Darrick J. Wong
2019-09-03  3:49     ` Damien Le Moal
2019-09-03 21:56       ` Darrick J. Wong
2019-09-04  2:14         ` Damien Le Moal
2019-09-03  6:16     ` Christoph Hellwig
2019-09-03  6:21       ` Damien Le Moal
2019-09-03  6:24         ` Christoph Hellwig

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=201908310444.szHT6ZbB%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=damien.lemoal@wdc.com \
    --cc=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --cc=hare@suse.de \
    --cc=jthumshirn@suse.de \
    --cc=kbuild-all@01.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=matias.bjorling@wdc.com \
    --cc=naohiro.aota@wdc.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).