[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <201506180458.e6paay0G%fengguang.wu@intel.com>
Date: Thu, 18 Jun 2015 04:04:27 +0800
From: kbuild test robot <fengguang.wu@...el.com>
To: Al Viro <viro@...iv.linux.org.uk>
Cc: kbuild-all@...org, linux-fsdevel@...r.kernel.org,
Evgeniy Dushistov <dushistov@...l.ru>,
linux-kernel@...r.kernel.org
Subject: [vfs:ufs 143/148] fs/ufs/inode.c:1382:6: sparse: symbol
'ufs_truncate_blocks' was not declared. Should it be static?
tree: git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git ufs
head: e19b8eadd131ad50c0c033709aba5f3dacd02d3c
commit: 0df3df4fd76a6acd8516175817ce101a5c781df5 [143/148] ufs: move truncate code into inode.c
reproduce:
# apt-get install sparse
git checkout 0df3df4fd76a6acd8516175817ce101a5c781df5
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
fs/ufs/inode.c:131:72: sparse: incorrect type in argument 3 (different type sizes)
fs/ufs/inode.c:131:72: expected unsigned long [usertype] *offsets
fs/ufs/inode.c:131:72: got unsigned int *<noident>
fs/ufs/util.h:197:40: sparse: restricted __fs16 degrades to integer
fs/ufs/util.h:231:40: sparse: restricted __fs16 degrades to integer
>> fs/ufs/inode.c:1382:6: sparse: symbol 'ufs_truncate_blocks' was not declared. Should it be static?
fs/ufs/inode.c: In function 'ufs_frag_map':
fs/ufs/inode.c:131:65: warning: passing argument 3 of 'ufs_block_to_path' from incompatible pointer type
int depth = ufs_block_to_path(inode, frag >> uspi->s_fpbshift, offsets);
^
fs/ufs/inode.c:44:12: note: expected 'sector_t *' but argument is of type 'unsigned int *'
static int ufs_block_to_path(struct inode *inode, sector_t i_block, sector_t offsets[4])
^
fs/ufs/inode.c:69:16: warning: array subscript is above array bounds [-Warray-bounds]
offsets[n++] = i_block & (ptrs - 1);
^
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
http://lists.01.org/mailman/listinfo/kbuild Intel Corporation
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists