From: kernel test robot <lkp@intel.com> To: Naohiro Aota <naohiro.aota@wdc.com>, Josef Bacik <josef@toxicpanda.com>, David Sterba <dsterba@suse.com> Cc: clang-built-linux@googlegroups.com, kbuild-all@lists.01.org, linux-btrfs@vger.kernel.org, Naohiro Aota <naohiro.aota@wdc.com> Subject: Re: [PATCH 16/17] btrfs: zoned: finish fully written block group Date: Thu, 12 Aug 2021 02:37:05 +0800 [thread overview] Message-ID: <202108120234.MkEMU4Zp-lkp@intel.com> (raw) In-Reply-To: <59c069e3890f3cbc7fa425cdcf756d241a8bfc92.1628690222.git.naohiro.aota@wdc.com> [-- Attachment #1: Type: text/plain, Size: 3615 bytes --] Hi Naohiro, I love your patch! Perhaps something to improve: [auto build test WARNING on kdave/for-next] [cannot apply to v5.14-rc5 next-20210811] [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/0day-ci/linux/commits/Naohiro-Aota/ZNS-Support-for-Btrfs/20210811-222302 base: https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-next config: x86_64-randconfig-a012-20210810 (attached as .config) compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project d39ebdae674c8efc84ebe8dc32716ec353220530) reproduce (this is a W=1 build): wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross # https://github.com/0day-ci/linux/commit/ccecd271dc2436fe587af8d2083c3c96ab86e309 git remote add linux-review https://github.com/0day-ci/linux git fetch --no-tags linux-review Naohiro-Aota/ZNS-Support-for-Btrfs/20210811-222302 git checkout ccecd271dc2436fe587af8d2083c3c96ab86e309 # save the attached .config to linux build tree COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64 If you fix the issue, kindly add following tag as appropriate Reported-by: kernel test robot <lkp@intel.com> All warnings (new ones prefixed by >>): >> fs/btrfs/zoned.c:1940:6: warning: variable 'ret' is used uninitialized whenever 'if' condition is false [-Wsometimes-uninitialized] if (!device->zone_info->max_active_zones) { ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ fs/btrfs/zoned.c:1956:9: note: uninitialized use occurs here return ret; ^~~ fs/btrfs/zoned.c:1940:2: note: remove the 'if' if its condition is always true if (!device->zone_info->max_active_zones) { ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ fs/btrfs/zoned.c:1908:9: note: initialize the variable 'ret' to silence this warning int ret; ^ = 0 1 warning generated. vim +1940 fs/btrfs/zoned.c 1900 1901 int btrfs_zone_finish_endio(struct btrfs_fs_info *fs_info, u64 logical, 1902 u64 length) 1903 { 1904 struct btrfs_block_group *block_group; 1905 struct map_lookup *map; 1906 struct btrfs_device *device; 1907 u64 physical; 1908 int ret; 1909 1910 if (!btrfs_is_zoned(fs_info)) 1911 return 0; 1912 1913 block_group = btrfs_lookup_block_group(fs_info, logical); 1914 ASSERT(block_group); 1915 1916 if (logical + length < block_group->start + block_group->zone_capacity) { 1917 ret = 0; 1918 goto out; 1919 } 1920 1921 spin_lock(&block_group->lock); 1922 1923 if (!block_group->zone_is_active) { 1924 spin_unlock(&block_group->lock); 1925 ret = 0; 1926 goto out; 1927 } 1928 1929 block_group->zone_is_active = 0; 1930 /* We should have consumed all the free space */ 1931 ASSERT(block_group->alloc_offset == block_group->zone_capacity); 1932 ASSERT(block_group->free_space_ctl->free_space == 0); 1933 btrfs_clear_treelog_bg(block_group); 1934 spin_unlock(&block_group->lock); 1935 1936 map = block_group->physical_map; 1937 device = map->stripes[0].dev; 1938 physical = map->stripes[0].physical; 1939 > 1940 if (!device->zone_info->max_active_zones) { --- 0-DAY CI Kernel Test Service, Intel Corporation https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org [-- Attachment #2: .config.gz --] [-- Type: application/gzip, Size: 35768 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com> To: kbuild-all@lists.01.org Subject: Re: [PATCH 16/17] btrfs: zoned: finish fully written block group Date: Thu, 12 Aug 2021 02:37:05 +0800 [thread overview] Message-ID: <202108120234.MkEMU4Zp-lkp@intel.com> (raw) In-Reply-To: <59c069e3890f3cbc7fa425cdcf756d241a8bfc92.1628690222.git.naohiro.aota@wdc.com> [-- Attachment #1: Type: text/plain, Size: 3709 bytes --] Hi Naohiro, I love your patch! Perhaps something to improve: [auto build test WARNING on kdave/for-next] [cannot apply to v5.14-rc5 next-20210811] [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/0day-ci/linux/commits/Naohiro-Aota/ZNS-Support-for-Btrfs/20210811-222302 base: https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-next config: x86_64-randconfig-a012-20210810 (attached as .config) compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project d39ebdae674c8efc84ebe8dc32716ec353220530) reproduce (this is a W=1 build): wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross # https://github.com/0day-ci/linux/commit/ccecd271dc2436fe587af8d2083c3c96ab86e309 git remote add linux-review https://github.com/0day-ci/linux git fetch --no-tags linux-review Naohiro-Aota/ZNS-Support-for-Btrfs/20210811-222302 git checkout ccecd271dc2436fe587af8d2083c3c96ab86e309 # save the attached .config to linux build tree COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64 If you fix the issue, kindly add following tag as appropriate Reported-by: kernel test robot <lkp@intel.com> All warnings (new ones prefixed by >>): >> fs/btrfs/zoned.c:1940:6: warning: variable 'ret' is used uninitialized whenever 'if' condition is false [-Wsometimes-uninitialized] if (!device->zone_info->max_active_zones) { ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ fs/btrfs/zoned.c:1956:9: note: uninitialized use occurs here return ret; ^~~ fs/btrfs/zoned.c:1940:2: note: remove the 'if' if its condition is always true if (!device->zone_info->max_active_zones) { ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ fs/btrfs/zoned.c:1908:9: note: initialize the variable 'ret' to silence this warning int ret; ^ = 0 1 warning generated. vim +1940 fs/btrfs/zoned.c 1900 1901 int btrfs_zone_finish_endio(struct btrfs_fs_info *fs_info, u64 logical, 1902 u64 length) 1903 { 1904 struct btrfs_block_group *block_group; 1905 struct map_lookup *map; 1906 struct btrfs_device *device; 1907 u64 physical; 1908 int ret; 1909 1910 if (!btrfs_is_zoned(fs_info)) 1911 return 0; 1912 1913 block_group = btrfs_lookup_block_group(fs_info, logical); 1914 ASSERT(block_group); 1915 1916 if (logical + length < block_group->start + block_group->zone_capacity) { 1917 ret = 0; 1918 goto out; 1919 } 1920 1921 spin_lock(&block_group->lock); 1922 1923 if (!block_group->zone_is_active) { 1924 spin_unlock(&block_group->lock); 1925 ret = 0; 1926 goto out; 1927 } 1928 1929 block_group->zone_is_active = 0; 1930 /* We should have consumed all the free space */ 1931 ASSERT(block_group->alloc_offset == block_group->zone_capacity); 1932 ASSERT(block_group->free_space_ctl->free_space == 0); 1933 btrfs_clear_treelog_bg(block_group); 1934 spin_unlock(&block_group->lock); 1935 1936 map = block_group->physical_map; 1937 device = map->stripes[0].dev; 1938 physical = map->stripes[0].physical; 1939 > 1940 if (!device->zone_info->max_active_zones) { --- 0-DAY CI Kernel Test Service, Intel Corporation https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org [-- Attachment #2: config.gz --] [-- Type: application/gzip, Size: 35768 bytes --]
next prev parent reply other threads:[~2021-08-11 18:37 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-11 14:16 [PATCH 00/17] ZNS Support for Btrfs Naohiro Aota 2021-08-11 14:16 ` [PATCH 01/17] btrfs: zoned: load zone capacity information from devices Naohiro Aota 2021-08-11 14:16 ` [PATCH 02/17] btrfs: zoned: move btrfs_free_excluded_extents out from btrfs_calc_zone_unusable Naohiro Aota 2021-08-11 14:16 ` [PATCH 03/17] btrfs: zoned: calculate free space from zone capacity Naohiro Aota 2021-08-11 14:16 ` [PATCH 04/17] btrfs: zoned: tweak reclaim threshold for " Naohiro Aota 2021-08-11 14:16 ` [PATCH 05/17] btrfs: zoned: consider zone as full when no more SB can be written Naohiro Aota 2021-08-11 14:16 ` [PATCH 06/17] btrfs: zoned: locate superblock position using zone capacity Naohiro Aota 2021-08-11 14:16 ` [PATCH 07/17] btrfs: zoned: finish superblock zone once no space left for new SB Naohiro Aota 2021-08-11 14:16 ` [PATCH 08/17] btrfs: zoned: load active zone information from devices Naohiro Aota 2021-08-11 14:16 ` [PATCH 09/17] btrfs: zoned: introduce physical_map to btrfs_block_group Naohiro Aota 2021-08-11 14:16 ` [PATCH 10/17] btrfs: zoned: implement active zone tracking Naohiro Aota 2021-08-11 14:16 ` [PATCH 11/17] btrfs: zoned: load active zone info for block group Naohiro Aota 2021-08-11 14:16 ` [PATCH 12/17] btrfs: zoned: activate block group on allocation Naohiro Aota 2021-08-11 14:16 ` [PATCH 13/17] btrfs: zoned: activate new block group Naohiro Aota 2021-08-11 14:16 ` [PATCH 14/17] btrfs: move ffe_ctl one level up Naohiro Aota 2021-08-11 14:16 ` [PATCH 15/17] btrfs: zoned: avoid chunk allocation if active block group has enough space Naohiro Aota 2021-08-11 14:16 ` [PATCH 16/17] btrfs: zoned: finish fully written block group Naohiro Aota 2021-08-11 17:26 ` kernel test robot 2021-08-11 17:26 ` kernel test robot 2021-08-16 4:34 ` Naohiro Aota 2021-08-16 4:34 ` Naohiro Aota 2021-08-11 18:37 ` kernel test robot [this message] 2021-08-11 18:37 ` kernel test robot 2021-08-11 14:16 ` [PATCH 17/17] btrfs: zoned: finish relocating " Naohiro Aota 2021-08-11 22:09 [PATCH 16/17] btrfs: zoned: finish fully written " kernel test robot
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=202108120234.MkEMU4Zp-lkp@intel.com \ --to=lkp@intel.com \ --cc=clang-built-linux@googlegroups.com \ --cc=dsterba@suse.com \ --cc=josef@toxicpanda.com \ --cc=kbuild-all@lists.01.org \ --cc=linux-btrfs@vger.kernel.org \ --cc=naohiro.aota@wdc.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.