From: kernel test robot <lkp@intel.com>
To: Daeho Jeong <daehojeong@google.com>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [jaegeuk-f2fs:dev-test 5/7] fs/f2fs/data.c:137:8: error: too many arguments to function call, expected 3, have 4
Date: Tue, 14 Jun 2022 13:27:06 +0800 [thread overview]
Message-ID: <202206141312.6Prd40vG-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git dev-test
head: b133c2a8acb301652cdf98198f21b41e4c36c281
commit: 1b565702dffe0d67d19fce41be2eae24c0d19709 [5/7] f2fs: handle decompress only post processing in softirq
config: i386-randconfig-a004-20220613 (https://download.01.org/0day-ci/archive/20220614/202206141312.6Prd40vG-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project c97436f8b6e2718286e8496faf53a2c800e281cf)
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://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git/commit/?id=1b565702dffe0d67d19fce41be2eae24c0d19709
git remote add jaegeuk-f2fs https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git
git fetch --no-tags jaegeuk-f2fs dev-test
git checkout 1b565702dffe0d67d19fce41be2eae24c0d19709
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=i386 SHELL=/bin/bash fs/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> fs/f2fs/data.c:137:8: error: too many arguments to function call, expected 3, have 4
in_softirq);
^~~~~~~~~~
fs/f2fs/f2fs.h:4232:20: note: 'f2fs_end_read_compressed_page' declared here
static inline void f2fs_end_read_compressed_page(struct page *page,
^
>> fs/f2fs/data.c:138:28: error: too many arguments to function call, expected single argument 'page', have 2 arguments
f2fs_put_page_dic(page, in_softirq);
~~~~~~~~~~~~~~~~~ ^~~~~~~~~~
fs/f2fs/f2fs.h:4237:20: note: 'f2fs_put_page_dic' declared here
static inline void f2fs_put_page_dic(struct page *page)
^
fs/f2fs/data.c:242:16: error: too many arguments to function call, expected 3, have 4
blkaddr, in_softirq);
^~~~~~~~~~
fs/f2fs/f2fs.h:4232:20: note: 'f2fs_end_read_compressed_page' declared here
static inline void f2fs_end_read_compressed_page(struct page *page,
^
3 errors generated.
vim +137 fs/f2fs/data.c
121
122 static void f2fs_finish_read_bio(struct bio *bio, bool in_softirq)
123 {
124 struct bio_vec *bv;
125 struct bvec_iter_all iter_all;
126
127 /*
128 * Update and unlock the bio's pagecache pages, and put the
129 * decompression context for any compressed pages.
130 */
131 bio_for_each_segment_all(bv, bio, iter_all) {
132 struct page *page = bv->bv_page;
133
134 if (f2fs_is_compressed_page(page)) {
135 if (bio->bi_status)
136 f2fs_end_read_compressed_page(page, true, 0,
> 137 in_softirq);
> 138 f2fs_put_page_dic(page, in_softirq);
139 continue;
140 }
141
142 /* PG_error was set if decryption or verity failed. */
143 if (bio->bi_status || PageError(page)) {
144 ClearPageUptodate(page);
145 /* will re-read again later */
146 ClearPageError(page);
147 } else {
148 SetPageUptodate(page);
149 }
150 dec_page_count(F2FS_P_SB(page), __read_io_type(page));
151 unlock_page(page);
152 }
153
154 if (bio->bi_private)
155 mempool_free(bio->bi_private, bio_post_read_ctx_pool);
156 bio_put(bio);
157 }
158
--
0-DAY CI Kernel Test Service
https://01.org/lkp
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
reply other threads:[~2022-06-14 5:27 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=202206141312.6Prd40vG-lkp@intel.com \
--to=lkp@intel.com \
--cc=daehojeong@google.com \
--cc=jaegeuk@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=llvm@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).