mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Chao Yu <yuchao0@huawei.com>
Cc: kbuild-all@lists.01.org, jaegeuk@kernel.org,
	linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, chao@kernel.org,
	Chao Yu <yuchao0@huawei.com>
Subject: Re: [PATCH 3/3] Revert "f2fs: use kvmalloc, if kmalloc is failed"
Date: Sat, 2 Nov 2019 22:17:10 +0800	[thread overview]
Message-ID: <201911022233.zTMqGPBr%lkp@intel.com> (raw)
In-Reply-To: <20191101095324.9902-3-yuchao0@huawei.com>

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

Hi Chao,

I love your patch! Yet something to improve:

[auto build test ERROR on f2fs/dev-test]
[cannot apply to v5.4-rc5 next-20191031]
[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/Chao-Yu/f2fs-clean-up-check-condition-for-writting-beyond-EOF/20191102-212408
base:   https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git dev-test
config: sparc64-allmodconfig (attached as .config)
compiler: sparc64-linux-gcc (GCC) 7.4.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        GCC_VERSION=7.4.0 make.cross ARCH=sparc64 

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

All errors (new ones prefixed by >>):

   fs/f2fs/super.c: In function 'destroy_device_list':
>> fs/f2fs/super.c:1055:17: error: 'struct f2fs_dev_info' has no member named 'blkz_type'; did you mean 'blkz_seq'?
      kfree(FDEV(i).blkz_type);
                    ^~~~~~~~~
                    blkz_seq

vim +1055 fs/f2fs/super.c

  1047	
  1048	static void destroy_device_list(struct f2fs_sb_info *sbi)
  1049	{
  1050		int i;
  1051	
  1052		for (i = 0; i < sbi->s_ndevs; i++) {
  1053			blkdev_put(FDEV(i).bdev, FMODE_EXCL);
  1054	#ifdef CONFIG_BLK_DEV_ZONED
> 1055			kfree(FDEV(i).blkz_type);
  1056	#endif
  1057		}
  1058		kfree(sbi->devs);
  1059	}
  1060	

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 59107 bytes --]

  reply	other threads:[~2019-11-02 14:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-01  9:53 [PATCH 1/3] f2fs: clean up check condition for writting beyond EOF Chao Yu
2019-11-01  9:53 ` [PATCH 2/3] f2fs: show f2fs instance in printk_ratelimited Chao Yu
2019-11-01  9:53 ` [PATCH 3/3] Revert "f2fs: use kvmalloc, if kmalloc is failed" Chao Yu
2019-11-02 14:17   ` kbuild test robot [this message]
2019-11-04  8:03     ` Chao Yu
2019-11-05  0:02   ` Jaegeuk Kim
2019-11-05  2:17     ` Chao Yu
2019-11-05  2:38       ` Eric Biggers
2019-11-05  2:49         ` Chao Yu
2019-11-05  3:04           ` Jaegeuk Kim

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=201911022233.zTMqGPBr%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yuchao0@huawei.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: 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

Powered by JetHome