All of lore.kernel.org
 help / color / mirror / Atom feed
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/overlayfs/super.c:1499:62: sparse: sparse: incorrect type in argument 4 (different base types)
Date: Wed, 21 Feb 2024 23:33:38 +0800	[thread overview]
Message-ID: <202402212310.KPtSDrRy-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: powerpc-randconfig-r131-20240221 (https://download.01.org/0day-ci/archive/20240221/202402212310.KPtSDrRy-lkp@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project 36adfec155de366d722f2bac8ff9162289dcf06c)
reproduce: (https://download.01.org/0day-ci/archive/20240221/202402212310.KPtSDrRy-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/202402212310.KPtSDrRy-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> fs/overlayfs/super.c:1499:62: sparse: sparse: incorrect type in argument 4 (different base types) @@     expected restricted slab_flags_t [usertype] flags @@     got int @@
   fs/overlayfs/super.c:1499:62: sparse:     expected restricted slab_flags_t [usertype] flags
   fs/overlayfs/super.c:1499:62: sparse:     got int
   fs/overlayfs/super.c: note: in included file (through include/linux/mmzone.h, include/linux/gfp.h, include/linux/xarray.h, ...):
   include/linux/page-flags.h:242:46: sparse: sparse: self-comparison always evaluates to false

vim +1499 fs/overlayfs/super.c

13cf199d0088b77 Amir Goldstein 2017-06-12  1491  
e9be9d5e76e3487 Miklos Szeredi 2014-10-24  1492  static int __init ovl_init(void)
e9be9d5e76e3487 Miklos Szeredi 2014-10-24  1493  {
13cf199d0088b77 Amir Goldstein 2017-06-12  1494  	int err;
13cf199d0088b77 Amir Goldstein 2017-06-12  1495  
13cf199d0088b77 Amir Goldstein 2017-06-12  1496  	ovl_inode_cachep = kmem_cache_create("ovl_inode",
13cf199d0088b77 Amir Goldstein 2017-06-12  1497  					     sizeof(struct ovl_inode), 0,
13cf199d0088b77 Amir Goldstein 2017-06-12  1498  					     (SLAB_RECLAIM_ACCOUNT|
13cf199d0088b77 Amir Goldstein 2017-06-12 @1499  					      SLAB_MEM_SPREAD|SLAB_ACCOUNT),
13cf199d0088b77 Amir Goldstein 2017-06-12  1500  					     ovl_inode_init_once);
13cf199d0088b77 Amir Goldstein 2017-06-12  1501  	if (ovl_inode_cachep == NULL)
13cf199d0088b77 Amir Goldstein 2017-06-12  1502  		return -ENOMEM;
13cf199d0088b77 Amir Goldstein 2017-06-12  1503  
13cf199d0088b77 Amir Goldstein 2017-06-12  1504  	err = register_filesystem(&ovl_fs_type);
2406a307ac7ddfd Jiufei Xue     2019-11-20  1505  	if (!err)
2406a307ac7ddfd Jiufei Xue     2019-11-20  1506  		return 0;
2406a307ac7ddfd Jiufei Xue     2019-11-20  1507  
13cf199d0088b77 Amir Goldstein 2017-06-12  1508  	kmem_cache_destroy(ovl_inode_cachep);
13cf199d0088b77 Amir Goldstein 2017-06-12  1509  
13cf199d0088b77 Amir Goldstein 2017-06-12  1510  	return err;
e9be9d5e76e3487 Miklos Szeredi 2014-10-24  1511  }
e9be9d5e76e3487 Miklos Szeredi 2014-10-24  1512  

:::::: The code at line 1499 was first introduced by commit
:::::: 13cf199d0088b77ab08a9594df2e73e775317ed2 ovl: allocate an ovl_inode struct

:::::: TO: Amir Goldstein <amir73il@gmail.com>
:::::: CC: Miklos Szeredi <mszeredi@redhat.com>

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2024-02-21 15:34 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=202402212310.KPtSDrRy-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 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.