From: kernel test robot <lkp@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
linux-f2fs-devel@lists.sourceforge.net,
oe-kbuild-all@lists.linux.dev
Subject: [f2fs-dev] [jaegeuk-f2fs:dev-test 5/6] fs/f2fs/super.c:1563:23: error: 'struct f2fs_dev_info' has no member named 'blkz_seq'
Date: Tue, 11 Jul 2023 05:02:35 +0800 [thread overview]
Message-ID: <202307110435.0H8FQZZW-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git dev-test
head: d73b38253cda925126fc85e32277fbe2f1b100bf
commit: 2031cbae1532cadb0838ebc1fecbfd14698b5a0a [5/6] f2fs: don't reopen the main block device in f2fs_scan_devices
config: alpha-randconfig-r021-20230710 (https://download.01.org/0day-ci/archive/20230711/202307110435.0H8FQZZW-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230711/202307110435.0H8FQZZW-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202307110435.0H8FQZZW-lkp@intel.com/
All errors (new ones prefixed by >>):
fs/f2fs/super.c: In function 'destroy_device_list':
>> fs/f2fs/super.c:1563:23: error: 'struct f2fs_dev_info' has no member named 'blkz_seq'
1563 | kvfree(FDEV(0).blkz_seq);
| ^
vim +1563 fs/f2fs/super.c
1558
1559 static void destroy_device_list(struct f2fs_sb_info *sbi)
1560 {
1561 int i;
1562
> 1563 kvfree(FDEV(0).blkz_seq);
1564 for (i = 1; i < sbi->s_ndevs; i++) {
1565 blkdev_put(FDEV(i).bdev, sbi->sb->s_type);
1566 #ifdef CONFIG_BLK_DEV_ZONED
1567 kvfree(FDEV(i).blkz_seq);
1568 #endif
1569 }
1570 kvfree(sbi->devs);
1571 }
1572
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
reply other threads:[~2023-07-10 21:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202307110435.0H8FQZZW-lkp@intel.com \
--to=lkp@intel.com \
--cc=hch@lst.de \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=oe-kbuild-all@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).