GNU/Weeb Mailing List <[email protected]>
 help / color / mirror / Atom feed
From: kernel test robot <[email protected]>
To: Palmer Dabbelt <[email protected]>
Cc: [email protected], [email protected],
	Ammar Faizi <[email protected]>,
	GNU/Weeb Mailing List <[email protected]>,
	[email protected]
Subject: [ammarfaizi2-block:palmer/linux/vdso-fix-v3 9/9] arch/riscv/kernel/vdso.c:26:27: warning: tentative definition of variable with internal linkage has incomplete non-array type 'struct __vdso_info'
Date: Fri, 16 Sep 2022 22:22:52 +0800	[thread overview]
Message-ID: <[email protected]> (raw)

tree:   https://github.com/ammarfaizi2/linux-block palmer/linux/vdso-fix-v3
head:   fcbe4db4bf998e22fc7a35a2e02f6ba3d5ffb5db
commit: fcbe4db4bf998e22fc7a35a2e02f6ba3d5ffb5db [9/9] WIP: riscv: vdso: fix NULL deference in vdso_join_timens() when vfork
config: riscv-randconfig-r022-20220916 (https://download.01.org/0day-ci/archive/20220916/[email protected]/config)
compiler: clang version 16.0.0 (https://github.com/llvm/llvm-project 791a7ae1ba3efd6bca96338e10ffde557ba83920)
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
        # install riscv cross compiling tool for clang build
        # apt-get install binutils-riscv64-linux-gnu
        # https://github.com/ammarfaizi2/linux-block/commit/fcbe4db4bf998e22fc7a35a2e02f6ba3d5ffb5db
        git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
        git fetch --no-tags ammarfaizi2-block palmer/linux/vdso-fix-v3
        git checkout fcbe4db4bf998e22fc7a35a2e02f6ba3d5ffb5db
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=riscv SHELL=/bin/bash arch/riscv/kernel/ drivers/char/pcmcia/

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <[email protected]>

All warnings (new ones prefixed by >>):

>> arch/riscv/kernel/vdso.c:26:27: warning: tentative definition of variable with internal linkage has incomplete non-array type 'struct __vdso_info' [-Wtentative-definition-incomplete-type]
   static struct __vdso_info vdso_info;
                             ^
   arch/riscv/kernel/vdso.c:26:15: note: forward declaration of 'struct __vdso_info'
   static struct __vdso_info vdso_info;
                 ^
   arch/riscv/kernel/vdso.c:29:27: warning: tentative definition of variable with internal linkage has incomplete non-array type 'struct __vdso_info' [-Wtentative-definition-incomplete-type]
   static struct __vdso_info compat_vdso_info;
                             ^
   arch/riscv/kernel/vdso.c:26:15: note: forward declaration of 'struct __vdso_info'
   static struct __vdso_info vdso_info;
                 ^
   2 warnings generated.


vim +26 arch/riscv/kernel/vdso.c

    24	
    25	extern char vdso_start[], vdso_end[];
  > 26	static struct __vdso_info vdso_info;
    27	#ifdef CONFIG_COMPAT
    28	extern char compat_vdso_start[], compat_vdso_end[];
    29	static struct __vdso_info compat_vdso_info;
    30	#endif
    31	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

                 reply	other threads:[~2022-09-16 14:22 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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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