All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Benjamin Berg <benjamin.berg@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, Johannes Berg <johannes.berg@intel.com>
Subject: [uml:next 44/50] arch/x86/um/ptrace.c:245:31: sparse: sparse: symbol 'user_uml_view' was not declared. Should it be static?
Date: Mon, 28 Oct 2024 18:37:13 +0800	[thread overview]
Message-ID: <202410281821.WSPsAwq7-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/uml/linux next
head:   d3b08e5f3f2829943342b88d3e2b44fb0ccdccab
commit: 3f17fed2149192c7d3b76a45a6a87b4ff22cd586 [44/50] um: switch to regset API and depend on XSTATE
config: um-randconfig-r112-20241026 (https://download.01.org/0day-ci/archive/20241028/202410281821.WSPsAwq7-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/20241028/202410281821.WSPsAwq7-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/202410281821.WSPsAwq7-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> arch/x86/um/ptrace.c:245:31: sparse: sparse: symbol 'user_uml_view' was not declared. Should it be static?
--
>> arch/x86/um/signal.c:87:19: sparse: sparse: incorrect type in assignment (different address spaces) @@     expected struct _xstate [noderef] __user *from_fp64 @@     got void * @@
   arch/x86/um/signal.c:87:19: sparse:     expected struct _xstate [noderef] __user *from_fp64
   arch/x86/um/signal.c:87:19: sparse:     got void *
   arch/x86/um/signal.c:201:9: sparse: sparse: cast removes address space '__user' of expression
   arch/x86/um/signal.c:201:9: sparse: sparse: cast removes address space '__user' of expression
>> arch/x86/um/signal.c:201:9: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void const volatile [noderef] __user *ptr @@     got int * @@
   arch/x86/um/signal.c:201:9: sparse:     expected void const volatile [noderef] __user *ptr
   arch/x86/um/signal.c:201:9: sparse:     got int *
   arch/x86/um/signal.c:201:9: sparse: sparse: cast removes address space '__user' of expression
   arch/x86/um/signal.c:201:9: sparse: sparse: cast removes address space '__user' of expression
   arch/x86/um/signal.c:201:9: sparse: sparse: cast removes address space '__user' of expression
>> arch/x86/um/signal.c:201:9: sparse: sparse: incorrect type in argument 2 (different address spaces) @@     expected void [noderef] __user *ptr @@     got int * @@
   arch/x86/um/signal.c:201:9: sparse:     expected void [noderef] __user *ptr
   arch/x86/um/signal.c:201:9: sparse:     got int *
   arch/x86/um/signal.c:387:16: sparse: sparse: Using plain integer as NULL pointer
   arch/x86/um/signal.c:411:24: sparse: sparse: cast removes address space '__user' of expression
   arch/x86/um/signal.c:411:24: sparse: sparse: incorrect type in initializer (different address spaces) @@     expected char [noderef] __user *__x @@     got void * @@
   arch/x86/um/signal.c:411:24: sparse:     expected char [noderef] __user *__x
   arch/x86/um/signal.c:411:24: sparse:     got void *

vim +/user_uml_view +245 arch/x86/um/ptrace.c

   244	
 > 245	const struct user_regset_view user_uml_view = {
   246	#ifdef CONFIG_X86_32
   247		.name = "i386", .e_machine = EM_386,
   248	#else
   249		.name = "x86_64", .e_machine = EM_X86_64,
   250	#endif
   251		.regsets = uml_regsets, .n = ARRAY_SIZE(uml_regsets)
   252	};
   253	

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

                 reply	other threads:[~2024-10-28 10:37 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=202410281821.WSPsAwq7-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=benjamin.berg@intel.com \
    --cc=johannes.berg@intel.com \
    --cc=oe-kbuild-all@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.