From: Chandan Babu R <chandan.babu@oracle.com> To: Dave Chinner <david@fromorbit.com> Cc: kernel test robot <lkp@intel.com>, linux-xfs@vger.kernel.org, kbuild-all@lists.01.org, djwong@kernel.org, Dave Chinner <dchinner@redhat.com> Subject: Re: [PATCH V9 14/19] xfs: Introduce per-inode 64-bit extent counters Date: Thu, 07 Apr 2022 13:48:55 +0530 [thread overview] Message-ID: <87ilrlxq4w.fsf@debian-BULLSEYE-live-builder-AMD64> (raw) In-Reply-To: <20220407010737.GD1544202@dread.disaster.area> On 07 Apr 2022 at 06:37, Dave Chinner wrote: > On Thu, Apr 07, 2022 at 03:03:32AM +0800, kernel test robot wrote: >> Hi Chandan, >> >> Thank you for the patch! Perhaps something to improve: >> >> [auto build test WARNING on xfs-linux/for-next] >> [also build test WARNING on v5.18-rc1 next-20220406] >> [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] >> >> url: https://github.com/intel-lab-lkp/linux/commits/Chandan-Babu-R/xfs-Extend-per-inode-extent-counters/20220406-174647 >> base: https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git for-next >> config: i386-randconfig-s002 (https://download.01.org/0day-ci/archive/20220407/202204070218.QyD2PQPx-lkp@intel.com/config) >> compiler: gcc-11 (Debian 11.2.0-19) 11.2.0 >> reproduce: >> # apt-get install sparse >> # sparse version: v0.6.4-dirty >> # https://github.com/intel-lab-lkp/linux/commit/28be4fd3f13d4ba2bcedceb8951cd3bfe852cba2 >> git remote add linux-review https://github.com/intel-lab-lkp/linux >> git fetch --no-tags linux-review Chandan-Babu-R/xfs-Extend-per-inode-extent-counters/20220406-174647 >> git checkout 28be4fd3f13d4ba2bcedceb8951cd3bfe852cba2 >> # save the config file to linux build tree >> mkdir build_dir >> make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash fs/xfs/ >> >> If you fix the issue, kindly add following tag as appropriate >> Reported-by: kernel test robot <lkp@intel.com> >> >> >> sparse warnings: (new ones prefixed by >>) >> >> fs/xfs/xfs_inode_item_recover.c:209:31: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __be64 [usertype] di_v3_pad @@ got unsigned long long [usertype] di_v3_pad @@ >> fs/xfs/xfs_inode_item_recover.c:209:31: sparse: expected restricted __be64 [usertype] di_v3_pad >> fs/xfs/xfs_inode_item_recover.c:209:31: sparse: got unsigned long long [usertype] di_v3_pad >> >> vim +209 fs/xfs/xfs_inode_item_recover.c >> >> 167 >> 168 STATIC void >> 169 xfs_log_dinode_to_disk( >> 170 struct xfs_log_dinode *from, >> 171 struct xfs_dinode *to, >> 172 xfs_lsn_t lsn) >> 173 { >> 174 to->di_magic = cpu_to_be16(from->di_magic); >> 175 to->di_mode = cpu_to_be16(from->di_mode); >> 176 to->di_version = from->di_version; >> 177 to->di_format = from->di_format; >> 178 to->di_onlink = 0; >> 179 to->di_uid = cpu_to_be32(from->di_uid); >> 180 to->di_gid = cpu_to_be32(from->di_gid); >> 181 to->di_nlink = cpu_to_be32(from->di_nlink); >> 182 to->di_projid_lo = cpu_to_be16(from->di_projid_lo); >> 183 to->di_projid_hi = cpu_to_be16(from->di_projid_hi); >> 184 >> 185 to->di_atime = xfs_log_dinode_to_disk_ts(from, from->di_atime); >> 186 to->di_mtime = xfs_log_dinode_to_disk_ts(from, from->di_mtime); >> 187 to->di_ctime = xfs_log_dinode_to_disk_ts(from, from->di_ctime); >> 188 >> 189 to->di_size = cpu_to_be64(from->di_size); >> 190 to->di_nblocks = cpu_to_be64(from->di_nblocks); >> 191 to->di_extsize = cpu_to_be32(from->di_extsize); >> 192 to->di_forkoff = from->di_forkoff; >> 193 to->di_aformat = from->di_aformat; >> 194 to->di_dmevmask = cpu_to_be32(from->di_dmevmask); >> 195 to->di_dmstate = cpu_to_be16(from->di_dmstate); >> 196 to->di_flags = cpu_to_be16(from->di_flags); >> 197 to->di_gen = cpu_to_be32(from->di_gen); >> 198 >> 199 if (from->di_version == 3) { >> 200 to->di_changecount = cpu_to_be64(from->di_changecount); >> 201 to->di_crtime = xfs_log_dinode_to_disk_ts(from, >> 202 from->di_crtime); >> 203 to->di_flags2 = cpu_to_be64(from->di_flags2); >> 204 to->di_cowextsize = cpu_to_be32(from->di_cowextsize); >> 205 to->di_ino = cpu_to_be64(from->di_ino); >> 206 to->di_lsn = cpu_to_be64(lsn); >> 207 memcpy(to->di_pad2, from->di_pad2, sizeof(to->di_pad2)); >> 208 uuid_copy(&to->di_uuid, &from->di_uuid); >> > 209 to->di_v3_pad = from->di_v3_pad; > > Why not just explicitly write zero to the di_v3_pad field? > Yes, We can do that since the call to xfs_log_dinode_to_disk_iext_counters() will update the values of union members correctly for v3 inodes with large extent count feature enabled. >> 210 } else { >> 211 to->di_flushiter = cpu_to_be16(from->di_flushiter); >> 212 memcpy(to->di_v2_pad, from->di_v2_pad, sizeof(to->di_v2_pad)); > > Same here? > This field too can be set to zeroes explicitly. -- chandan
WARNING: multiple messages have this Message-ID (diff)
From: Chandan Babu R <chandan.babu@oracle.com> To: kbuild-all@lists.01.org Subject: Re: [PATCH V9 14/19] xfs: Introduce per-inode 64-bit extent counters Date: Thu, 07 Apr 2022 13:48:55 +0530 [thread overview] Message-ID: <87ilrlxq4w.fsf@debian-BULLSEYE-live-builder-AMD64> (raw) In-Reply-To: <20220407010737.GD1544202@dread.disaster.area> [-- Attachment #1: Type: text/plain, Size: 4785 bytes --] On 07 Apr 2022 at 06:37, Dave Chinner wrote: > On Thu, Apr 07, 2022 at 03:03:32AM +0800, kernel test robot wrote: >> Hi Chandan, >> >> Thank you for the patch! Perhaps something to improve: >> >> [auto build test WARNING on xfs-linux/for-next] >> [also build test WARNING on v5.18-rc1 next-20220406] >> [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] >> >> url: https://github.com/intel-lab-lkp/linux/commits/Chandan-Babu-R/xfs-Extend-per-inode-extent-counters/20220406-174647 >> base: https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git for-next >> config: i386-randconfig-s002 (https://download.01.org/0day-ci/archive/20220407/202204070218.QyD2PQPx-lkp(a)intel.com/config) >> compiler: gcc-11 (Debian 11.2.0-19) 11.2.0 >> reproduce: >> # apt-get install sparse >> # sparse version: v0.6.4-dirty >> # https://github.com/intel-lab-lkp/linux/commit/28be4fd3f13d4ba2bcedceb8951cd3bfe852cba2 >> git remote add linux-review https://github.com/intel-lab-lkp/linux >> git fetch --no-tags linux-review Chandan-Babu-R/xfs-Extend-per-inode-extent-counters/20220406-174647 >> git checkout 28be4fd3f13d4ba2bcedceb8951cd3bfe852cba2 >> # save the config file to linux build tree >> mkdir build_dir >> make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash fs/xfs/ >> >> If you fix the issue, kindly add following tag as appropriate >> Reported-by: kernel test robot <lkp@intel.com> >> >> >> sparse warnings: (new ones prefixed by >>) >> >> fs/xfs/xfs_inode_item_recover.c:209:31: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __be64 [usertype] di_v3_pad @@ got unsigned long long [usertype] di_v3_pad @@ >> fs/xfs/xfs_inode_item_recover.c:209:31: sparse: expected restricted __be64 [usertype] di_v3_pad >> fs/xfs/xfs_inode_item_recover.c:209:31: sparse: got unsigned long long [usertype] di_v3_pad >> >> vim +209 fs/xfs/xfs_inode_item_recover.c >> >> 167 >> 168 STATIC void >> 169 xfs_log_dinode_to_disk( >> 170 struct xfs_log_dinode *from, >> 171 struct xfs_dinode *to, >> 172 xfs_lsn_t lsn) >> 173 { >> 174 to->di_magic = cpu_to_be16(from->di_magic); >> 175 to->di_mode = cpu_to_be16(from->di_mode); >> 176 to->di_version = from->di_version; >> 177 to->di_format = from->di_format; >> 178 to->di_onlink = 0; >> 179 to->di_uid = cpu_to_be32(from->di_uid); >> 180 to->di_gid = cpu_to_be32(from->di_gid); >> 181 to->di_nlink = cpu_to_be32(from->di_nlink); >> 182 to->di_projid_lo = cpu_to_be16(from->di_projid_lo); >> 183 to->di_projid_hi = cpu_to_be16(from->di_projid_hi); >> 184 >> 185 to->di_atime = xfs_log_dinode_to_disk_ts(from, from->di_atime); >> 186 to->di_mtime = xfs_log_dinode_to_disk_ts(from, from->di_mtime); >> 187 to->di_ctime = xfs_log_dinode_to_disk_ts(from, from->di_ctime); >> 188 >> 189 to->di_size = cpu_to_be64(from->di_size); >> 190 to->di_nblocks = cpu_to_be64(from->di_nblocks); >> 191 to->di_extsize = cpu_to_be32(from->di_extsize); >> 192 to->di_forkoff = from->di_forkoff; >> 193 to->di_aformat = from->di_aformat; >> 194 to->di_dmevmask = cpu_to_be32(from->di_dmevmask); >> 195 to->di_dmstate = cpu_to_be16(from->di_dmstate); >> 196 to->di_flags = cpu_to_be16(from->di_flags); >> 197 to->di_gen = cpu_to_be32(from->di_gen); >> 198 >> 199 if (from->di_version == 3) { >> 200 to->di_changecount = cpu_to_be64(from->di_changecount); >> 201 to->di_crtime = xfs_log_dinode_to_disk_ts(from, >> 202 from->di_crtime); >> 203 to->di_flags2 = cpu_to_be64(from->di_flags2); >> 204 to->di_cowextsize = cpu_to_be32(from->di_cowextsize); >> 205 to->di_ino = cpu_to_be64(from->di_ino); >> 206 to->di_lsn = cpu_to_be64(lsn); >> 207 memcpy(to->di_pad2, from->di_pad2, sizeof(to->di_pad2)); >> 208 uuid_copy(&to->di_uuid, &from->di_uuid); >> > 209 to->di_v3_pad = from->di_v3_pad; > > Why not just explicitly write zero to the di_v3_pad field? > Yes, We can do that since the call to xfs_log_dinode_to_disk_iext_counters() will update the values of union members correctly for v3 inodes with large extent count feature enabled. >> 210 } else { >> 211 to->di_flushiter = cpu_to_be16(from->di_flushiter); >> 212 memcpy(to->di_v2_pad, from->di_v2_pad, sizeof(to->di_v2_pad)); > > Same here? > This field too can be set to zeroes explicitly. -- chandan
next prev parent reply other threads:[~2022-04-07 8:19 UTC|newest] Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-06 6:18 [PATCH V9 00/19] xfs: Extend per-inode extent counters Chandan Babu R 2022-04-06 6:18 ` [PATCH V9 01/19] xfs: Move extent count limits to xfs_format.h Chandan Babu R 2022-04-06 6:18 ` [PATCH V9 02/19] xfs: Define max extent length based on on-disk format definition Chandan Babu R 2022-04-06 6:18 ` [PATCH V9 03/19] xfs: Introduce xfs_iext_max_nextents() helper Chandan Babu R 2022-04-06 6:18 ` [PATCH V9 04/19] xfs: Use xfs_extnum_t instead of basic data types Chandan Babu R 2022-04-06 6:18 ` [PATCH V9 05/19] xfs: Introduce xfs_dfork_nextents() helper Chandan Babu R 2022-04-06 6:18 ` [PATCH V9 06/19] xfs: Use basic types to define xfs_log_dinode's di_nextents and di_anextents Chandan Babu R 2022-04-06 6:18 ` [PATCH V9 07/19] xfs: Promote xfs_extnum_t and xfs_aextnum_t to 64 and 32-bits respectively Chandan Babu R 2022-04-06 6:18 ` [PATCH V9 08/19] xfs: Introduce XFS_SB_FEAT_INCOMPAT_NREXT64 and associated per-fs feature bit Chandan Babu R 2022-04-07 0:50 ` Dave Chinner 2022-04-06 6:18 ` [PATCH V9 09/19] xfs: Introduce XFS_FSOP_GEOM_FLAGS_NREXT64 Chandan Babu R 2022-04-06 6:18 ` [PATCH V9 10/19] xfs: Introduce XFS_DIFLAG2_NREXT64 and associated helpers Chandan Babu R 2022-04-06 6:18 ` [PATCH V9 11/19] xfs: Use uint64_t to count maximum blocks that can be used by BMBT Chandan Babu R 2022-04-07 0:52 ` Dave Chinner 2022-04-06 6:18 ` [PATCH V9 12/19] xfs: Introduce macros to represent new maximum extent counts for data/attr forks Chandan Babu R 2022-04-07 1:05 ` Dave Chinner 2022-04-07 1:58 ` Darrick J. Wong 2022-04-07 2:44 ` Dave Chinner 2022-04-07 8:18 ` Chandan Babu R 2022-04-07 8:56 ` Dave Chinner 2022-04-07 8:18 ` Chandan Babu R 2022-04-06 6:18 ` [PATCH V9 13/19] xfs: Replace numbered inode recovery error messages with descriptive ones Chandan Babu R 2022-04-07 1:50 ` Darrick J. Wong 2022-04-06 6:18 ` [PATCH V9 14/19] xfs: Introduce per-inode 64-bit extent counters Chandan Babu R 2022-04-06 19:03 ` kernel test robot 2022-04-07 1:07 ` Dave Chinner 2022-04-07 1:07 ` Dave Chinner 2022-04-07 8:18 ` Chandan Babu R [this message] 2022-04-07 8:18 ` Chandan Babu R 2022-04-06 6:18 ` [PATCH V9 15/19] xfs: Directory's data fork extent counter can never overflow Chandan Babu R 2022-04-07 1:13 ` Dave Chinner 2022-04-07 1:48 ` Darrick J. Wong 2022-04-07 8:19 ` Chandan Babu R 2022-04-09 13:47 ` [PATCH V9.1] " Chandan Babu R 2022-04-11 1:33 ` Dave Chinner 2022-04-11 22:07 ` Darrick J. Wong 2022-04-12 3:39 ` Chandan Babu R 2022-04-12 14:02 ` [PATCH V9.2] " Chandan Babu R 2022-04-12 17:04 ` Darrick J. Wong 2022-04-06 6:19 ` [PATCH V9 16/19] xfs: Conditionally upgrade existing inodes to use large extent counters Chandan Babu R 2022-04-07 1:22 ` Dave Chinner 2022-04-07 1:46 ` Darrick J. Wong 2022-04-07 8:19 ` Chandan Babu R 2022-04-07 1:46 ` Darrick J. Wong 2022-04-07 2:00 ` Darrick J. Wong 2022-04-07 8:19 ` Chandan Babu R 2022-04-09 13:52 ` [PATCH V9.1] " Chandan Babu R 2022-04-11 1:34 ` Dave Chinner 2022-04-06 6:19 ` [PATCH V9 17/19] xfs: Decouple XFS_IBULK flags from XFS_IWALK flags Chandan Babu R 2022-04-07 1:29 ` Darrick J. Wong 2022-04-06 6:19 ` [PATCH V9 18/19] xfs: Enable bulkstat ioctl to support 64-bit per-inode extent counters Chandan Babu R 2022-04-07 1:29 ` Darrick J. Wong 2022-04-07 1:42 ` Dave Chinner 2022-04-07 8:20 ` Chandan Babu R 2022-04-09 13:57 ` [PATCH V9.1] " Chandan Babu R 2022-04-11 2:56 ` Dave Chinner 2022-04-13 2:57 ` Darrick J. Wong 2022-04-13 7:48 ` Chandan Babu R 2022-04-06 6:19 ` [PATCH V9 19/19] xfs: Add XFS_SB_FEAT_INCOMPAT_NREXT64 to the list of supported flags Chandan Babu R 2022-04-07 1:23 ` Dave Chinner 2022-04-07 1:26 ` Darrick J. Wong 2022-04-09 13:23 ` [PATCH V9.1] xfs: Introduce macros to represent new maximum extent counts for data/attr forks Chandan Babu R
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=87ilrlxq4w.fsf@debian-BULLSEYE-live-builder-AMD64 \ --to=chandan.babu@oracle.com \ --cc=david@fromorbit.com \ --cc=dchinner@redhat.com \ --cc=djwong@kernel.org \ --cc=kbuild-all@lists.01.org \ --cc=linux-xfs@vger.kernel.org \ --cc=lkp@intel.com \ /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.