From: kernel test robot <lkp@intel.com>
To: Jan Kara <jack@suse.cz>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Christian Brauner <christianvanbrauner@gmail.com>,
Christian Brauner <brauner@kernel.org>
Subject: [brauner-github:vfs.all 224/271] fs/bfs/inode.c:180:43: error: no member named 'ino' in 'struct inode'
Date: Mon, 27 Jul 2026 21:24:25 +0800 [thread overview]
Message-ID: <202607272132.5qdCaHxj-lkp@intel.com> (raw)
tree: https://github.com/brauner/linux.git vfs.all
head: 000710393edad9c9974ee19ce0e95459137b3c3b
commit: 763d78b5dbba67952960a5f40ad15518c79fae86 [224/271] bfs: Fix data integrity writeout issues
config: s390-randconfig-001-20260727 (https://download.01.org/0day-ci/archive/20260727/202607272132.5qdCaHxj-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 890b11e09e45e9d8b29f2f94f22052be3934e757)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260727/202607272132.5qdCaHxj-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/202607272132.5qdCaHxj-lkp@intel.com/
All errors (new ones prefixed by >>):
>> fs/bfs/inode.c:180:43: error: no member named 'ino' in 'struct inode'
180 | di = find_inode(inode->i_sb, (u16)inode->ino, &bh);
| ~~~~~ ^
1 error generated.
vim +180 fs/bfs/inode.c
172
173 static int bfs_sync_inode_metadata(struct inode *inode,
174 struct writeback_control *wbc)
175 {
176 int err = 0;
177 struct bfs_inode *di;
178 struct buffer_head *bh;
179
> 180 di = find_inode(inode->i_sb, (u16)inode->ino, &bh);
181 if (IS_ERR(di))
182 return PTR_ERR(di);
183
184 sync_dirty_buffer(bh);
185 if (buffer_write_io_error(bh)) {
186 err = -EIO;
187 goto out;
188 }
189 err = mmb_sync(&BFS_I(inode)->i_metadata_bhs);
190 out:
191 brelse(bh);
192 return err;
193 }
194
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-27 13:24 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=202607272132.5qdCaHxj-lkp@intel.com \
--to=lkp@intel.com \
--cc=brauner@kernel.org \
--cc=christianvanbrauner@gmail.com \
--cc=jack@suse.cz \
--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