Hi Josef,

FYI, there are new sparse warnings show up in

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-next.git fsync-work
head:   6792139d008f49bbadff93f06db6f8275157d2bc
commit: 6792139d008f49bbadff93f06db6f8275157d2bc [52/52] Btrfs: make fsync suck less

All sparse warnings:

  fs/btrfs/file.c:179:21: sparse: symbol 'btrfs_find_defrag_inode' was not declared. Should it be static?
+ fs/btrfs/file.c:905:6: sparse: symbol 'update_extent_generation' was not declared. Should it be static?

vim +905 fs/btrfs/file.c
   902	 * list.  Call this only on extents that actually exist, otherwise this will do
   903	 * a whole lot of work for nothing.
   904	 */
 > 905	void update_extent_generation(struct inode *inode, struct btrfs_path *path,
   906				      int slot, u64 gen)
   907	{
   908		struct btrfs_file_extent_item *fi;

Please consider folding the attached diff :-)

---
0-DAY kernel build testing backend         Open Source Technology Centre
Fengguang Wu <wfg@linux.intel.com>                     Intel Corporation