[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <201912270810.Hlw06Rxu%lkp@intel.com>
Date: Fri, 27 Dec 2019 08:17:46 +0800
From: kbuild test robot <lkp@...el.com>
To: yu kuai <yukuai3@...wei.com>
Cc: kbuild-all@...ts.01.org, darrick.wong@...cle.com,
bfoster@...hat.com, dchinner@...hat.com, sandeen@...deen.net,
cmaiolino@...hat.com, hch@....de, linux-xfs@...r.kernel.org,
linux-kernel@...r.kernel.org, yukuai3@...wei.com,
zhengbin13@...wei.com, yi.zhang@...wei.com, houtao1@...wei.com
Subject: Re: [PATCH 2/2] xfs: fix stale data exposure problem when punch
hole, collapse range or zero range across a delalloc extent
Hi yu,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on xfs-linux/for-next]
[cannot apply to djwong-xfs/djwong-devel v5.5-rc3 next-20191220]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/yu-kuai/fix-stale-data-exposure-problem/20191226-235515
base: https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git for-next
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-129-g341daf20-dirty
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@...el.com>
sparse warnings: (new ones prefixed by >>)
>> fs/xfs/xfs_file.c:790:1: sparse: sparse: symbol 'try_split_da_extent' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
Powered by blists - more mailing lists