public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Nick Kossifidis <mick@ics.forth.gr>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	linux-kernel@vger.kernel.org,
	Palmer Dabbelt <palmerdabbelt@google.com>
Subject: fs/proc/vmcore.c:443:42: warning: unused variable 'vmcore_mmap_ops'
Date: Fri, 29 Apr 2022 06:33:32 +0800	[thread overview]
Message-ID: <202204290642.I2dLZBgO-lkp@intel.com> (raw)

Hi Nick,

First bad commit (maybe != root cause):

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   249aca0d3d631660aa3583c6a3559b75b6e971b4
commit: 5640975003d0234da08559677e22ec25b9cb3267 RISC-V: Add crash kernel support
date:   1 year ago
config: riscv-randconfig-c006-20220428 (https://download.01.org/0day-ci/archive/20220429/202204290642.I2dLZBgO-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project c59473aacce38cd7dd77eebceaf3c98c5707ab3b)
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://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5640975003d0234da08559677e22ec25b9cb3267
        git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
        git fetch --no-tags linus master
        git checkout 5640975003d0234da08559677e22ec25b9cb3267
        # save the config file
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross 

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

All warnings (new ones prefixed by >>):

>> fs/proc/vmcore.c:443:42: warning: unused variable 'vmcore_mmap_ops' [-Wunused-const-variable]
   static const struct vm_operations_struct vmcore_mmap_ops = {
                                            ^
   8 warnings generated.


vim +/vmcore_mmap_ops +443 fs/proc/vmcore.c

9cb218131de1c59 Michael Holzheu 2013-09-11  442  
9cb218131de1c59 Michael Holzheu 2013-09-11 @443  static const struct vm_operations_struct vmcore_mmap_ops = {
9cb218131de1c59 Michael Holzheu 2013-09-11  444  	.fault = mmap_vmcore_fault,
9cb218131de1c59 Michael Holzheu 2013-09-11  445  };
9cb218131de1c59 Michael Holzheu 2013-09-11  446  

:::::: The code at line 443 was first introduced by commit
:::::: 9cb218131de1c59dca9063b2efe876f053f316af vmcore: introduce remap_oldmem_pfn_range()

:::::: TO: Michael Holzheu <holzheu@linux.vnet.ibm.com>
:::::: CC: Linus Torvalds <torvalds@linux-foundation.org>

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

             reply	other threads:[~2022-04-28 22:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28 22:33 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-11-18  5:02 fs/proc/vmcore.c:443:42: warning: unused variable 'vmcore_mmap_ops' kernel test robot
2021-05-11 10:33 kernel test robot

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=202204290642.I2dLZBgO-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=mick@ics.forth.gr \
    --cc=palmerdabbelt@google.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