From: kernel test robot <lkp@intel.com>
To: "David Hildenbrand (Red Hat)" <david@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [davidhildenbrand:hugetlb_unshare 7/8] mm/rmap.c:1877:24: error: use of undeclared identifier 'range'
Date: Thu, 20 Nov 2025 21:13:30 +0800 [thread overview]
Message-ID: <202511202119.DaZbZygy-lkp@intel.com> (raw)
tree: https://github.com/davidhildenbrand/linux hugetlb_unshare
head: f73f34e9b553d94cf3030e2674fbf2dab619181a
commit: b9189040ca4a05c8025ecff5b70a7895018d34e5 [7/8] mm/rmap: factor out PMD table unsharing into try_to_unshare_hugetlb_pmd_table()
config: x86_64-allnoconfig (https://download.01.org/0day-ci/archive/20251120/202511202119.DaZbZygy-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251120/202511202119.DaZbZygy-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/oe-kbuild-all/202511202119.DaZbZygy-lkp@intel.com/
All errors (new ones prefixed by >>):
mm/rmap.c:1873:31: error: use of undeclared identifier 'tlb'
1873 | unshared = huge_pmd_unshare(&tlb, vma, address);
| ^
>> mm/rmap.c:1877:24: error: use of undeclared identifier 'range'
1877 | flush_tlb_range(vma, range.start, range.end);
| ^
mm/rmap.c:1877:37: error: use of undeclared identifier 'range'
1877 | flush_tlb_range(vma, range.start, range.end);
| ^
3 errors generated.
vim +/range +1877 mm/rmap.c
1848
1849 static bool try_to_unshare_hugetlb_pmd_table(struct vm_area_struct *vma,
1850 unsigned long address, enum ttu_flags flags,
1851 struct page_vma_mapped_walk *pvmw, bool *ret)
1852 {
1853 bool unshared;
1854
1855 if (!IS_ENABLED(CONFIG_HUGETLB_PMD_PAGE_TABLE_SHARING))
1856 return false;
1857
1858 /*
1859 * To call huge_pmd_unshare, i_mmap_rwsem must be held in write mode.
1860 * Callers needs to explicitly do this outside rmap routines.
1861 *
1862 * We also must hold hugetlb vma_lock in write mode. Lock order dictates
1863 * acquiring vma_lock BEFORE i_mmap_rwsem. We can only try lock here
1864 * and fail if unsuccessful.
1865 */
1866 VM_WARN_ON_ONCE(!(flags & TTU_RMAP_LOCKED));
1867 if (!hugetlb_vma_trylock_write(vma)) {
1868 page_vma_mapped_walk_done(pvmw);
1869 *ret = false;
1870 return true;
1871 }
1872
1873 unshared = huge_pmd_unshare(&tlb, vma, address);
1874 hugetlb_vma_unlock_write(vma);
1875
1876 if (unshared) {
> 1877 flush_tlb_range(vma, range.start, range.end);
1878 /*
1879 * The PMD table was unmapped, consequently unmapping the
1880 * folio.
1881 */
1882 page_vma_mapped_walk_done(pvmw);
1883 }
1884 return unshared;
1885 }
1886
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-11-20 13:14 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=202511202119.DaZbZygy-lkp@intel.com \
--to=lkp@intel.com \
--cc=david@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).