linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [tglx-devel:x86/fpu 63/77] arch/x86/kernel/signal.c:931:17: sparse: sparse: incorrect type in argument 1 (different address spaces)
@ 2021-10-11  7:00 kernel test robot
  0 siblings, 0 replies; only message in thread
From: kernel test robot @ 2021-10-11  7:00 UTC (permalink / raw)
  To: Thomas Gleixner; +Cc: kbuild-all, linux-kernel

[-- Attachment #1: Type: text/plain, Size: 3089 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git x86/fpu
head:   a365ccb2764d58791ee5946b16fa0ffceb17021f
commit: 09ee55699174bd06f70b1e859d666879a14185d3 [63/77] x86/signal: Use fpu::__state_user_size for sigalt stack validation
config: x86_64-randconfig-s031-20211011 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.4-dirty
        # https://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git/commit/?id=09ee55699174bd06f70b1e859d666879a14185d3
        git remote add tglx-devel https://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git
        git fetch --no-tags tglx-devel x86/fpu
        git checkout 09ee55699174bd06f70b1e859d666879a14185d3
        # save the attached .config to linux build tree
        make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=x86_64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>


sparse warnings: (new ones prefixed by >>)
   arch/x86/kernel/signal.c:917:39: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected struct spinlock [usertype] *lock @@     got struct spinlock [noderef] __rcu * @@
   arch/x86/kernel/signal.c:917:39: sparse:     expected struct spinlock [usertype] *lock
   arch/x86/kernel/signal.c:917:39: sparse:     got struct spinlock [noderef] __rcu *
   arch/x86/kernel/signal.c:923:41: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected struct spinlock [usertype] *lock @@     got struct spinlock [noderef] __rcu * @@
   arch/x86/kernel/signal.c:923:41: sparse:     expected struct spinlock [usertype] *lock
   arch/x86/kernel/signal.c:923:41: sparse:     got struct spinlock [noderef] __rcu *
>> arch/x86/kernel/signal.c:931:17: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected struct lockdep_map const *lock @@     got struct lockdep_map [noderef] __rcu * @@
   arch/x86/kernel/signal.c:931:17: sparse:     expected struct lockdep_map const *lock
   arch/x86/kernel/signal.c:931:17: sparse:     got struct lockdep_map [noderef] __rcu *
   arch/x86/kernel/signal.c:916:9: sparse: sparse: context imbalance in 'sigaltstack_lock' - wrong count at exit
   arch/x86/kernel/signal.c: note: in included file (through include/linux/sched.h):
   arch/x86/include/asm/current.h:15:16: sparse: sparse: context imbalance in 'sigaltstack_unlock' - unexpected unlock

vim +931 arch/x86/kernel/signal.c

   925	
   926	bool sigaltstack_size_valid(size_t ss_size)
   927	{
   928		if (fpu_state_size_dynamic()) {
   929			unsigned long fsize = max_frame_size - fpu_default_state_size;
   930	
 > 931			lockdep_assert_held(&current->sighand->siglock);
   932	
   933			fsize += current->group_leader->thread.fpu.__user_state_size;
   934			return ss_size > fsize;
   935		}
   936		return true;
   937	}
   938	#endif
   939	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 36646 bytes --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2021-10-11  7:03 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-10-11  7:00 [tglx-devel:x86/fpu 63/77] arch/x86/kernel/signal.c:931:17: sparse: sparse: incorrect type in argument 1 (different address spaces) kernel test robot

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).