From: kernel test robot <lkp@intel.com>
To: Jack Qiu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
Chao Yu <yuchao0@huawei.com>,
linux-f2fs-devel@lists.sourceforge.net,
Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [f2fs-dev] [jaegeuk-f2fs:dev-test 2/2] fs/f2fs/file.c:3908:15: error: use of undeclared identifier 'sbi'
Date: Tue, 7 Jun 2022 15:40:21 +0800 [thread overview]
Message-ID: <202206071533.vc9l1Css-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git dev-test
head: 7f7c4d65019e9c82538b92ec5df2e4f0c6765998
commit: 7f7c4d65019e9c82538b92ec5df2e4f0c6765998 [2/2] f2fs: optimize error handling in redirty_blocks
config: i386-randconfig-a002 (https://download.01.org/0day-ci/archive/20220607/202206071533.vc9l1Css-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project b92436efcb7813fc481b30f2593a4907568d917a)
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=7f7c4d65019e9c82538b92ec5df2e4f0c6765998
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 7f7c4d65019e9c82538b92ec5df2e4f0c6765998
# 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/f2fs/
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/file.c:3908:15: error: use of undeclared identifier 'sbi'
f2fs_bug_on(sbi, !page);
^
1 error generated.
vim +/sbi +3908 fs/f2fs/file.c
3884
3885 static int redirty_blocks(struct inode *inode, pgoff_t page_idx, int len)
3886 {
3887 DEFINE_READAHEAD(ractl, NULL, NULL, inode->i_mapping, page_idx);
3888 struct address_space *mapping = inode->i_mapping;
3889 struct page *page;
3890 pgoff_t redirty_idx = page_idx;
3891 int i, page_len = 0, ret = 0;
3892
3893 page_cache_ra_unbounded(&ractl, len, 0);
3894
3895 for (i = 0; i < len; i++, page_idx++) {
3896 page = read_cache_page(mapping, page_idx, NULL, NULL);
3897 if (IS_ERR(page)) {
3898 ret = PTR_ERR(page);
3899 break;
3900 }
3901 page_len++;
3902 }
3903
3904 for (i = 0; i < page_len; i++, redirty_idx++) {
3905 page = find_lock_page(mapping, redirty_idx);
3906
3907 /* It will never fail, when page has pinned above */
> 3908 f2fs_bug_on(sbi, !page);
3909
3910 set_page_dirty(page);
3911 f2fs_put_page(page, 1);
3912 f2fs_put_page(page, 0);
3913 }
3914
3915 return ret;
3916 }
3917
--
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-07 7:41 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=202206071533.vc9l1Css-lkp@intel.com \
--to=lkp@intel.com \
--cc=jaegeuk@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=llvm@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;
as well as URLs for NNTP newsgroup(s).