From: kernel test robot <[email protected]>
To: David Howells <[email protected]>
Cc: [email protected], [email protected],
GNU/Weeb Mailing List <[email protected]>,
[email protected], Kees Cook <[email protected]>
Subject: [ammarfaizi2-block:dhowells/linux-fs/fscache-next 3/3] fs/cifs/fscache.c:106:9: error: no member named 'netfs_ctx' in 'struct cifsInodeInfo'
Date: Fri, 20 May 2022 08:08:00 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
tree: https://github.com/ammarfaizi2/linux-block dhowells/linux-fs/fscache-next
head: a3457aa9c40f99183345cbedd7e0a7404bcc6370
commit: a3457aa9c40f99183345cbedd7e0a7404bcc6370 [3/3] netfs: Fix gcc-12 warning by embedding vfs inode in netfs_i_context
config: x86_64-allmodconfig (https://download.01.org/0day-ci/archive/20220520/[email protected]/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project e00cbbec06c08dc616a0d52a20f678b8fbd4e304)
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://github.com/ammarfaizi2/linux-block/commit/a3457aa9c40f99183345cbedd7e0a7404bcc6370
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block dhowells/linux-fs/fscache-next
git checkout a3457aa9c40f99183345cbedd7e0a7404bcc6370
# 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=x86_64 SHELL=/bin/bash fs/cifs/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <[email protected]>
All errors (new ones prefixed by >>):
>> fs/cifs/fscache.c:106:9: error: no member named 'netfs_ctx' in 'struct cifsInodeInfo'
cifsi->netfs_ctx.cache =
~~~~~ ^
fs/cifs/fscache.c:134:10: error: no member named 'netfs_ctx' in 'struct cifsInodeInfo'
cifsi->netfs_ctx.cache = NULL;
~~~~~ ^
2 errors generated.
vim +106 fs/cifs/fscache.c
402cb8dda949d9 David Howells 2018-04-04 96
70431bfd825d9c David Howells 2020-11-17 97 void cifs_fscache_get_inode_cookie(struct inode *inode)
9451a9a52f91a4 Suresh Jayaraman 2010-07-05 98 {
70431bfd825d9c David Howells 2020-11-17 99 struct cifs_fscache_inode_coherency_data cd;
9451a9a52f91a4 Suresh Jayaraman 2010-07-05 100 struct cifsInodeInfo *cifsi = CIFS_I(inode);
9451a9a52f91a4 Suresh Jayaraman 2010-07-05 101 struct cifs_sb_info *cifs_sb = CIFS_SB(inode->i_sb);
96daf2b09178d8 Steve French 2011-05-27 102 struct cifs_tcon *tcon = cifs_sb_master_tcon(cifs_sb);
9451a9a52f91a4 Suresh Jayaraman 2010-07-05 103
a3457aa9c40f99 David Howells 2022-05-19 104 cifs_fscache_fill_coherency(&cifsi->nic.inode, &cd);
9451a9a52f91a4 Suresh Jayaraman 2010-07-05 105
bc899ee1c898e5 David Howells 2021-06-29 @106 cifsi->netfs_ctx.cache =
70431bfd825d9c David Howells 2020-11-17 107 fscache_acquire_cookie(tcon->fscache, 0,
70431bfd825d9c David Howells 2020-11-17 108 &cifsi->uniqueid, sizeof(cifsi->uniqueid),
70431bfd825d9c David Howells 2020-11-17 109 &cd, sizeof(cd),
a3457aa9c40f99 David Howells 2022-05-19 110 i_size_read(&cifsi->nic.inode));
9451a9a52f91a4 Suresh Jayaraman 2010-07-05 111 }
9451a9a52f91a4 Suresh Jayaraman 2010-07-05 112
:::::: The code at line 106 was first introduced by commit
:::::: bc899ee1c898e520574ff4d99356eb2e724a9265 netfs: Add a netfs inode context
:::::: TO: David Howells <[email protected]>
:::::: CC: David Howells <[email protected]>
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-05-20 0:08 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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