From: kernel test robot <lkp@intel.com>
To: Chao Yu <chao@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Chao Yu <chao@kernel.org>
Subject: [chao:cleanup 2/2] fs/f2fs/data.c:332:39: error: expression cannot be followed by a postfix '->' operator; add parentheses
Date: Fri, 26 Sep 2025 13:48:05 +0800 [thread overview]
Message-ID: <202509261311.c1JiZZxU-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git cleanup
head: ea458a3f3d672b53286ed7058ba33a95c0713cac
commit: ea458a3f3d672b53286ed7058ba33a95c0713cac [2/2] f2fs: use fscrypt_finalize_bounce_page() for cleanup
config: x86_64-buildonly-randconfig-002-20250926 (https://download.01.org/0day-ci/archive/20250926/202509261311.c1JiZZxU-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250926/202509261311.c1JiZZxU-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/202509261311.c1JiZZxU-lkp@intel.com/
All errors (new ones prefixed by >>):
>> fs/f2fs/data.c:332:39: error: expression cannot be followed by a postfix '->' operator; add parentheses
332 | fscrypt_finalize_bounce_page(&&folio->page);
| ~~~~~~~^
| ( )
>> fs/f2fs/data.c:332:39: error: member reference base type 'void' is not a structure or union
332 | fscrypt_finalize_bounce_page(&&folio->page);
| ~~~~~~~^ ~~~~
>> fs/f2fs/data.c:332:34: error: use of undeclared label 'folio'
332 | fscrypt_finalize_bounce_page(&&folio->page);
| ^
3 errors generated.
vim +332 fs/f2fs/data.c
316
317 static void f2fs_write_end_io(struct bio *bio)
318 {
319 struct f2fs_sb_info *sbi;
320 struct folio_iter fi;
321
322 iostat_update_and_unbind_ctx(bio);
323 sbi = bio->bi_private;
324
325 if (time_to_inject(sbi, FAULT_WRITE_IO))
326 bio->bi_status = BLK_STS_IOERR;
327
328 bio_for_each_folio_all(fi, bio) {
329 struct folio *folio = fi.folio;
330 enum count_type type;
331
> 332 fscrypt_finalize_bounce_page(&&folio->page);
333
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-09-26 5:48 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=202509261311.c1JiZZxU-lkp@intel.com \
--to=lkp@intel.com \
--cc=chao@kernel.org \
--cc=llvm@lists.linux.dev \
--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