From: kernel test robot <lkp@intel.com>
To: Chao Yu <yuchao0@huawei.com>, Chao Yu <chao@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, Chao Yu <yuchao0@huawei.com>,
Chao Yu <chao@kernel.org>
Subject: [chao:bugfix/syzbot 33/33] fs/f2fs/f2fs.h:3130:24: error: 'struct f2fs_inode_info' has no member named 'i_gc_failures'; did you mean 'i_pin_failure'?
Date: Mon, 6 May 2024 00:48:26 +0800 [thread overview]
Message-ID: <202405060007.AISdO2GQ-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git bugfix/syzbot
head: d7c9e98caf2285d83bf9e839c7398946bbc7deb3
commit: d7c9e98caf2285d83bf9e839c7398946bbc7deb3 [33/33] f2fs: remove unused GC_FAILURE_PIN
config: arc-randconfig-002-20240505 (https://download.01.org/0day-ci/archive/20240506/202405060007.AISdO2GQ-lkp@intel.com/config)
compiler: arc-elf-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240506/202405060007.AISdO2GQ-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/202405060007.AISdO2GQ-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from fs/f2fs/dir.c:13:
fs/f2fs/f2fs.h: In function 'f2fs_i_gc_failures_write':
>> fs/f2fs/f2fs.h:3130:24: error: 'struct f2fs_inode_info' has no member named 'i_gc_failures'; did you mean 'i_pin_failure'?
3130 | F2FS_I(inode)->i_gc_failures = count;
| ^~~~~~~~~~~~~
| i_pin_failure
--
In file included from fs/f2fs/recovery.c:12:
fs/f2fs/f2fs.h: In function 'f2fs_i_gc_failures_write':
>> fs/f2fs/f2fs.h:3130:24: error: 'struct f2fs_inode_info' has no member named 'i_gc_failures'; did you mean 'i_pin_failure'?
3130 | F2FS_I(inode)->i_gc_failures = count;
| ^~~~~~~~~~~~~
| i_pin_failure
fs/f2fs/recovery.c: In function 'recover_inode':
>> fs/f2fs/recovery.c:333:24: error: 'struct f2fs_inode_info' has no member named 'i_gc_failures'; did you mean 'i_pin_failure'?
333 | F2FS_I(inode)->i_gc_failures = le16_to_cpu(raw->i_gc_failures);
| ^~~~~~~~~~~~~
| i_pin_failure
--
In file included from fs/f2fs/file.c:29:
fs/f2fs/f2fs.h: In function 'f2fs_i_gc_failures_write':
>> fs/f2fs/f2fs.h:3130:24: error: 'struct f2fs_inode_info' has no member named 'i_gc_failures'; did you mean 'i_pin_failure'?
3130 | F2FS_I(inode)->i_gc_failures = count;
| ^~~~~~~~~~~~~
| i_pin_failure
fs/f2fs/file.c: In function 'f2fs_pin_file_control':
>> fs/f2fs/file.c:3220:53: error: 'struct f2fs_inode_info' has no member named 'i_gc_failures'; did you mean 'i_pin_failure'?
3220 | f2fs_i_gc_failures_write(inode, fi->i_gc_failures + 1);
| ^~~~~~~~~~~~~
| i_pin_failure
fs/f2fs/file.c:3222:17: error: 'struct f2fs_inode_info' has no member named 'i_gc_failures'; did you mean 'i_pin_failure'?
3222 | if (fi->i_gc_failures > sbi->gc_pin_file_threshold) {
| ^~~~~~~~~~~~~
| i_pin_failure
fs/f2fs/file.c:3224:55: error: 'struct f2fs_inode_info' has no member named 'i_gc_failures'; did you mean 'i_pin_failure'?
3224 | __func__, inode->i_ino, fi->i_gc_failures);
| ^~~~~~~~~~~~~
fs/f2fs/f2fs.h:1829:53: note: in definition of macro 'f2fs_warn'
1829 | f2fs_printk(sbi, false, KERN_WARNING fmt, ##__VA_ARGS__)
| ^~~~~~~~~~~
fs/f2fs/file.c: In function 'f2fs_ioc_set_pin_file':
fs/f2fs/file.c:3288:30: error: 'struct f2fs_inode_info' has no member named 'i_gc_failures'; did you mean 'i_pin_failure'?
3288 | ret = F2FS_I(inode)->i_gc_failures;
| ^~~~~~~~~~~~~
| i_pin_failure
fs/f2fs/file.c: In function 'f2fs_ioc_get_pin_file':
fs/f2fs/file.c:3303:38: error: 'struct f2fs_inode_info' has no member named 'i_gc_failures'; did you mean 'i_pin_failure'?
3303 | pin = F2FS_I(inode)->i_gc_failures;
| ^~~~~~~~~~~~~
| i_pin_failure
--
In file included from fs/f2fs/inode.c:16:
fs/f2fs/f2fs.h: In function 'f2fs_i_gc_failures_write':
>> fs/f2fs/f2fs.h:3130:24: error: 'struct f2fs_inode_info' has no member named 'i_gc_failures'; did you mean 'i_pin_failure'?
3130 | F2FS_I(inode)->i_gc_failures = count;
| ^~~~~~~~~~~~~
| i_pin_failure
fs/f2fs/inode.c: In function 'do_read_inode':
>> fs/f2fs/inode.c:418:21: error: 'struct f2fs_inode_info' has no member named 'i_gc_failures'; did you mean 'i_pin_failure'?
418 | fi->i_gc_failures = le16_to_cpu(ri->i_gc_failures);
| ^~~~~~~~~~~~~
| i_pin_failure
In file included from include/linux/byteorder/little_endian.h:5,
from arch/arc/include/uapi/asm/byteorder.h:16,
from include/asm-generic/bitops/le.h:6,
from arch/arc/include/asm/bitops.h:192,
from include/linux/bitops.h:68,
from include/linux/thread_info.h:27,
from include/asm-generic/preempt.h:5,
from ./arch/arc/include/generated/asm/preempt.h:1,
from include/linux/preempt.h:79,
from include/linux/spinlock.h:56,
from include/linux/wait.h:9,
from include/linux/wait_bit.h:8,
from include/linux/fs.h:6,
from fs/f2fs/inode.c:8:
fs/f2fs/inode.c: In function 'f2fs_update_inode':
fs/f2fs/inode.c:688:64: error: 'struct f2fs_inode_info' has no member named 'i_gc_failures'; did you mean 'i_pin_failure'?
688 | ri->i_gc_failures = cpu_to_le16(F2FS_I(inode)->i_gc_failures);
| ^~~~~~~~~~~~~
include/uapi/linux/byteorder/little_endian.h:36:51: note: in definition of macro '__cpu_to_le16'
36 | #define __cpu_to_le16(x) ((__force __le16)(__u16)(x))
| ^
fs/f2fs/inode.c:688:37: note: in expansion of macro 'cpu_to_le16'
688 | ri->i_gc_failures = cpu_to_le16(F2FS_I(inode)->i_gc_failures);
| ^~~~~~~~~~~
vim +3130 fs/f2fs/f2fs.h
3126
3127 static inline void f2fs_i_gc_failures_write(struct inode *inode,
3128 unsigned int count)
3129 {
> 3130 F2FS_I(inode)->i_gc_failures = count;
3131 f2fs_mark_inode_dirty_sync(inode, true);
3132 }
3133
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-05-05 16: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=202405060007.AISdO2GQ-lkp@intel.com \
--to=lkp@intel.com \
--cc=chao@kernel.org \
--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 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.