Linux-Fsdevel Archive on lore.kernel.org
help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Aravind Ramesh <aravind.ramesh@wdc.com>,
	jaegeuk@kernel.org, yuchao0@huawei.com,
	linux-fsdevel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net, hch@lst.de
Cc: kbuild-all@lists.01.org, Damien.LeMoal@wdc.com,
	niklas.cassel@wdc.com, matias.bjorling@wdc.com,
	Aravind Ramesh <aravind.ramesh@wdc.com>
Subject: Re: [PATCH 1/2] f2fs: support zone capacity less than zone size
Date: Fri, 3 Jul 2020 06:09:51 +0800	[thread overview]
Message-ID: <202007030626.nfIX24Ji%lkp@intel.com> (raw)
In-Reply-To: <20200702155401.13322-2-aravind.ramesh@wdc.com>

[-- Attachment #1: Type: text/plain, Size: 2093 bytes --]

Hi Aravind,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on f2fs/dev-test]
[also build test ERROR on next-20200702]
[cannot apply to v5.8-rc3]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use  as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Aravind-Ramesh/f2fs-zns-zone-capacity-support/20200702-235735
base:   https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git dev-test
config: x86_64-rhel-7.6 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-14) 9.3.0
reproduce (this is a W=1 build):
        # save the attached .config to linux build tree
        make W=1 ARCH=x86_64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   fs/f2fs/super.c: In function 'f2fs_report_zone_cb':
>> fs/f2fs/super.c:3058:48: error: 'struct blk_zone' has no member named 'capacity'
    3058 |  rz_args->dev->zone_capacity_blocks[idx] = zone->capacity >>
         |                                                ^~
   fs/f2fs/super.c:3060:23: error: 'struct blk_zone' has no member named 'capacity'
    3060 |  if (zone->len != zone->capacity && !rz_args->zone_cap_mismatch)
         |                       ^~

vim +3058 fs/f2fs/super.c

  3048	
  3049	static int f2fs_report_zone_cb(struct blk_zone *zone, unsigned int idx,
  3050				      void *data)
  3051	{
  3052		struct f2fs_report_zones_args *rz_args = data;
  3053	
  3054		if (zone->type == BLK_ZONE_TYPE_CONVENTIONAL)
  3055			return 0;
  3056	
  3057		set_bit(idx, rz_args->dev->blkz_seq);
> 3058		rz_args->dev->zone_capacity_blocks[idx] = zone->capacity >>
  3059							F2FS_LOG_SECTORS_PER_BLOCK;
  3060		if (zone->len != zone->capacity && !rz_args->zone_cap_mismatch)
  3061			rz_args->zone_cap_mismatch = true;
  3062	
  3063		return 0;
  3064	}
  3065	

---
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: 49253 bytes --]

  reply	other threads:[~2020-07-02 22:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02 15:53 [PATCH 0/2] f2fs: zns zone-capacity support Aravind Ramesh
2020-07-02 15:54 ` [PATCH 1/2] f2fs: support zone capacity less than zone size Aravind Ramesh
2020-07-02 22:09   ` kernel test robot [this message]
2020-07-02 23:27   ` kernel test robot
2020-07-07  0:07   ` Jaegeuk Kim
2020-07-07  3:27     ` Aravind Ramesh
2020-07-07  3:49       ` Jaegeuk Kim
2020-07-07  5:18         ` Aravind Ramesh
2020-07-07 12:18   ` Chao Yu
2020-07-07 18:23     ` Aravind Ramesh
2020-07-08  2:33       ` Chao Yu
2020-07-08 13:04         ` Aravind Ramesh
2020-07-09  2:55           ` Chao Yu
2020-07-09  5:31             ` Aravind Ramesh
2020-07-09  7:05               ` Chao Yu
2020-07-09  7:11                 ` Aravind Ramesh
2020-07-10 17:44                   ` Aravind Ramesh
2020-07-02 15:54 ` [PATCH 2/2] f2fs: manage zone capacity during writes and gc Aravind Ramesh

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=202007030626.nfIX24Ji%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Damien.LeMoal@wdc.com \
    --cc=aravind.ramesh@wdc.com \
    --cc=hch@lst.de \
    --cc=jaegeuk@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=matias.bjorling@wdc.com \
    --cc=niklas.cassel@wdc.com \
    --cc=yuchao0@huawei.com \
    --subject='Re: [PATCH 1/2] f2fs: support zone capacity less than zone size' \
    /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

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).