From: kernel test robot <lkp@intel.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 2/3] mm, slab: use an enum to define SLAB_ cache creation flags
Date: Thu, 22 Feb 2024 09:54:49 +0800 [thread overview]
Message-ID: <202402220942.XxR0oby3-lkp@intel.com> (raw)
In-Reply-To: <20240220-slab-cleanup-flags-v1-2-e657e373944a@suse.cz>
Hi Vlastimil,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 6613476e225e090cc9aad49be7fa504e290dd33d]
url: https://github.com/intel-lab-lkp/linux/commits/Vlastimil-Babka/mm-slab-deprecate-SLAB_MEM_SPREAD-flag/20240221-005936
base: 6613476e225e090cc9aad49be7fa504e290dd33d
patch link: https://lore.kernel.org/r/20240220-slab-cleanup-flags-v1-2-e657e373944a%40suse.cz
patch subject: [PATCH 2/3] mm, slab: use an enum to define SLAB_ cache creation flags
config: i386-randconfig-r111-20240222 (https://download.01.org/0day-ci/archive/20240222/202402220942.XxR0oby3-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240222/202402220942.XxR0oby3-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/202402220942.XxR0oby3-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> fs/overlayfs/super.c:1499:63: sparse: sparse: restricted slab_flags_t degrades to integer
>> fs/overlayfs/super.c:1499:62: sparse: sparse: incorrect type in argument 4 (different base types) @@ expected restricted slab_flags_t [usertype] flags @@ got unsigned int @@
fs/overlayfs/super.c:1499:62: sparse: expected restricted slab_flags_t [usertype] flags
fs/overlayfs/super.c:1499:62: sparse: got unsigned int
--
>> fs/tracefs/inode.c:793:54: sparse: sparse: restricted slab_flags_t degrades to integer
>> fs/tracefs/inode.c:792:69: sparse: sparse: incorrect type in argument 4 (different base types) @@ expected restricted slab_flags_t [usertype] flags @@ got unsigned int @@
fs/tracefs/inode.c:792:69: sparse: expected restricted slab_flags_t [usertype] flags
fs/tracefs/inode.c:792:69: sparse: got unsigned int
vim +1499 fs/overlayfs/super.c
13cf199d0088b7 Amir Goldstein 2017-06-12 1491
e9be9d5e76e348 Miklos Szeredi 2014-10-24 1492 static int __init ovl_init(void)
e9be9d5e76e348 Miklos Szeredi 2014-10-24 1493 {
13cf199d0088b7 Amir Goldstein 2017-06-12 1494 int err;
13cf199d0088b7 Amir Goldstein 2017-06-12 1495
13cf199d0088b7 Amir Goldstein 2017-06-12 1496 ovl_inode_cachep = kmem_cache_create("ovl_inode",
13cf199d0088b7 Amir Goldstein 2017-06-12 1497 sizeof(struct ovl_inode), 0,
13cf199d0088b7 Amir Goldstein 2017-06-12 1498 (SLAB_RECLAIM_ACCOUNT|
13cf199d0088b7 Amir Goldstein 2017-06-12 @1499 SLAB_MEM_SPREAD|SLAB_ACCOUNT),
13cf199d0088b7 Amir Goldstein 2017-06-12 1500 ovl_inode_init_once);
13cf199d0088b7 Amir Goldstein 2017-06-12 1501 if (ovl_inode_cachep == NULL)
13cf199d0088b7 Amir Goldstein 2017-06-12 1502 return -ENOMEM;
13cf199d0088b7 Amir Goldstein 2017-06-12 1503
13cf199d0088b7 Amir Goldstein 2017-06-12 1504 err = register_filesystem(&ovl_fs_type);
2406a307ac7ddf Jiufei Xue 2019-11-20 1505 if (!err)
2406a307ac7ddf Jiufei Xue 2019-11-20 1506 return 0;
2406a307ac7ddf Jiufei Xue 2019-11-20 1507
13cf199d0088b7 Amir Goldstein 2017-06-12 1508 kmem_cache_destroy(ovl_inode_cachep);
13cf199d0088b7 Amir Goldstein 2017-06-12 1509
13cf199d0088b7 Amir Goldstein 2017-06-12 1510 return err;
e9be9d5e76e348 Miklos Szeredi 2014-10-24 1511 }
e9be9d5e76e348 Miklos Szeredi 2014-10-24 1512
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-02-22 1:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 16:58 [PATCH 0/3] cleanup of SLAB_ flags Vlastimil Babka
2024-02-20 16:58 ` [PATCH 1/3] mm, slab: deprecate SLAB_MEM_SPREAD flag Vlastimil Babka
2024-02-21 2:17 ` Song, Xiongwei
2024-02-21 7:11 ` Chengming Zhou
2024-02-21 18:30 ` Roman Gushchin
2024-02-22 1:10 ` Song, Xiongwei
2024-02-22 2:32 ` Chengming Zhou
2024-02-22 3:13 ` Song, Xiongwei
2024-02-23 16:41 ` Vlastimil Babka
2024-02-24 9:32 ` Chengming Zhou
2024-02-20 16:58 ` [PATCH 2/3] mm, slab: use an enum to define SLAB_ cache creation flags Vlastimil Babka
2024-02-21 2:23 ` Song, Xiongwei
2024-02-21 7:13 ` Chengming Zhou
2024-02-21 18:33 ` Roman Gushchin
2024-02-23 16:42 ` Vlastimil Babka
2024-02-21 22:19 ` Vlastimil Babka
2024-02-22 1:54 ` kernel test robot
2024-02-22 1:54 ` kernel test robot [this message]
2024-02-23 3:12 ` Christoph Lameter (Ampere)
2024-02-23 16:43 ` Vlastimil Babka
2024-02-23 17:06 ` Vlastimil Babka
2024-02-20 16:58 ` [PATCH 3/3] mm, slab, kasan: replace kasan_never_merge() with SLAB_NO_MERGE Vlastimil Babka
2024-02-21 2:25 ` Song, Xiongwei
2024-02-21 7:14 ` Chengming Zhou
2024-02-21 20:48 ` Andrey Konovalov
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=202402220942.XxR0oby3-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.