From: kernel test robot <lkp@intel.com>
To: Daejun Park <daejun7.park@samsung.com>,
"jaegeuk@kernel.org" <jaegeuk@kernel.org>,
"chao@kernel.org" <chao@kernel.org>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"mhiramat@kernel.org" <mhiramat@kernel.org>,
"linux-f2fs-devel@lists.sourceforge.net"
<linux-f2fs-devel@lists.sourceforge.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-trace-kernel@vger.kernel.org"
<linux-trace-kernel@vger.kernel.org>
Cc: Seokhwan Kim <sukka.kim@samsung.com>,
beomsu kim <beomsu7.kim@samsung.com>,
oe-kbuild-all@lists.linux.dev
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: add async reset zone command support
Date: Fri, 28 Apr 2023 14:16:15 +0800 [thread overview]
Message-ID: <202304281424.WrTeoZ4B-lkp@intel.com> (raw)
In-Reply-To: <20230428025646epcms2p35acbea45ee80d36808861edba8a3c84a@epcms2p3>
Hi Daejun,
kernel test robot noticed the following build errors:
[auto build test ERROR on jaegeuk-f2fs/dev-test]
[also build test ERROR on jaegeuk-f2fs/dev linus/master next-20230427]
[cannot apply to v6.3]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Daejun-Park/f2fs-add-async-reset-zone-command-support/20230428-105944
base: https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git dev-test
patch link: https://lore.kernel.org/r/20230428025646epcms2p35acbea45ee80d36808861edba8a3c84a%40epcms2p3
patch subject: [PATCH v3] f2fs: add async reset zone command support
config: microblaze-randconfig-r024-20230427 (https://download.01.org/0day-ci/archive/20230428/202304281424.WrTeoZ4B-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 12.1.0
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/intel-lab-lkp/linux/commit/2f3e641e3de509a5ed879fb10fdf3377fd9ca0d9
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Daejun-Park/f2fs-add-async-reset-zone-command-support/20230428-105944
git checkout 2f3e641e3de509a5ed879fb10fdf3377fd9ca0d9
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=microblaze olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=microblaze SHELL=/bin/bash fs/f2fs/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202304281424.WrTeoZ4B-lkp@intel.com/
All errors (new ones prefixed by >>):
fs/f2fs/segment.c: In function 'f2fs_wait_discard_bio':
>> fs/f2fs/segment.c:1789:33: error: implicit declaration of function '__submit_zone_reset_cmd' [-Werror=implicit-function-declaration]
1789 | __submit_zone_reset_cmd(sbi, dc, REQ_SYNC,
| ^~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/__submit_zone_reset_cmd +1789 fs/f2fs/segment.c
1775
1776 /* This should be covered by global mutex, &sit_i->sentry_lock */
1777 static void f2fs_wait_discard_bio(struct f2fs_sb_info *sbi, block_t blkaddr)
1778 {
1779 struct discard_cmd_control *dcc = SM_I(sbi)->dcc_info;
1780 struct discard_cmd *dc;
1781 bool need_wait = false;
1782
1783 mutex_lock(&dcc->cmd_lock);
1784 dc = __lookup_discard_cmd(sbi, blkaddr);
1785 if (dc) {
1786 if (f2fs_sb_has_blkzoned(sbi) && bdev_is_zoned(dc->bdev)) {
1787 /* force submit zone reset */
1788 if (dc->state == D_PREP)
> 1789 __submit_zone_reset_cmd(sbi, dc, REQ_SYNC,
1790 &dcc->wait_list, NULL);
1791 dc->ref++;
1792 need_wait = true;
1793 } else {
1794 if (dc->state == D_PREP) {
1795 __punch_discard_cmd(sbi, dc, blkaddr);
1796 } else {
1797 dc->ref++;
1798 need_wait = true;
1799 }
1800 }
1801 }
1802 mutex_unlock(&dcc->cmd_lock);
1803
1804 if (need_wait)
1805 __wait_one_discard_bio(sbi, dc);
1806 }
1807
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Daejun Park <daejun7.park@samsung.com>,
"jaegeuk@kernel.org" <jaegeuk@kernel.org>,
"chao@kernel.org" <chao@kernel.org>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"mhiramat@kernel.org" <mhiramat@kernel.org>,
"linux-f2fs-devel@lists.sourceforge.net"
<linux-f2fs-devel@lists.sourceforge.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-trace-kernel@vger.kernel.org"
<linux-trace-kernel@vger.kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
Seokhwan Kim <sukka.kim@samsung.com>,
Yonggil Song <yonggil.song@samsung.com>,
beomsu kim <beomsu7.kim@samsung.com>,
Daejun Park <daejun7.park@samsung.com>
Subject: Re: [PATCH v3] f2fs: add async reset zone command support
Date: Fri, 28 Apr 2023 14:16:15 +0800 [thread overview]
Message-ID: <202304281424.WrTeoZ4B-lkp@intel.com> (raw)
In-Reply-To: <20230428025646epcms2p35acbea45ee80d36808861edba8a3c84a@epcms2p3>
Hi Daejun,
kernel test robot noticed the following build errors:
[auto build test ERROR on jaegeuk-f2fs/dev-test]
[also build test ERROR on jaegeuk-f2fs/dev linus/master next-20230427]
[cannot apply to v6.3]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Daejun-Park/f2fs-add-async-reset-zone-command-support/20230428-105944
base: https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git dev-test
patch link: https://lore.kernel.org/r/20230428025646epcms2p35acbea45ee80d36808861edba8a3c84a%40epcms2p3
patch subject: [PATCH v3] f2fs: add async reset zone command support
config: microblaze-randconfig-r024-20230427 (https://download.01.org/0day-ci/archive/20230428/202304281424.WrTeoZ4B-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 12.1.0
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/intel-lab-lkp/linux/commit/2f3e641e3de509a5ed879fb10fdf3377fd9ca0d9
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Daejun-Park/f2fs-add-async-reset-zone-command-support/20230428-105944
git checkout 2f3e641e3de509a5ed879fb10fdf3377fd9ca0d9
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=microblaze olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=microblaze SHELL=/bin/bash fs/f2fs/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202304281424.WrTeoZ4B-lkp@intel.com/
All errors (new ones prefixed by >>):
fs/f2fs/segment.c: In function 'f2fs_wait_discard_bio':
>> fs/f2fs/segment.c:1789:33: error: implicit declaration of function '__submit_zone_reset_cmd' [-Werror=implicit-function-declaration]
1789 | __submit_zone_reset_cmd(sbi, dc, REQ_SYNC,
| ^~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/__submit_zone_reset_cmd +1789 fs/f2fs/segment.c
1775
1776 /* This should be covered by global mutex, &sit_i->sentry_lock */
1777 static void f2fs_wait_discard_bio(struct f2fs_sb_info *sbi, block_t blkaddr)
1778 {
1779 struct discard_cmd_control *dcc = SM_I(sbi)->dcc_info;
1780 struct discard_cmd *dc;
1781 bool need_wait = false;
1782
1783 mutex_lock(&dcc->cmd_lock);
1784 dc = __lookup_discard_cmd(sbi, blkaddr);
1785 if (dc) {
1786 if (f2fs_sb_has_blkzoned(sbi) && bdev_is_zoned(dc->bdev)) {
1787 /* force submit zone reset */
1788 if (dc->state == D_PREP)
> 1789 __submit_zone_reset_cmd(sbi, dc, REQ_SYNC,
1790 &dcc->wait_list, NULL);
1791 dc->ref++;
1792 need_wait = true;
1793 } else {
1794 if (dc->state == D_PREP) {
1795 __punch_discard_cmd(sbi, dc, blkaddr);
1796 } else {
1797 dc->ref++;
1798 need_wait = true;
1799 }
1800 }
1801 }
1802 mutex_unlock(&dcc->cmd_lock);
1803
1804 if (need_wait)
1805 __wait_one_discard_bio(sbi, dc);
1806 }
1807
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next prev parent reply other threads:[~2023-04-28 6:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230428025646epcms2p35acbea45ee80d36808861edba8a3c84a@epcms2p3>
2023-04-28 2:56 ` [f2fs-dev] [PATCH v3] f2fs: add async reset zone command support Daejun Park
2023-04-28 2:56 ` Daejun Park
2023-04-28 6:16 ` kernel test robot [this message]
2023-04-28 6:16 ` kernel test robot
2023-04-28 13:24 ` [f2fs-dev] " kernel test robot
2023-04-28 13:24 ` 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=202304281424.WrTeoZ4B-lkp@intel.com \
--to=lkp@intel.com \
--cc=beomsu7.kim@samsung.com \
--cc=chao@kernel.org \
--cc=daejun7.park@samsung.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=sukka.kim@samsung.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.