Hi Nikolay,

[auto build test WARNING on next-20170217]
[cannot apply to btrfs/next v4.9-rc8 v4.9-rc7 v4.9-rc6 v4.10-rc8]
[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/Nikolay-Borisov/More-btrfs_inode-cleanups/20170217-233314
config: xtensa-allmodconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 4.9.0
reproduce:
        wget 
https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross
 -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=xtensa 

All warnings (new ones prefixed by >>):

   fs/btrfs/inode.c: In function 'btrfs_test_destroy_inode':
>> fs/btrfs/inode.c:9279:2: warning: passing argument 1 of 
>> 'btrfs_drop_extent_cache' from incompatible pointer type
     btrfs_drop_extent_cache(inode, 0, (u64)-1, 0);
     ^
   In file included from fs/btrfs/inode.c:45:0:
   fs/btrfs/ctree.h:3222:6: note: expected 'struct btrfs_inode *' but argument 
is of type 'struct inode *'
    void btrfs_drop_extent_cache(struct btrfs_inode *inode, u64 start, u64 end,
         ^
--
   fs/btrfs/tests/inode-tests.c: In function 'test_btrfs_get_extent':
>> fs/btrfs/tests/inode-tests.c:296:2: warning: passing argument 1 of 
>> 'btrfs_drop_extent_cache' from incompatible pointer type
     btrfs_drop_extent_cache(inode, 0, (u64)-1, 0);
     ^
   In file included from fs/btrfs/tests/inode-tests.c:21:0:
   fs/btrfs/tests/../ctree.h:3222:6: note: expected 'struct btrfs_inode *' but 
argument is of type 'struct inode *'
    void btrfs_drop_extent_cache(struct btrfs_inode *inode, u64 start, u64 end,
         ^

vim +/btrfs_drop_extent_cache +9279 fs/btrfs/inode.c

0b32f4bbb Josef Bacik   2012-03-13  9263        
ei->io_failure_tree.track_uptodate = 1;
b812ce287 Josef Bacik   2012-11-16  9264        atomic_set(&ei->sync_writers, 
0);
2ead6ae77 Yan, Zheng    2010-05-16  9265        mutex_init(&ei->log_mutex);
f248679e8 Josef Bacik   2012-01-13  9266        mutex_init(&ei->delalloc_mutex);
e6dcd2dc9 Chris Mason   2008-07-17  9267        
btrfs_ordered_inode_tree_init(&ei->ordered_tree);
2ead6ae77 Yan, Zheng    2010-05-16  9268        
INIT_LIST_HEAD(&ei->delalloc_inodes);
8089fe62c David Sterba  2015-11-19  9269        
INIT_LIST_HEAD(&ei->delayed_iput);
2ead6ae77 Yan, Zheng    2010-05-16  9270        RB_CLEAR_NODE(&ei->rb_node);
5f9a8a51d Filipe Manana 2016-05-12  9271        init_rwsem(&ei->dio_sem);
2ead6ae77 Yan, Zheng    2010-05-16  9272  
2ead6ae77 Yan, Zheng    2010-05-16  9273        return inode;
39279cc3d Chris Mason   2007-06-12  9274  }
39279cc3d Chris Mason   2007-06-12  9275  
aaedb55bc Josef Bacik   2013-10-11  9276  #ifdef 
CONFIG_BTRFS_FS_RUN_SANITY_TESTS
aaedb55bc Josef Bacik   2013-10-11  9277  void btrfs_test_destroy_inode(struct 
inode *inode)
aaedb55bc Josef Bacik   2013-10-11  9278  {
aaedb55bc Josef Bacik   2013-10-11 @9279        btrfs_drop_extent_cache(inode, 
0, (u64)-1, 0);
aaedb55bc Josef Bacik   2013-10-11  9280        
kmem_cache_free(btrfs_inode_cachep, BTRFS_I(inode));
aaedb55bc Josef Bacik   2013-10-11  9281  }
aaedb55bc Josef Bacik   2013-10-11  9282  #endif
aaedb55bc Josef Bacik   2013-10-11  9283  
fa0d7e3de Nick Piggin   2011-01-07  9284  static void btrfs_i_callback(struct 
rcu_head *head)
fa0d7e3de Nick Piggin   2011-01-07  9285  {
fa0d7e3de Nick Piggin   2011-01-07  9286        struct inode *inode = 
container_of(head, struct inode, i_rcu);
fa0d7e3de Nick Piggin   2011-01-07  9287        
kmem_cache_free(btrfs_inode_cachep, BTRFS_I(inode));

:::::: The code at line 9279 was first introduced by commit
:::::: aaedb55bc08f384b7f57dbb3222a511baed4decf Btrfs: add tests for 
btrfs_get_extent

:::::: TO: Josef Bacik <jba...@fusionio.com>
:::::: CC: Chris Mason <chris.ma...@fusionio.com>

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

Attachment: .config.gz
Description: application/gzip

Reply via email to