From: kernel test robot <lkp@intel.com>
To: Chao Yu <yuchao0@huawei.com>, Chao Yu <chao@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Chao Yu <yuchao0@huawei.com>, Chao Yu <chao@kernel.org>
Subject: [chao:bugfix/common 7/7] fs/f2fs/file.c:41:9: warning: variable 'end' set but not used
Date: Tue, 20 May 2025 00:05:27 +0800 [thread overview]
Message-ID: <202505192317.v8BHsr1M-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git bugfix/common
head: e016c01f389556a6ba04208719f95895cf5a5a6c
commit: e016c01f389556a6ba04208719f95895cf5a5a6c [7/7] f2fs: fix to zero post-eof page
config: arm-randconfig-001-20250519 (https://download.01.org/0day-ci/archive/20250519/202505192317.v8BHsr1M-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
rustc: rustc 1.78.0 (9b00956e5 2024-04-29)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250519/202505192317.v8BHsr1M-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/202505192317.v8BHsr1M-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> fs/f2fs/file.c:41:9: warning: variable 'end' set but not used [-Wunused-but-set-variable]
41 | loff_t end;
| ^
1 warning generated.
vim +/end +41 fs/f2fs/file.c
37
38 static void f2fs_zero_post_eof_page(struct inode *inode, loff_t new_size)
39 {
40 loff_t old_size = i_size_read(inode);
> 41 loff_t end;
42
43 if (new_size < old_size)
44 return;
45
46 end = min(new_size, round_up(old_size, PAGE_SIZE));
47 truncate_pagecache(inode, old_size);
48 }
49
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-05-19 16:05 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=202505192317.v8BHsr1M-lkp@intel.com \
--to=lkp@intel.com \
--cc=chao@kernel.org \
--cc=llvm@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox