public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [willy-pagecache:for-next 34/106] kernel/events/uprobes.c:793:22: error: 'struct address_space' has no member named 'ops'; did you mean 'a_ops'?
Date: Mon, 9 May 2022 19:36:50 +0800	[thread overview]
Message-ID: <202205091929.FnbrVrc0-lkp@intel.com> (raw)

tree:   git://git.infradead.org/users/willy/pagecache for-next
head:   aa4aa19cc518a24bec4de5ff7caaf212d0091805
commit: 0e03bd90d662c215ce99813a175df0e4fd074f5c [34/106] fs: Introduce aops->read_folio
config: mips-allyesconfig (https://download.01.org/0day-ci/archive/20220509/202205091929.FnbrVrc0-lkp@intel.com/config)
compiler: mips-linux-gcc (GCC) 11.3.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
        git remote add willy-pagecache git://git.infradead.org/users/willy/pagecache
        git fetch --no-tags willy-pagecache for-next
        git checkout 0e03bd90d662c215ce99813a175df0e4fd074f5c
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=mips SHELL=/bin/bash

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

Note: the willy-pagecache/for-next HEAD aa4aa19cc518a24bec4de5ff7caaf212d0091805 builds fine.
      It only hurts bisectability.

All errors (new ones prefixed by >>):

   kernel/events/uprobes.c: In function '__copy_insn':
>> kernel/events/uprobes.c:793:22: error: 'struct address_space' has no member named 'ops'; did you mean 'a_ops'?
     793 |         if (mapping->ops->read_folio || mapping->a_ops->readpage)
         |                      ^~~
         |                      a_ops


vim +793 kernel/events/uprobes.c

   783	
   784	static int __copy_insn(struct address_space *mapping, struct file *filp,
   785				void *insn, int nbytes, loff_t offset)
   786	{
   787		struct page *page;
   788		/*
   789		 * Ensure that the page that has the original instruction is populated
   790		 * and in page-cache. If ->readpage == NULL it must be shmem_mapping(),
   791		 * see uprobe_register().
   792		 */
 > 793		if (mapping->ops->read_folio || mapping->a_ops->readpage)
   794			page = read_mapping_page(mapping, offset >> PAGE_SHIFT, filp);
   795		else
   796			page = shmem_read_mapping_page(mapping, offset >> PAGE_SHIFT);
   797		if (IS_ERR(page))
   798			return PTR_ERR(page);
   799	
   800		copy_from_page(page, offset, insn, nbytes);
   801		put_page(page);
   802	
   803		return 0;
   804	}
   805	

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

                 reply	other threads:[~2022-05-09 11: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=202205091929.FnbrVrc0-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox