From: kernel test robot <lkp@intel.com>
To: Andrey Albershteyn <aalbersh@redhat.com>, linux-fsdevel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
Andrey Albershteyn <aalbersh@redhat.com>,
linux-api@vger.kernel.org, monstr@monstr.eu, mpe@ellerman.id.au,
npiggin@gmail.com, christophe.leroy@csgroup.eu,
naveen@kernel.org, maddy@linux.ibm.com, luto@kernel.org,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
chris@zankel.net, jcmvbkbc@gmail.com, viro@zeniv.linux.org.uk,
brauner@kernel.org, jack@suse.cz, arnd@arndb.de,
linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-m68k@lists.linux-m68k.org, linux-parisc@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org,
linux-sh@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: [PATCH] fs: introduce getfsxattrat and setfsxattrat syscalls
Date: Mon, 13 Jan 2025 11:25:27 +0800 [thread overview]
Message-ID: <202501131033.KKMmoHBV-lkp@intel.com> (raw)
In-Reply-To: <20250109174540.893098-1-aalbersh@kernel.org>
Hi Andrey,
kernel test robot noticed the following build warnings:
[auto build test WARNING on brauner-vfs/vfs.all]
[also build test WARNING on geert-m68k/for-next powerpc/next powerpc/fixes s390/features linus/master v6.13-rc6 next-20250110]
[cannot apply to geert-m68k/for-linus deller-parisc/for-next jcmvbkbc-xtensa/xtensa-for-next arnd-asm-generic/master tip/x86/asm]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Andrey-Albershteyn/fs-introduce-getfsxattrat-and-setfsxattrat-syscalls/20250110-014739
base: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git vfs.all
patch link: https://lore.kernel.org/r/20250109174540.893098-1-aalbersh%40kernel.org
patch subject: [PATCH] fs: introduce getfsxattrat and setfsxattrat syscalls
config: m68k-randconfig-r122-20250111 (https://download.01.org/0day-ci/archive/20250113/202501131033.KKMmoHBV-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 14.2.0
reproduce: (https://download.01.org/0day-ci/archive/20250113/202501131033.KKMmoHBV-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/202501131033.KKMmoHBV-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
fs/inode.c:957:24: sparse: sparse: context imbalance in 'inode_lru_isolate' - wrong count at exit
fs/inode.c:1058:9: sparse: sparse: context imbalance in 'find_inode' - different lock contexts for basic block
fs/inode.c:1099:9: sparse: sparse: context imbalance in 'find_inode_fast' - different lock contexts for basic block
fs/inode.c:1829:5: sparse: sparse: context imbalance in 'insert_inode_locked' - wrong count at exit
fs/inode.c:1947:20: sparse: sparse: context imbalance in 'iput_final' - unexpected unlock
fs/inode.c:1961:6: sparse: sparse: context imbalance in 'iput' - wrong count at exit
fs/inode.c:2494:17: sparse: sparse: context imbalance in '__wait_on_freeing_inode' - unexpected unlock
>> fs/inode.c:2998:39: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected struct fsxattr [noderef] __user *ufa @@ got struct fsxattr *fsx @@
fs/inode.c:2998:39: sparse: expected struct fsxattr [noderef] __user *ufa
fs/inode.c:2998:39: sparse: got struct fsxattr *fsx
fs/inode.c:3032:41: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected struct fsxattr [noderef] __user *ufa @@ got struct fsxattr *fsx @@
fs/inode.c:3032:41: sparse: expected struct fsxattr [noderef] __user *ufa
fs/inode.c:3032:41: sparse: got struct fsxattr *fsx
vim +2998 fs/inode.c
2959
2960 SYSCALL_DEFINE4(getfsxattrat, int, dfd, const char __user *, filename,
2961 struct fsxattr *, fsx, int, at_flags)
2962 {
2963 struct fd dir;
2964 struct fileattr fa;
2965 struct path filepath;
2966 struct inode *inode;
2967 int error;
2968
2969 if (at_flags)
2970 return -EINVAL;
2971
2972 if (!capable(CAP_FOWNER))
2973 return -EPERM;
2974
2975 dir = fdget(dfd);
2976 if (!fd_file(dir))
2977 return -EBADF;
2978
2979 if (!S_ISDIR(file_inode(fd_file(dir))->i_mode)) {
2980 error = -EBADF;
2981 goto out;
2982 }
2983
2984 error = user_path_at(dfd, filename, at_flags, &filepath);
2985 if (error)
2986 goto out;
2987
2988 inode = filepath.dentry->d_inode;
2989 if (file_inode(fd_file(dir))->i_sb->s_magic != inode->i_sb->s_magic) {
2990 error = -EBADF;
2991 goto out_path;
2992 }
2993
2994 error = vfs_fileattr_get(filepath.dentry, &fa);
2995 if (error)
2996 goto out_path;
2997
> 2998 if (copy_fsxattr_to_user(&fa, fsx))
2999 error = -EFAULT;
3000
3001 out_path:
3002 path_put(&filepath);
3003 out:
3004 fdput(dir);
3005 return error;
3006 }
3007
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-01-13 3:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 17:45 [PATCH] fs: introduce getfsxattrat and setfsxattrat syscalls Andrey Albershteyn
2025-01-09 19:59 ` Arnd Bergmann
2025-01-10 9:44 ` Andrey Albershteyn
2025-01-11 13:07 ` kernel test robot
2025-01-11 15:47 ` kernel test robot
2025-01-11 21:05 ` kernel test robot
2025-01-13 3:25 ` kernel test robot [this message]
2025-01-13 11:19 ` Jan Kara
2025-01-13 15:31 ` Andrey Albershteyn
2025-01-15 0:05 ` Darrick J. Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202501131033.KKMmoHBV-lkp@intel.com \
--to=lkp@intel.com \
--cc=aalbersh@redhat.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=brauner@kernel.org \
--cc=chris@zankel.net \
--cc=christophe.leroy@csgroup.eu \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jack@suse.cz \
--cc=jcmvbkbc@gmail.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=luto@kernel.org \
--cc=maddy@linux.ibm.com \
--cc=mingo@redhat.com \
--cc=monstr@monstr.eu \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=npiggin@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sparclinux@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).