All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Joey Gouly <joey.gouly@arm.com>
Cc: kbuild-all@lists.01.org, Ammar Faizi <ammarfaizi2@gnuweeb.org>,
	GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
	linux-kernel@vger.kernel.org,
	Catalin Marinas <catalin.marinas@arm.com>
Subject: [ammarfaizi2-block:arm64/linux/for-next/gettimeofday 2/3] arch/arm64/kernel/alternative.c:198:6: warning: no previous prototype for 'apply_alternatives_vdso'
Date: Sat, 10 Sep 2022 11:49:29 +0800	[thread overview]
Message-ID: <202209101157.EfOSTasF-lkp@intel.com> (raw)

tree:   https://github.com/ammarfaizi2/linux-block arm64/linux/for-next/gettimeofday
head:   9025cebf12d1763de36d5e09e2b0a1e4f9b13b28
commit: 4e3bca8f7cdd3b658ee7ad700fdce95b5e13a441 [2/3] arm64: alternative: patch alternatives in the vDSO
config: arm64-buildonly-randconfig-r001-20220907 (https://download.01.org/0day-ci/archive/20220910/202209101157.EfOSTasF-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 12.1.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://github.com/ammarfaizi2/linux-block/commit/4e3bca8f7cdd3b658ee7ad700fdce95b5e13a441
        git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
        git fetch --no-tags ammarfaizi2-block arm64/linux/for-next/gettimeofday
        git checkout 4e3bca8f7cdd3b658ee7ad700fdce95b5e13a441
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arm64 SHELL=/bin/bash arch/arm64/kernel/

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

All warnings (new ones prefixed by >>):

>> arch/arm64/kernel/alternative.c:198:6: warning: no previous prototype for 'apply_alternatives_vdso' [-Wmissing-prototypes]
     198 | void apply_alternatives_vdso(void)
         |      ^~~~~~~~~~~~~~~~~~~~~~~


vim +/apply_alternatives_vdso +198 arch/arm64/kernel/alternative.c

   197	
 > 198	void apply_alternatives_vdso(void)
   199	{
   200		struct alt_region region;
   201		const struct elf64_hdr *hdr;
   202		const struct elf64_shdr *shdr;
   203		const struct elf64_shdr *alt;
   204		DECLARE_BITMAP(all_capabilities, ARM64_NPATCHABLE);
   205	
   206		bitmap_fill(all_capabilities, ARM64_NPATCHABLE);
   207	
   208		hdr = (struct elf64_hdr *)vdso_start;
   209		shdr = (void *)hdr + hdr->e_shoff;
   210		alt = find_section(hdr, shdr, ".altinstructions");
   211		if (!alt)
   212			return;
   213	
   214		region = (struct alt_region){
   215			.begin	= (void *)hdr + alt->sh_offset,
   216			.end	= (void *)hdr + alt->sh_offset + alt->sh_size,
   217		};
   218	
   219		__apply_alternatives(&region, false, &all_capabilities[0]);
   220	}
   221	

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

                 reply	other threads:[~2022-09-10  3:49 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=202209101157.EfOSTasF-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=ammarfaizi2@gnuweeb.org \
    --cc=catalin.marinas@arm.com \
    --cc=gwml@vger.gnuweeb.org \
    --cc=joey.gouly@arm.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.