From: kernel test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: kbuild-all@lists.01.org,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
linux-kernel@vger.kernel.org
Subject: [ammarfaizi2-block:dhowells/linux-fs/cifs-netfs 32/41] fs/cifs/fscache.c:112:67: sparse: sparse: incorrect type in argument 2 (different base types)
Date: Wed, 1 Jun 2022 19:01:17 +0800 [thread overview]
Message-ID: <202206011851.UCwIa18w-lkp@intel.com> (raw)
tree: https://github.com/ammarfaizi2/linux-block dhowells/linux-fs/cifs-netfs
head: 1fc71b6b30f6d2a981c163b77c9aee0aecaecb29
commit: ccc1acdfa787b5bf5c9c2b3f829b18f5a0bb0938 [32/41] mm, netfs, fscache: Stop read optimisation when folio removed from pagecache
config: x86_64-randconfig-s021 (https://download.01.org/0day-ci/archive/20220601/202206011851.UCwIa18w-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-1) 11.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-14-g5a0004b5-dirty
# https://github.com/ammarfaizi2/linux-block/commit/ccc1acdfa787b5bf5c9c2b3f829b18f5a0bb0938
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block dhowells/linux-fs/cifs-netfs
git checkout ccc1acdfa787b5bf5c9c2b3f829b18f5a0bb0938
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 SHELL=/bin/bash fs/cifs/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> fs/cifs/fscache.c:112:67: sparse: sparse: incorrect type in argument 2 (different base types) @@ expected unsigned long volatile *addr @@ got unsigned long flags @@
fs/cifs/fscache.c:112:67: sparse: expected unsigned long volatile *addr
fs/cifs/fscache.c:112:67: sparse: got unsigned long flags
vim +112 fs/cifs/fscache.c
96
97 void cifs_fscache_get_inode_cookie(struct inode *inode)
98 {
99 struct cifs_fscache_inode_coherency_data cd;
100 struct cifsInodeInfo *cifsi = CIFS_I(inode);
101 struct cifs_sb_info *cifs_sb = CIFS_SB(inode->i_sb);
102 struct cifs_tcon *tcon = cifs_sb_master_tcon(cifs_sb);
103
104 cifs_fscache_fill_coherency(&cifsi->vfs_inode, &cd);
105
106 cifsi->netfs_ctx.cache =
107 fscache_acquire_cookie(tcon->fscache, 0,
108 &cifsi->uniqueid, sizeof(cifsi->uniqueid),
109 &cd, sizeof(cd),
110 i_size_read(&cifsi->vfs_inode));
111 if (cifsi->netfs_ctx.cache)
> 112 set_bit(AS_NOTIFY_REMOVING_FOLIO, inode->i_mapping->flags);
113
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-06-01 11:02 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=202206011851.UCwIa18w-lkp@intel.com \
--to=lkp@intel.com \
--cc=dhowells@redhat.com \
--cc=gwml@vger.gnuweeb.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®