All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [android-common:android15-6.6-lts 205/205] mm/pagewalk.c:590:5: warning: no previous prototype for 'walk_page_range_debug'
Date: Tue, 17 Nov 2026 20:25:39 +0100	[thread overview]
Message-ID: <20261117201829.3eSjdrxM-lkp@intel.com> (raw)

:::::: 
:::::: Manual check reason: "too many reports for this commit"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: cros-kernel-buildreports@googlegroups.com

Hi Lorenzo,

FYI, the error/warning still remains.

tree:   https://android.googlesource.com/kernel/common android15-6.6-lts
head:   824580839cbc0d47e64dd2bbdef66590a57ef92d
commit: 56a45fdbe5b254d952bdfd9891be3330b831ff0d [205/205] mm/pagewalk: split walk_page_range_novma() into kernel/user parts
:::::: branch date: 30 hours ago
:::::: commit date: 3 months ago
config: x86_64-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20261117/20261117201829.3eSjdrxM-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261117/20261117201829.3eSjdrxM-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/r/20261117201829.3eSjdrxM-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> mm/pagewalk.c:590:5: warning: no previous prototype for 'walk_page_range_debug' [-Wmissing-prototypes]
     590 | int walk_page_range_debug(struct mm_struct *mm, unsigned long start,
         |     ^~~~~~~~~~~~~~~~~~~~~


vim +/walk_page_range_debug +590 mm/pagewalk.c

56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  574  
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  575  /**
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  576   * walk_page_range_debug - walk a range of pagetables not backed by a vma
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  577   * @mm:		mm_struct representing the target process of page table walk
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  578   * @start:	start address of the virtual address range
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  579   * @end:	end address of the virtual address range
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  580   * @ops:	operation to call during the walk
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  581   * @pgd:	pgd to walk if different from mm->pgd
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  582   * @private:	private data for callbacks' usage
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  583   *
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  584   * Similar to walk_page_range() but can walk any page tables even if they are
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  585   * not backed by VMAs. Because 'unusual' entries may be walked this function
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  586   * will also not lock the PTEs for the pte_entry() callback.
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  587   *
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  588   * This is for debugging purposes ONLY.
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  589   */
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14 @590  int walk_page_range_debug(struct mm_struct *mm, unsigned long start,
488ae6a2b933cb5 Steven Price    2020-02-03  591  			  unsigned long end, const struct mm_walk_ops *ops,
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  592  			  pgd_t *pgd, void *private)
488ae6a2b933cb5 Steven Price    2020-02-03  593  {
488ae6a2b933cb5 Steven Price    2020-02-03  594  	struct mm_walk walk = {
488ae6a2b933cb5 Steven Price    2020-02-03  595  		.ops		= ops,
488ae6a2b933cb5 Steven Price    2020-02-03  596  		.mm		= mm,
e47690d756a7605 Steven Price    2020-02-03  597  		.pgd		= pgd,
488ae6a2b933cb5 Steven Price    2020-02-03  598  		.private	= private,
488ae6a2b933cb5 Steven Price    2020-02-03  599  		.no_vma		= true
488ae6a2b933cb5 Steven Price    2020-02-03  600  	};
488ae6a2b933cb5 Steven Price    2020-02-03  601  
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  602  	/* For convenience, we allow traversal of kernel mappings. */
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  603  	if (mm == &init_mm)
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  604  		return walk_kernel_page_table_range(start, end, ops,
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  605  						    pgd, private);
488ae6a2b933cb5 Steven Price    2020-02-03  606  	if (start >= end || !walk.mm)
488ae6a2b933cb5 Steven Price    2020-02-03  607  		return -EINVAL;
488ae6a2b933cb5 Steven Price    2020-02-03  608  
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  609  	/*
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  610  	 * The mmap lock protects the page walker from changes to the page
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  611  	 * tables during the walk.  However a read lock is insufficient to
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  612  	 * protect those areas which don't have a VMA as munmap() detaches
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  613  	 * the VMAs before downgrading to a read lock and actually tearing
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  614  	 * down PTEs/page tables. In which case, the mmap write lock should
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  615  	 * be held.
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  616  	 */
56a45fdbe5b254d Lorenzo Stoakes 2026-08-14  617  	mmap_assert_write_locked(mm);
488ae6a2b933cb5 Steven Price    2020-02-03  618  
8782fb61cc84836 Steven Price    2022-09-02  619  	return walk_pgd_range(start, end, &walk);
488ae6a2b933cb5 Steven Price    2020-02-03  620  }
488ae6a2b933cb5 Steven Price    2020-02-03  621  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-11-17 19:26 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=20261117201829.3eSjdrxM-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild@lists.linux.dev \
    /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.