From: kernel test robot <lkp@intel.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [vbabka:b4/slab-cleanup-flags 3/4] fs/proc/inode.c:99:49: sparse: sparse: restricted slab_flags_t degrades to integer
Date: Wed, 21 Feb 2024 19:00:09 +0800 [thread overview]
Message-ID: <202402211803.Lmf1ANXx-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vbabka/linux.git b4/slab-cleanup-flags
head: 95c527f4e5dd5245977e9625ec6e1197dc0e733b
commit: 9cd1bbdf6848577e2e1c1a3cab62dbe91b993439 [3/4] mm, slab: use an enum to define SLAB_ cache creation flags
config: sparc-randconfig-r111-20240221 (https://download.01.org/0day-ci/archive/20240221/202402211803.Lmf1ANXx-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20240221/202402211803.Lmf1ANXx-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/202402211803.Lmf1ANXx-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
fs/proc/inode.c:55:17: sparse: sparse: incompatible types in comparison expression (different address spaces):
fs/proc/inode.c:55:17: sparse: struct ctl_table_header [noderef] __rcu *
fs/proc/inode.c:55:17: sparse: struct ctl_table_header *
>> fs/proc/inode.c:99:49: sparse: sparse: restricted slab_flags_t degrades to integer
>> fs/proc/inode.c:98:77: sparse: sparse: incorrect type in argument 4 (different base types) @@ expected restricted slab_flags_t [usertype] flags @@ got unsigned int @@
fs/proc/inode.c:117:22: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct hlist_node *node @@ got struct hlist_node [noderef] __rcu * @@
vim +99 fs/proc/inode.c
^1da177e4c3f41 Linus Torvalds 2005-04-16 92
195b8cf0689554 Alexey Dobriyan 2018-04-10 93 void __init proc_init_kmemcache(void)
^1da177e4c3f41 Linus Torvalds 2005-04-16 94 {
^1da177e4c3f41 Linus Torvalds 2005-04-16 95 proc_inode_cachep = kmem_cache_create("proc_inode_cache",
^1da177e4c3f41 Linus Torvalds 2005-04-16 96 sizeof(struct proc_inode),
fffb60f93ce588 Paul Jackson 2006-03-24 97 0, (SLAB_RECLAIM_ACCOUNT|
5d097056c9a017 Vladimir Davydov 2016-01-14 @98 SLAB_MEM_SPREAD|SLAB_ACCOUNT|
5d097056c9a017 Vladimir Davydov 2016-01-14 @99 SLAB_PANIC),
20c2df83d25c6a Paul Mundt 2007-07-20 100 init_once);
195b8cf0689554 Alexey Dobriyan 2018-04-10 101 pde_opener_cache =
195b8cf0689554 Alexey Dobriyan 2018-04-10 102 kmem_cache_create("pde_opener", sizeof(struct pde_opener), 0,
2acddbe8168967 Alexey Dobriyan 2018-04-10 103 SLAB_ACCOUNT|SLAB_PANIC, NULL);
b4884f23331ae3 Alexey Dobriyan 2018-04-10 104 proc_dir_entry_cache = kmem_cache_create_usercopy(
2d6e4e822ad817 Alexey Dobriyan 2018-08-21 105 "proc_dir_entry", SIZEOF_PDE, 0, SLAB_PANIC,
2d6e4e822ad817 Alexey Dobriyan 2018-08-21 106 offsetof(struct proc_dir_entry, inline_name),
2d6e4e822ad817 Alexey Dobriyan 2018-08-21 107 SIZEOF_PDE_INLINE_NAME, NULL);
2d6e4e822ad817 Alexey Dobriyan 2018-08-21 108 BUILD_BUG_ON(sizeof(struct proc_dir_entry) >= SIZEOF_PDE);
^1da177e4c3f41 Linus Torvalds 2005-04-16 109 }
^1da177e4c3f41 Linus Torvalds 2005-04-16 110
:::::: The code at line 99 was first introduced by commit
:::::: 5d097056c9a017a3b720849efb5432f37acabbac kmemcg: account certain kmem allocations to memcg
:::::: TO: Vladimir Davydov <vdavydov@virtuozzo.com>
:::::: CC: Linus Torvalds <torvalds@linux-foundation.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-02-21 11:00 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=202402211803.Lmf1ANXx-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vbabka@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).