From: kernel test robot <lkp@intel.com>
To: Byungchul Park <byungchul@sk.com>
Cc: oe-kbuild-all@lists.linux.dev,
"David Hildenbrand" <david@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Linux Memory Management List" <linux-mm@kvack.org>,
"Pavel Begunkov" <asml.silence@gmail.com>,
"Toke Høiland-Jørgensen " <toke@redhat.com>
Subject: [akpm-mm:mm-unstable 101/288] net/core/netmem_priv.h:19:73: sparse: sparse: incorrect type in argument 1 (different base types)
Date: Fri, 16 Jan 2026 14:29:31 +0800 [thread overview]
Message-ID: <202601161420.8xY65Dyx-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-unstable
head: f8ed52ac0cfbddff992bb9600941bfe51e1e385a
commit: 71b73571e052b94a2af7835373d4090afee5e1eb [101/288] mm: introduce a new page type for page pool in page type
config: x86_64-randconfig-123-20260116 (https://download.01.org/0day-ci/archive/20260116/202601161420.8xY65Dyx-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260116/202601161420.8xY65Dyx-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/202601161420.8xY65Dyx-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
net/core/skbuff.c: note: in included file:
>> net/core/netmem_priv.h:19:73: sparse: sparse: incorrect type in argument 1 (different base types) @@ expected restricted netmem_ref [usertype] netmem @@ got unsigned long @@
net/core/netmem_priv.h:19:73: sparse: expected restricted netmem_ref [usertype] netmem
net/core/netmem_priv.h:19:73: sparse: got unsigned long
>> net/core/netmem_priv.h:19:73: sparse: sparse: incorrect type in argument 1 (different base types) @@ expected restricted netmem_ref [usertype] netmem @@ got unsigned long @@
net/core/netmem_priv.h:19:73: sparse: expected restricted netmem_ref [usertype] netmem
net/core/netmem_priv.h:19:73: sparse: got unsigned long
net/core/skbuff.c: note: in included file (through include/linux/skbuff.h, include/net/net_namespace.h, include/linux/inet.h):
include/net/checksum.h:33:39: sparse: sparse: incorrect type in argument 3 (different base types) @@ expected restricted __wsum [usertype] sum @@ got unsigned int @@
include/net/checksum.h:33:39: sparse: expected restricted __wsum [usertype] sum
include/net/checksum.h:33:39: sparse: got unsigned int
vim +19 net/core/netmem_priv.h
10
11 static inline bool netmem_is_pp(netmem_ref netmem)
12 {
13 /* XXX: Now that the offset of page_type is shared between
14 * struct page and net_iov, just cast the netmem to struct page
15 * unconditionally by clearing NET_IOV if any, no matter whether
16 * it comes from struct net_iov or struct page. This should be
17 * adjusted once the offset is no longer shared.
18 */
> 19 return PageNetpp(__netmem_to_page((__force unsigned long)netmem & ~NET_IOV));
20 }
21
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-01-16 6:29 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=202601161420.8xY65Dyx-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=asml.silence@gmail.com \
--cc=byungchul@sk.com \
--cc=david@kernel.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=toke@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox