From: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
To: kernel test robot <lkp@intel.com>, Nico Boehr <nrb@linux.ibm.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Heiko Carstens <hca@linux.ibm.com>
Subject: Re: arch/s390/lib/uaccess.c:65:15: error: variable 'spec' has initializer but incomplete type
Date: Mon, 24 Jan 2022 09:27:49 +0100 [thread overview]
Message-ID: <2537ad58-675f-c05d-04e4-07358e92c7c3@linux.ibm.com> (raw)
In-Reply-To: <202201221613.fgIWUw0F-lkp@intel.com>
On 1/22/22 09:42, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 9b57f458985742bd1c585f4c7f36d04634ce1143
> commit: 012a224e1fa31fc256aab921f691598e03db6018 s390/uaccess: introduce bit field for OAC specifier
> date: 5 days ago
> config: s390-randconfig-r033-20220120 (https://download.01.org/0day-ci/archive/20220122/202201221613.fgIWUw0F-lkp@intel.com/config)
> compiler: s390-linux-gcc (GCC) 11.2.0
> reproduce (this is a W=1 build):
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=012a224e1fa31fc256aab921f691598e03db6018
> git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> git fetch --no-tags linus master
> git checkout 012a224e1fa31fc256aab921f691598e03db6018
> # save the config file to linux build tree
> mkdir build_dir
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=s390 SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> arch/s390/lib/uaccess.c: In function 'copy_from_user_mvcos':
>>> arch/s390/lib/uaccess.c:65:15: error: variable 'spec' has initializer but incomplete type
> 65 | union oac spec = {
> | ^~~
>>> arch/s390/lib/uaccess.c:66:18: error: 'union oac' has no member named 'oac2'
> 66 | .oac2.as = PSW_BITS_AS_SECONDARY,
> | ^~~~
> arch/s390/lib/uaccess.c:66:28: warning: excess elements in union initializer
> 66 | .oac2.as = PSW_BITS_AS_SECONDARY,
> | ^~~~~~~~~~~~~~~~~~~~~
> arch/s390/lib/uaccess.c:66:28: note: (near initialization for 'spec')
> arch/s390/lib/uaccess.c:67:18: error: 'union oac' has no member named 'oac2'
> 67 | .oac2.a = 1,
> | ^~~~
> arch/s390/lib/uaccess.c:67:27: warning: excess elements in union initializer
> 67 | .oac2.a = 1,
> | ^
> arch/s390/lib/uaccess.c:67:27: note: (near initialization for 'spec')
>>> arch/s390/lib/uaccess.c:65:19: error: storage size of 'spec' isn't known
> 65 | union oac spec = {
> | ^~~~
> arch/s390/lib/uaccess.c:65:19: warning: unused variable 'spec' [-Wunused-variable]
> arch/s390/lib/uaccess.c: In function 'copy_to_user_mvcos':
> arch/s390/lib/uaccess.c:142:15: error: variable 'spec' has initializer but incomplete type
> 142 | union oac spec = {
> | ^~~
>>> arch/s390/lib/uaccess.c:143:18: error: 'union oac' has no member named 'oac1'
> 143 | .oac1.as = PSW_BITS_AS_SECONDARY,
> | ^~~~
> arch/s390/lib/uaccess.c:143:28: warning: excess elements in union initializer
> 143 | .oac1.as = PSW_BITS_AS_SECONDARY,
> | ^~~~~~~~~~~~~~~~~~~~~
> arch/s390/lib/uaccess.c:143:28: note: (near initialization for 'spec')
> arch/s390/lib/uaccess.c:144:18: error: 'union oac' has no member named 'oac1'
> 144 | .oac1.a = 1,
> | ^~~~
> arch/s390/lib/uaccess.c:144:27: warning: excess elements in union initializer
> 144 | .oac1.a = 1,
> | ^
> arch/s390/lib/uaccess.c:144:27: note: (near initialization for 'spec')
> arch/s390/lib/uaccess.c:142:19: error: storage size of 'spec' isn't known
> 142 | union oac spec = {
> | ^~~~
> arch/s390/lib/uaccess.c:142:19: warning: unused variable 'spec' [-Wunused-variable]
> arch/s390/lib/uaccess.c: In function 'clear_user_mvcos':
> arch/s390/lib/uaccess.c:218:15: error: variable 'spec' has initializer but incomplete type
> 218 | union oac spec = {
> | ^~~
> arch/s390/lib/uaccess.c:219:18: error: 'union oac' has no member named 'oac1'
> 219 | .oac1.as = PSW_BITS_AS_SECONDARY,
> | ^~~~
> arch/s390/lib/uaccess.c:219:28: warning: excess elements in union initializer
> 219 | .oac1.as = PSW_BITS_AS_SECONDARY,
> | ^~~~~~~~~~~~~~~~~~~~~
> arch/s390/lib/uaccess.c:219:28: note: (near initialization for 'spec')
> arch/s390/lib/uaccess.c:220:18: error: 'union oac' has no member named 'oac1'
> 220 | .oac1.a = 1,
> | ^~~~
> arch/s390/lib/uaccess.c:220:27: warning: excess elements in union initializer
> 220 | .oac1.a = 1,
> | ^
> arch/s390/lib/uaccess.c:220:27: note: (near initialization for 'spec')
> arch/s390/lib/uaccess.c:218:19: error: storage size of 'spec' isn't known
> 218 | union oac spec = {
> | ^~~~
> arch/s390/lib/uaccess.c:218:19: warning: unused variable 'spec' [-Wunused-variable]
This is caused by the union definition being covered by the #ifdef CONFIG_HAVE_MARCH_Z10_FEATURES.
prev parent reply other threads:[~2022-01-24 8:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 8:42 kernel test robot
2022-01-24 8:27 ` Janis Schoetterl-Glausch [this message]
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=2537ad58-675f-c05d-04e4-07358e92c7c3@linux.ibm.com \
--to=scgl@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=nrb@linux.ibm.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
all inboxes | Powered by JetHome®