Re: [PATCH v5 7/7] fs: introduce file_getattr and file_setattr syscalls

[Heiko Carstens <hca@linux.ibm.com>]

On Sun, May 18, 2025 at 07:26:00PM +0800, kernel test robot wrote:
> Hi Andrey,
> 
> kernel test robot noticed the following build warnings:
> 
> [auto build test WARNING on 0d8d44db295ccad20052d6301ef49ff01fb8ae2d]
> 
> url:    https://github.com/intel-lab-lkp/linux/commits/Andrey-Albershteyn/fs-split-fileattr-related-helpers-into-separate-file/20250513-172128
> base:   0d8d44db295ccad20052d6301ef49ff01fb8ae2d
> patch link:    https://lore.kernel.org/r/20250513-xattrat-syscall-v5-7-22bb9c6c767f%40kernel.org
> patch subject: [PATCH v5 7/7] fs: introduce file_getattr and file_setattr syscalls
> config: s390-randconfig-r112-20250518 (https://download.01.org/0day-ci/archive/20250518/202505181900.UGh2tVRs-lkp@intel.com/config)
> compiler: s390-linux-gcc (GCC) 8.5.0
> reproduce: (https://download.01.org/0day-ci/archive/20250518/202505181900.UGh2tVRs-lkp@intel.com/reproduce)
> 
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202505181900.UGh2tVRs-lkp@intel.com/
> 
> sparse warnings: (new ones prefixed by >>)
> >> fs/file_attr.c:362:1: sparse: sparse: Using plain integer as NULL pointer
> >> fs/file_attr.c:362:1: sparse: sparse: Using plain integer as NULL pointer
> >> fs/file_attr.c:362:1: sparse: sparse: Using plain integer as NULL pointer
> >> fs/file_attr.c:362:1: sparse: sparse: Using plain integer as NULL pointer
>    fs/file_attr.c:416:1: sparse: sparse: Using plain integer as NULL pointer
>    fs/file_attr.c:416:1: sparse: sparse: Using plain integer as NULL pointer
>    fs/file_attr.c:416:1: sparse: sparse: Using plain integer as NULL pointer
>    fs/file_attr.c:416:1: sparse: sparse: Using plain integer as NULL pointer
> 
> vim +362 fs/file_attr.c
> 
>    361	
>  > 362	SYSCALL_DEFINE5(file_getattr, int, dfd, const char __user *, filename,
>    363			struct fsxattr __user *, ufsx, size_t, usize,
>    364			unsigned int, at_flags)
>    365	{

Please ignore the warning. There is nothing to fix; this is a warning which
happens only with CONFIG_COMPAT and Al's "SC_DELOUSE" macro, which is used for
compat syscalls. Sparse cannot handle that.