From: kernel test robot <lkp@intel.com>
To: Chao Yu <yuchao0@huawei.com>, Chao Yu <chao@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, Chao Yu <yuchao0@huawei.com>,
Chao Yu <chao@kernel.org>
Subject: [chao:wip 4/4] fs/f2fs/data.c:615:61: error: 'struct f2fs_bio_info' has no member named 'zone_wait'
Date: Mon, 18 Mar 2024 03:00:47 +0800 [thread overview]
Message-ID: <202403180211.RyitU8RO-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git wip
head: 5d1d1ce6987e9ad0cf26ca1071a94aadbb5c2a83
commit: 5d1d1ce6987e9ad0cf26ca1071a94aadbb5c2a83 [4/4] f2fs: zone: don't block IO if there is remained open zone
config: sh-allmodconfig (https://download.01.org/0day-ci/archive/20240318/202403180211.RyitU8RO-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240318/202403180211.RyitU8RO-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/202403180211.RyitU8RO-lkp@intel.com/
All errors (new ones prefixed by >>):
fs/f2fs/data.c: In function 'f2fs_init_write_merge_io':
>> fs/f2fs/data.c:615:61: error: 'struct f2fs_bio_info' has no member named 'zone_wait'
615 | init_completion(&sbi->write_io[i][j].zone_wait);
| ^
>> fs/f2fs/data.c:616:44: error: 'struct f2fs_bio_info' has no member named 'zone_pending_bio'
616 | sbi->write_io[i][j].zone_pending_bio = NULL;
| ^
vim +615 fs/f2fs/data.c
0fd785eb931d25 Chao Yu 2016-01-18 591
908ea6541661d7 Yufen Yu 2022-05-25 592 int f2fs_init_write_merge_io(struct f2fs_sb_info *sbi)
908ea6541661d7 Yufen Yu 2022-05-25 593 {
908ea6541661d7 Yufen Yu 2022-05-25 594 int i;
908ea6541661d7 Yufen Yu 2022-05-25 595
908ea6541661d7 Yufen Yu 2022-05-25 596 for (i = 0; i < NR_PAGE_TYPE; i++) {
908ea6541661d7 Yufen Yu 2022-05-25 597 int n = (i == META) ? 1 : NR_TEMP_TYPE;
908ea6541661d7 Yufen Yu 2022-05-25 598 int j;
908ea6541661d7 Yufen Yu 2022-05-25 599
908ea6541661d7 Yufen Yu 2022-05-25 600 sbi->write_io[i] = f2fs_kmalloc(sbi,
908ea6541661d7 Yufen Yu 2022-05-25 601 array_size(n, sizeof(struct f2fs_bio_info)),
908ea6541661d7 Yufen Yu 2022-05-25 602 GFP_KERNEL);
908ea6541661d7 Yufen Yu 2022-05-25 603 if (!sbi->write_io[i])
908ea6541661d7 Yufen Yu 2022-05-25 604 return -ENOMEM;
908ea6541661d7 Yufen Yu 2022-05-25 605
908ea6541661d7 Yufen Yu 2022-05-25 606 for (j = HOT; j < n; j++) {
908ea6541661d7 Yufen Yu 2022-05-25 607 init_f2fs_rwsem(&sbi->write_io[i][j].io_rwsem);
908ea6541661d7 Yufen Yu 2022-05-25 608 sbi->write_io[i][j].sbi = sbi;
908ea6541661d7 Yufen Yu 2022-05-25 609 sbi->write_io[i][j].bio = NULL;
908ea6541661d7 Yufen Yu 2022-05-25 610 spin_lock_init(&sbi->write_io[i][j].io_lock);
908ea6541661d7 Yufen Yu 2022-05-25 611 INIT_LIST_HEAD(&sbi->write_io[i][j].io_list);
908ea6541661d7 Yufen Yu 2022-05-25 612 INIT_LIST_HEAD(&sbi->write_io[i][j].bio_list);
908ea6541661d7 Yufen Yu 2022-05-25 613 init_f2fs_rwsem(&sbi->write_io[i][j].bio_list_lock);
e067dc3c6b9c41 Daeho Jeong 2023-05-03 614 #ifdef CONFIG_BLK_DEV_ZONED
e067dc3c6b9c41 Daeho Jeong 2023-05-03 @615 init_completion(&sbi->write_io[i][j].zone_wait);
e067dc3c6b9c41 Daeho Jeong 2023-05-03 @616 sbi->write_io[i][j].zone_pending_bio = NULL;
e067dc3c6b9c41 Daeho Jeong 2023-05-03 617 sbi->write_io[i][j].bi_private = NULL;
e067dc3c6b9c41 Daeho Jeong 2023-05-03 618 #endif
908ea6541661d7 Yufen Yu 2022-05-25 619 }
908ea6541661d7 Yufen Yu 2022-05-25 620 }
908ea6541661d7 Yufen Yu 2022-05-25 621
908ea6541661d7 Yufen Yu 2022-05-25 622 return 0;
908ea6541661d7 Yufen Yu 2022-05-25 623 }
908ea6541661d7 Yufen Yu 2022-05-25 624
:::::: The code at line 615 was first introduced by commit
:::::: e067dc3c6b9c419bac43c6a0be2d85f44681f863 f2fs: maintain six open zones for zoned devices
:::::: TO: Daeho Jeong <daehojeong@google.com>
:::::: CC: Jaegeuk Kim <jaegeuk@kernel.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-03-17 19:01 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=202403180211.RyitU8RO-lkp@intel.com \
--to=lkp@intel.com \
--cc=chao@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--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 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.