From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [brauner-github:work.ovl.cred.guard 46/47] fs/overlayfs/util.c:70:9: sparse: sparse: cannot size expression
Date: Sun, 16 Nov 2025 01:13:22 +0800 [thread overview]
Message-ID: <202511160131.7ekHOUWN-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check warning: fs/overlayfs/util.c:70:9: sparse: sparse: cannot size expression"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: Christian Brauner <christianvanbrauner@gmail.com>
TO: Christian Brauner <brauner@kernel.org>
tree: https://github.com/brauner/linux.git work.ovl.cred.guard
head: 74fa97e66e24a79a77ee469a7e8305f2013edd1f
commit: 05caf92703741e332e658d583bddc36d18d0067b [46/47] ovl: detect double credential overrides
:::::: branch date: 2 days ago
:::::: commit date: 2 days ago
config: x86_64-randconfig-r112-20251115 (https://download.01.org/0day-ci/archive/20251116/202511160131.7ekHOUWN-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/20251116/202511160131.7ekHOUWN-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/r/202511160131.7ekHOUWN-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
fs/overlayfs/util.c:70:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
fs/overlayfs/util.c:70:9: sparse: struct cred const [noderef] __rcu *
fs/overlayfs/util.c:70:9: sparse: struct cred const *
fs/overlayfs/util.c:70:9: sparse: sparse: cast from unknown type
>> fs/overlayfs/util.c:70:9: sparse: sparse: cannot size expression
vim +70 fs/overlayfs/util.c
bbb1e54dd53cf8 Miklos Szeredi 2016-12-16 64
bbb1e54dd53cf8 Miklos Szeredi 2016-12-16 65 const struct cred *ovl_override_creds(struct super_block *sb)
bbb1e54dd53cf8 Miklos Szeredi 2016-12-16 66 {
f01d08899fd7fa Andrea Righi 2023-05-21 67 struct ovl_fs *ofs = OVL_FS(sb);
bbb1e54dd53cf8 Miklos Szeredi 2016-12-16 68
05caf92703741e Christian Brauner 2025-11-13 69 /* Detect callchains where we override credentials multiple times. */
05caf92703741e Christian Brauner 2025-11-13 @70 VFS_WARN_ON_ONCE(current->cred == ofs->creator_cred);
6771e004b40962 Christian Brauner 2024-11-25 71 return override_creds(ofs->creator_cred);
bbb1e54dd53cf8 Miklos Szeredi 2016-12-16 72 }
bbb1e54dd53cf8 Miklos Szeredi 2016-12-16 73
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-11-15 17:13 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=202511160131.7ekHOUWN-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@lists.linux.dev \
/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.