linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Vinicius Costa Gomes <vinicius.gomes@intel.com>,
	brauner@kernel.org, amir73il@gmail.com, hu1.chen@intel.com
Cc: oe-kbuild-all@lists.linux.dev, miklos@szeredi.hu,
	malini.bhandaru@intel.com, tim.c.chen@intel.com,
	mikko.ylinen@intel.com, linux-unionfs@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Vinicius Costa Gomes <vinicius.gomes@intel.com>
Subject: Re: [PATCH overlayfs-next v3 1/4] cred: Add a light version of override/revert_creds()
Date: Thu, 7 Nov 2024 02:56:30 +0800	[thread overview]
Message-ID: <202411070234.EOrhSGRU-lkp@intel.com> (raw)
In-Reply-To: <20241105193514.828616-2-vinicius.gomes@intel.com>

Hi Vinicius,

kernel test robot noticed the following build warnings:

[auto build test WARNING on next-20241105]
[also build test WARNING on v6.12-rc6]
[cannot apply to brauner-vfs/vfs.all linus/master v6.12-rc6 v6.12-rc5 v6.12-rc4]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Vinicius-Costa-Gomes/cred-Add-a-light-version-of-override-revert_creds/20241106-033748
base:   next-20241105
patch link:    https://lore.kernel.org/r/20241105193514.828616-2-vinicius.gomes%40intel.com
patch subject: [PATCH overlayfs-next v3 1/4] cred: Add a light version of override/revert_creds()
config: x86_64-randconfig-121-20241106 (https://download.01.org/0day-ci/archive/20241107/202411070234.EOrhSGRU-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241107/202411070234.EOrhSGRU-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/202411070234.EOrhSGRU-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
   kernel/cred.c:104:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/cred.c:104:9: sparse:    struct cred *
   kernel/cred.c:104:9: sparse:    struct cred const [noderef] __rcu *
   kernel/cred.c:105:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/cred.c:105:9: sparse:    struct cred *
   kernel/cred.c:105:9: sparse:    struct cred const [noderef] __rcu *
   kernel/cred.c:121:9: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected struct atomic64_t const [usertype] *v @@     got struct atomic64_t const [noderef] __rcu * @@
   kernel/cred.c:121:9: sparse:     expected struct atomic64_t const [usertype] *v
   kernel/cred.c:121:9: sparse:     got struct atomic64_t const [noderef] __rcu *
   kernel/cred.c:124:22: sparse: sparse: cast removes address space '__rcu' of expression
   kernel/cred.c:127:17: sparse: sparse: cast removes address space '__rcu' of expression
   kernel/cred.c:218:13: sparse: sparse: incorrect type in assignment (different address spaces) @@     expected struct cred const *old @@     got struct cred const [noderef] __rcu *cred @@
   kernel/cred.c:218:13: sparse:     expected struct cred const *old
   kernel/cred.c:218:13: sparse:     got struct cred const [noderef] __rcu *cred
   kernel/cred.c:305:47: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected struct cred const *cred @@     got struct cred const [noderef] __rcu *cred @@
   kernel/cred.c:305:47: sparse:     expected struct cred const *cred
   kernel/cred.c:305:47: sparse:     got struct cred const [noderef] __rcu *cred
   kernel/cred.c:305:30: sparse: sparse: incorrect type in assignment (different address spaces) @@     expected struct cred const [noderef] __rcu *real_cred @@     got struct cred const * @@
   kernel/cred.c:305:30: sparse:     expected struct cred const [noderef] __rcu *real_cred
   kernel/cred.c:305:30: sparse:     got struct cred const *
   kernel/cred.c:306:17: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected struct atomic64_t const [usertype] *v @@     got struct atomic64_t const [noderef] __rcu * @@
   kernel/cred.c:306:17: sparse:     expected struct atomic64_t const [usertype] *v
   kernel/cred.c:306:17: sparse:     got struct atomic64_t const [noderef] __rcu *
   kernel/cred.c:344:32: sparse: sparse: incorrect type in assignment (different address spaces) @@     expected struct cred const [noderef] __rcu *real_cred @@     got struct cred const * @@
   kernel/cred.c:344:32: sparse:     expected struct cred const [noderef] __rcu *real_cred
   kernel/cred.c:344:32: sparse:     got struct cred const *
   kernel/cred.c:395:38: sparse: sparse: incorrect type in initializer (different address spaces) @@     expected struct cred const *old @@     got struct cred const [noderef] __rcu *real_cred @@
   kernel/cred.c:395:38: sparse:     expected struct cred const *old
   kernel/cred.c:395:38: sparse:     got struct cred const [noderef] __rcu *real_cred
   kernel/cred.c:400:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/cred.c:400:9: sparse:    struct cred const [noderef] __rcu *
   kernel/cred.c:400:9: sparse:    struct cred const *
   kernel/cred.c:519:46: sparse: sparse: incorrect type in initializer (different address spaces) @@     expected struct cred const *override @@     got struct cred const [noderef] __rcu *cred @@
   kernel/cred.c:519:46: sparse:     expected struct cred const *override
   kernel/cred.c:519:46: sparse:     got struct cred const [noderef] __rcu *cred
   kernel/cred.c:301:19: sparse: sparse: dereference of noderef expression
   kernel/cred.c: note: in included file:
>> include/linux/cred.h:182:41: sparse: sparse: incorrect type in initializer (different address spaces) @@     expected struct cred const *old @@     got struct cred const [noderef] __rcu *cred @@
   include/linux/cred.h:182:41: sparse:     expected struct cred const *old
   include/linux/cred.h:182:41: sparse:     got struct cred const [noderef] __rcu *cred

vim +182 include/linux/cred.h

   174	
   175	/*
   176	 * Override creds without bumping reference count. Caller must ensure
   177	 * reference remains valid or has taken reference. Almost always not the
   178	 * interface you want. Use override_creds()/revert_creds() instead.
   179	 */
   180	static inline const struct cred *override_creds_light(const struct cred *override_cred)
   181	{
 > 182		const struct cred *old = current->cred;
   183	
   184		rcu_assign_pointer(current->cred, override_cred);
   185		return old;
   186	}
   187	

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

  reply	other threads:[~2024-11-06 18:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-05 19:35 [PATCH overlayfs-next v3 0/4] overlayfs: Optimize override/revert creds Vinicius Costa Gomes
2024-11-05 19:35 ` [PATCH overlayfs-next v3 1/4] cred: Add a light version of override/revert_creds() Vinicius Costa Gomes
2024-11-06 18:56   ` kernel test robot [this message]
2024-11-05 19:35 ` [PATCH overlayfs-next v3 2/4] fs/backing-file: Convert to revert/override_creds_light() Vinicius Costa Gomes
2024-11-05 19:35 ` [PATCH overlayfs-next v3 3/4] fs/overlayfs: Optimize override/revert creds Vinicius Costa Gomes
2024-11-05 19:35 ` [PATCH overlayfs-next v3 4/4] fs/overlayfs: Drop creds usage decrement for ovl_setup_for_create() Vinicius Costa Gomes
2024-11-05 20:47 ` [PATCH overlayfs-next v3 0/4] overlayfs: Optimize override/revert creds Amir Goldstein
2024-11-05 22:27   ` Vinicius Costa Gomes

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=202411070234.EOrhSGRU-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=amir73il@gmail.com \
    --cc=brauner@kernel.org \
    --cc=hu1.chen@intel.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=malini.bhandaru@intel.com \
    --cc=mikko.ylinen@intel.com \
    --cc=miklos@szeredi.hu \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tim.c.chen@intel.com \
    --cc=vinicius.gomes@intel.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;
as well as URLs for NNTP newsgroup(s).