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/netfs-maple 26/40] fs/netfs/crypto.c:76:31: sparse: sparse: incompatible types in comparison expression (different type sizes):
Date: Tue, 5 Apr 2022 19:07:00 +0800 [thread overview]
Message-ID: <202204051933.fe6riDOF-lkp@intel.com> (raw)
tree: https://github.com/ammarfaizi2/linux-block dhowells/linux-fs/netfs-maple
head: 674eea41fc70a740ff83ec590f9833f805852464
commit: fc693b2e39df6567a0312f21bb9004e1d7983286 [26/40] netfs: Perform content encryption
config: i386-randconfig-s002 (https://download.01.org/0day-ci/archive/20220405/202204051933.fe6riDOF-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.2.0-19) 11.2.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-dirty
# https://github.com/ammarfaizi2/linux-block/commit/fc693b2e39df6567a0312f21bb9004e1d7983286
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block dhowells/linux-fs/netfs-maple
git checkout fc693b2e39df6567a0312f21bb9004e1d7983286
# save the config file to linux build tree
mkdir build_dir
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash fs/netfs/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> fs/netfs/crypto.c:76:31: sparse: sparse: incompatible types in comparison expression (different type sizes):
>> fs/netfs/crypto.c:76:31: sparse: unsigned int *
>> fs/netfs/crypto.c:76:31: sparse: unsigned long *
vim +76 fs/netfs/crypto.c
45
46 /*
47 * Populate a scatterlist from folios in an xarray.
48 */
49 static int netfs_xarray_to_sglist(struct xarray *xa, loff_t pos, size_t len,
50 struct scatterlist *sg, unsigned int n_sg)
51 {
52 struct scatterlist *p = sg;
53 struct folio *folio = NULL;
54 size_t seg, offset, skip = 0;
55 loff_t start = pos;
56 pgoff_t index = start >> PAGE_SHIFT;
57 int j;
58
59 XA_STATE(xas, xa, index);
60
61 sg_init_table(sg, n_sg);
62
63 rcu_read_lock();
64
65 xas_for_each(&xas, folio, ULONG_MAX) {
66 if (xas_retry(&xas, folio))
67 continue;
68 if (WARN_ON(xa_is_value(folio)) || WARN_ON(folio_test_hugetlb(folio)))
69 break;
70 for (j = (folio_index(folio) < index) ? index - folio_index(folio) : 0;
71 j < folio_nr_pages(folio); j++
72 ) {
73 struct page *subpage = folio_file_page(folio, j);
74
75 offset = (pos + skip) & ~PAGE_MASK;
> 76 seg = min(len, PAGE_SIZE - offset);
77
78 sg_set_page(p++, subpage, seg, offset);
79
80 len -= seg;
81 skip += seg;
82 if (len == 0)
83 break;
84 }
85 if (len == 0)
86 break;
87 }
88
89 rcu_read_unlock();
90 if (len > 0) {
91 kdebug("*** Insufficient source (%zx)", len);
92 //WARN_ON(len > 0);
93 return -EIO;
94 }
95
96 sg_mark_end(p - 1);
97 return p - sg;
98 }
99
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-04-06 1:54 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=202204051933.fe6riDOF-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 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.