From: kbuild test robot <lkp@intel.com> To: Frank van der Linden <fllinden@amazon.com> Cc: kbuild-all@lists.01.org, bfields@fieldses.org, chuck.lever@oracle.com, linux-nfs@vger.kernel.org Subject: Re: [PATCH 06/14] nfsd: define xattr functions to call in to their vfs counterparts Date: Thu, 12 Mar 2020 15:37:05 +0800 [thread overview] Message-ID: <202003121557.ixk2m2K3%lkp@intel.com> (raw) In-Reply-To: <20200311195954.27117-7-fllinden@amazon.com> Hi Frank, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on nfsd/nfsd-next] [also build test WARNING on nfs/linux-next linus/master v5.6-rc5 next-20200311] [cannot apply to cel/for-next] [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/Frank-van-der-Linden/server-side-user-xattr-support-RFC-8276/20200312-064928 base: git://linux-nfs.org/~bfields/linux.git nfsd-next reproduce: # apt-get install sparse # sparse version: v0.6.1-174-g094d5a94-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@intel.com> sparse warnings: (new ones prefixed by >>) >> fs/nfsd/vfs.c:2102:13: sparse: sparse: incorrect type in assignment (different base types) @@ expected int err @@ got restricted __int err @@ >> fs/nfsd/vfs.c:2102:13: sparse: expected int err >> fs/nfsd/vfs.c:2102:13: sparse: got restricted __be32 >> fs/nfsd/vfs.c:2104:24: sparse: sparse: incorrect type in return expression (different base types) @@ expected restricted __be32 @@ got be32 @@ >> fs/nfsd/vfs.c:2104:24: sparse: expected restricted __be32 >> fs/nfsd/vfs.c:2104:24: sparse: got int err fs/nfsd/vfs.c:2108:21: sparse: sparse: incorrect type in assignment (different base types) @@ expected int err @@ got restricted __int err @@ fs/nfsd/vfs.c:2108:21: sparse: expected int err fs/nfsd/vfs.c:2108:21: sparse: got restricted __be32 fs/nfsd/vfs.c:2112:16: sparse: sparse: incorrect type in return expression (different base types) @@ expected restricted __be32 @@ got be32 @@ fs/nfsd/vfs.c:2112:16: sparse: expected restricted __be32 fs/nfsd/vfs.c:2112:16: sparse: got int err fs/nfsd/vfs.c:2121:13: sparse: sparse: incorrect type in assignment (different base types) @@ expected int err @@ got restricted __int err @@ fs/nfsd/vfs.c:2121:13: sparse: expected int err fs/nfsd/vfs.c:2121:13: sparse: got restricted __be32 fs/nfsd/vfs.c:2123:24: sparse: sparse: incorrect type in return expression (different base types) @@ expected restricted __be32 @@ got be32 @@ fs/nfsd/vfs.c:2123:24: sparse: expected restricted __be32 fs/nfsd/vfs.c:2123:24: sparse: got int err fs/nfsd/vfs.c:2128:21: sparse: sparse: incorrect type in assignment (different base types) @@ expected int err @@ got restricted __int err @@ fs/nfsd/vfs.c:2128:21: sparse: expected int err fs/nfsd/vfs.c:2128:21: sparse: got restricted __be32 fs/nfsd/vfs.c:2132:16: sparse: sparse: incorrect type in return expression (different base types) @@ expected restricted __be32 @@ got be32 @@ fs/nfsd/vfs.c:2132:16: sparse: expected restricted __be32 fs/nfsd/vfs.c:2132:16: sparse: got int err fs/nfsd/vfs.c:2148:13: sparse: sparse: incorrect type in assignment (different base types) @@ expected int err @@ got restricted __int err @@ fs/nfsd/vfs.c:2148:13: sparse: expected int err fs/nfsd/vfs.c:2148:13: sparse: got restricted __be32 fs/nfsd/vfs.c:2150:24: sparse: sparse: incorrect type in return expression (different base types) @@ expected restricted __be32 @@ got be32 @@ fs/nfsd/vfs.c:2150:24: sparse: expected restricted __be32 fs/nfsd/vfs.c:2150:24: sparse: got int err fs/nfsd/vfs.c:2172:13: sparse: sparse: incorrect type in assignment (different base types) @@ expected int err @@ got restricted __int err @@ fs/nfsd/vfs.c:2172:13: sparse: expected int err fs/nfsd/vfs.c:2172:13: sparse: got restricted __be32 fs/nfsd/vfs.c:2174:24: sparse: sparse: incorrect type in return expression (different base types) @@ expected restricted __be32 @@ got be32 @@ fs/nfsd/vfs.c:2174:24: sparse: expected restricted __be32 fs/nfsd/vfs.c:2174:24: sparse: got int err vim +2102 fs/nfsd/vfs.c 2094 2095 __be32 2096 nfsd_getxattr(struct svc_rqst *rqstp, struct svc_fh *fhp, char *name, 2097 void *buf, int *lenp) 2098 { 2099 ssize_t lerr; 2100 int err; 2101 > 2102 err = fh_verify(rqstp, fhp, 0, NFSD_MAY_READ); 2103 if (err) > 2104 return err; 2105 2106 lerr = vfs_getxattr(fhp->fh_dentry, name, buf, *lenp); 2107 if (lerr < 0) 2108 err = nfsd_xattr_errno(lerr); 2109 else 2110 *lenp = lerr; 2111 2112 return err; 2113 } 2114 --- 0-DAY CI Kernel Test Service, Intel Corporation https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com> To: kbuild-all@lists.01.org Subject: Re: [PATCH 06/14] nfsd: define xattr functions to call in to their vfs counterparts Date: Thu, 12 Mar 2020 15:37:05 +0800 [thread overview] Message-ID: <202003121557.ixk2m2K3%lkp@intel.com> (raw) In-Reply-To: <20200311195954.27117-7-fllinden@amazon.com> [-- Attachment #1: Type: text/plain, Size: 4879 bytes --] Hi Frank, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on nfsd/nfsd-next] [also build test WARNING on nfs/linux-next linus/master v5.6-rc5 next-20200311] [cannot apply to cel/for-next] [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/Frank-van-der-Linden/server-side-user-xattr-support-RFC-8276/20200312-064928 base: git://linux-nfs.org/~bfields/linux.git nfsd-next reproduce: # apt-get install sparse # sparse version: v0.6.1-174-g094d5a94-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@intel.com> sparse warnings: (new ones prefixed by >>) >> fs/nfsd/vfs.c:2102:13: sparse: sparse: incorrect type in assignment (different base types) @@ expected int err @@ got restricted __int err @@ >> fs/nfsd/vfs.c:2102:13: sparse: expected int err >> fs/nfsd/vfs.c:2102:13: sparse: got restricted __be32 >> fs/nfsd/vfs.c:2104:24: sparse: sparse: incorrect type in return expression (different base types) @@ expected restricted __be32 @@ got be32 @@ >> fs/nfsd/vfs.c:2104:24: sparse: expected restricted __be32 >> fs/nfsd/vfs.c:2104:24: sparse: got int err fs/nfsd/vfs.c:2108:21: sparse: sparse: incorrect type in assignment (different base types) @@ expected int err @@ got restricted __int err @@ fs/nfsd/vfs.c:2108:21: sparse: expected int err fs/nfsd/vfs.c:2108:21: sparse: got restricted __be32 fs/nfsd/vfs.c:2112:16: sparse: sparse: incorrect type in return expression (different base types) @@ expected restricted __be32 @@ got be32 @@ fs/nfsd/vfs.c:2112:16: sparse: expected restricted __be32 fs/nfsd/vfs.c:2112:16: sparse: got int err fs/nfsd/vfs.c:2121:13: sparse: sparse: incorrect type in assignment (different base types) @@ expected int err @@ got restricted __int err @@ fs/nfsd/vfs.c:2121:13: sparse: expected int err fs/nfsd/vfs.c:2121:13: sparse: got restricted __be32 fs/nfsd/vfs.c:2123:24: sparse: sparse: incorrect type in return expression (different base types) @@ expected restricted __be32 @@ got be32 @@ fs/nfsd/vfs.c:2123:24: sparse: expected restricted __be32 fs/nfsd/vfs.c:2123:24: sparse: got int err fs/nfsd/vfs.c:2128:21: sparse: sparse: incorrect type in assignment (different base types) @@ expected int err @@ got restricted __int err @@ fs/nfsd/vfs.c:2128:21: sparse: expected int err fs/nfsd/vfs.c:2128:21: sparse: got restricted __be32 fs/nfsd/vfs.c:2132:16: sparse: sparse: incorrect type in return expression (different base types) @@ expected restricted __be32 @@ got be32 @@ fs/nfsd/vfs.c:2132:16: sparse: expected restricted __be32 fs/nfsd/vfs.c:2132:16: sparse: got int err fs/nfsd/vfs.c:2148:13: sparse: sparse: incorrect type in assignment (different base types) @@ expected int err @@ got restricted __int err @@ fs/nfsd/vfs.c:2148:13: sparse: expected int err fs/nfsd/vfs.c:2148:13: sparse: got restricted __be32 fs/nfsd/vfs.c:2150:24: sparse: sparse: incorrect type in return expression (different base types) @@ expected restricted __be32 @@ got be32 @@ fs/nfsd/vfs.c:2150:24: sparse: expected restricted __be32 fs/nfsd/vfs.c:2150:24: sparse: got int err fs/nfsd/vfs.c:2172:13: sparse: sparse: incorrect type in assignment (different base types) @@ expected int err @@ got restricted __int err @@ fs/nfsd/vfs.c:2172:13: sparse: expected int err fs/nfsd/vfs.c:2172:13: sparse: got restricted __be32 fs/nfsd/vfs.c:2174:24: sparse: sparse: incorrect type in return expression (different base types) @@ expected restricted __be32 @@ got be32 @@ fs/nfsd/vfs.c:2174:24: sparse: expected restricted __be32 fs/nfsd/vfs.c:2174:24: sparse: got int err vim +2102 fs/nfsd/vfs.c 2094 2095 __be32 2096 nfsd_getxattr(struct svc_rqst *rqstp, struct svc_fh *fhp, char *name, 2097 void *buf, int *lenp) 2098 { 2099 ssize_t lerr; 2100 int err; 2101 > 2102 err = fh_verify(rqstp, fhp, 0, NFSD_MAY_READ); 2103 if (err) > 2104 return err; 2105 2106 lerr = vfs_getxattr(fhp->fh_dentry, name, buf, *lenp); 2107 if (lerr < 0) 2108 err = nfsd_xattr_errno(lerr); 2109 else 2110 *lenp = lerr; 2111 2112 return err; 2113 } 2114 --- 0-DAY CI Kernel Test Service, Intel Corporation https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next prev parent reply other threads:[~2020-03-12 7:38 UTC|newest] Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-11 19:59 [PATCH 00/14] server side user xattr support (RFC 8276) Frank van der Linden 2020-03-11 19:59 ` [PATCH 01/14] nfs,nfsd: NFSv4.2 extended attribute protocol definitions Frank van der Linden 2020-03-11 19:59 ` [PATCH 02/14] xattr: modify vfs_{set,remove}xattr for NFS server use Frank van der Linden 2020-03-12 16:23 ` Chuck Lever 2020-03-13 15:35 ` J. Bruce Fields 2020-03-13 16:07 ` [PATCH 02/14] xattr: modify vfs_{set, remove}xattr " Frank van der Linden 2020-03-13 21:06 ` J. Bruce Fields 2020-03-11 19:59 ` [PATCH 03/14] nfsd: split off the write decode code in to a separate function Frank van der Linden 2020-03-11 19:59 ` [PATCH 04/14] nfsd: make sure the nfsd4_ops array has the right size Frank van der Linden 2020-03-11 19:59 ` [PATCH 05/14] nfsd: add defines for NFSv4.2 extended attribute support Frank van der Linden 2020-03-12 16:23 ` Chuck Lever 2020-03-11 19:59 ` [PATCH 06/14] nfsd: define xattr functions to call in to their vfs counterparts Frank van der Linden 2020-03-12 7:37 ` kbuild test robot [this message] 2020-03-12 7:37 ` kbuild test robot 2020-03-12 16:23 ` Chuck Lever 2020-03-12 17:16 ` Frank van der Linden 2020-03-12 17:57 ` Chuck Lever 2020-03-11 19:59 ` [PATCH 07/14] nfsd: take xattr bits in to account for permission checks Frank van der Linden 2020-03-11 19:59 ` [PATCH 08/14] nfsd: add structure definitions for xattr requests / responses Frank van der Linden 2020-03-11 19:59 ` [PATCH 09/14] nfsd: use kvmalloc in svcxdr_tmpalloc Frank van der Linden 2020-03-11 19:59 ` [PATCH 10/14] nfsd: implement the xattr procedure functions Frank van der Linden 2020-03-12 10:28 ` kbuild test robot 2020-03-12 10:28 ` kbuild test robot 2020-03-12 16:24 ` Chuck Lever 2020-03-11 19:59 ` [PATCH 11/14] nfsd: add user xattr RPC XDR encoding/decoding logic Frank van der Linden 2020-03-12 13:28 ` kbuild test robot 2020-03-12 13:28 ` kbuild test robot 2020-03-12 16:24 ` Chuck Lever 2020-03-19 22:13 ` Frank van der Linden 2020-03-19 22:15 ` Chuck Lever 2020-03-25 23:44 ` Frank van der Linden 2020-03-26 14:12 ` Chuck Lever 2020-03-12 19:16 ` Chuck Lever 2020-03-20 16:47 ` Frank van der Linden 2020-03-20 17:34 ` Chuck Lever 2020-03-20 17:54 ` J. Bruce Fields 2020-03-20 19:44 ` Frank van der Linden 2020-03-11 19:59 ` [PATCH 12/14] nfsd: add xattr operations to ops array Frank van der Linden 2020-03-11 19:59 ` [PATCH 13/14] xattr: add a function to check if a namespace is supported Frank van der Linden 2020-03-12 16:24 ` Chuck Lever 2020-03-11 19:59 ` [PATCH 14/14] nfsd: add fattr support for user extended attributes Frank van der Linden
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=202003121557.ixk2m2K3%lkp@intel.com \ --to=lkp@intel.com \ --cc=bfields@fieldses.org \ --cc=chuck.lever@oracle.com \ --cc=fllinden@amazon.com \ --cc=kbuild-all@lists.01.org \ --cc=linux-nfs@vger.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.