From: kernel test robot <lkp@intel.com>
To: David Hildenbrand <david@redhat.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [davidhildenbrand:fork_pat 1/1] include/linux/pgtable.h:1525:13: error: unused function 'untrack_pfn_copy'
Date: Tue, 25 Mar 2025 10:04:56 +0800 [thread overview]
Message-ID: <202503250935.Gm7ENdAr-lkp@intel.com> (raw)
tree: https://github.com/davidhildenbrand/linux fork_pat
head: 4474ef40921c064454fd03245526fc80f373873e
commit: 4474ef40921c064454fd03245526fc80f373873e [1/1] x86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range()
config: powerpc-randconfig-001-20250325 (https://download.01.org/0day-ci/archive/20250325/202503250935.Gm7ENdAr-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project c2692afc0a92cd5da140dfcdfff7818a5b8ce997)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250325/202503250935.Gm7ENdAr-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/202503250935.Gm7ENdAr-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from lib/test_bitops.c:12:
In file included from include/linux/slab.h:256:
In file included from include/linux/kasan.h:37:
>> include/linux/pgtable.h:1525:13: error: unused function 'untrack_pfn_copy' [-Werror,-Wunused-function]
1525 | static void untrack_pfn_copy(struct vm_area_struct *dst_vma, unsigned long pfn)
| ^~~~~~~~~~~~~~~~
1 error generated.
vim +/untrack_pfn_copy +1525 include/linux/pgtable.h
1520
1521 /*
1522 * untrack_pfn_copy is called when a VM_PFNMAP VMA failed to copy during
1523 * copy_page_range(), but after track_pfn_copy() was already called.
1524 */
> 1525 static void untrack_pfn_copy(struct vm_area_struct *dst_vma, unsigned long pfn)
1526 {
1527 }
1528
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-03-25 2:05 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=202503250935.Gm7ENdAr-lkp@intel.com \
--to=lkp@intel.com \
--cc=david@redhat.com \
--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