From: kernel test robot <lkp@intel.com>
To: Wupeng Ma <mawupeng1@huawei.com>,
akpm@linux-foundation.org, dave.hansen@linux.intel.com,
luto@kernel.org, tglx@linutronix.de, peterz@infradead.org
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
x86@kernel.org, mawupeng1@huawei.com, bp@suse.de,
mingo@redhat.com
Subject: Re: [PATCH v3 1/3] x86/mm/pat: Move follow_phys to pat-related file
Date: Fri, 12 Jan 2024 22:55:19 +0800 [thread overview]
Message-ID: <202401122234.MfmlPf9b-lkp@intel.com> (raw)
In-Reply-To: <20240111120929.2694440-2-mawupeng1@huawei.com>
Hi Wupeng,
kernel test robot noticed the following build errors:
[auto build test ERROR on akpm-mm/mm-everything]
[also build test ERROR on tip/x86/mm tip/master linus/master v6.7 next-20240112]
[cannot apply to tip/auto-latest]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Wupeng-Ma/x86-mm-pat-Move-follow_phys-to-pat-related-file/20240111-201305
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link: https://lore.kernel.org/r/20240111120929.2694440-2-mawupeng1%40huawei.com
patch subject: [PATCH v3 1/3] x86/mm/pat: Move follow_phys to pat-related file
config: i386-randconfig-012-20240112 (https://download.01.org/0day-ci/archive/20240112/202401122234.MfmlPf9b-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240112/202401122234.MfmlPf9b-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/202401122234.MfmlPf9b-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from include/linux/mm.h:29,
from include/linux/memblock.h:12,
from arch/x86/mm/pat/memtype.c:35:
arch/x86/mm/pat/memtype.c: In function 'follow_phys':
>> include/linux/pgtable.h:103:9: error: implicit declaration of function 'kunmap_local' [-Werror=implicit-function-declaration]
103 | kunmap_local((pte)); \
| ^~~~~~~~~~~~
include/linux/mm.h:2965:9: note: in expansion of macro 'pte_unmap'
2965 | pte_unmap(pte); \
| ^~~~~~~~~
arch/x86/mm/pat/memtype.c:976:9: note: in expansion of macro 'pte_unmap_unlock'
976 | pte_unmap_unlock(ptep, ptl);
| ^~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/kunmap_local +103 include/linux/pgtable.h
974b9b2c68f3d3 Mike Rapoport 2020-06-08 98
0d940a9b270b92 Hugh Dickins 2023-06-08 99 #ifdef CONFIG_HIGHPTE
0d940a9b270b92 Hugh Dickins 2023-06-08 100 #define __pte_map(pmd, address) \
0d940a9b270b92 Hugh Dickins 2023-06-08 101 ((pte_t *)kmap_local_page(pmd_page(*(pmd))) + pte_index((address)))
0d940a9b270b92 Hugh Dickins 2023-06-08 102 #define pte_unmap(pte) do { \
0d940a9b270b92 Hugh Dickins 2023-06-08 @103 kunmap_local((pte)); \
a349d72fd9efc8 Hugh Dickins 2023-07-11 104 rcu_read_unlock(); \
0d940a9b270b92 Hugh Dickins 2023-06-08 105 } while (0)
974b9b2c68f3d3 Mike Rapoport 2020-06-08 106 #else
0d940a9b270b92 Hugh Dickins 2023-06-08 107 static inline pte_t *__pte_map(pmd_t *pmd, unsigned long address)
0d940a9b270b92 Hugh Dickins 2023-06-08 108 {
0d940a9b270b92 Hugh Dickins 2023-06-08 109 return pte_offset_kernel(pmd, address);
0d940a9b270b92 Hugh Dickins 2023-06-08 110 }
0d940a9b270b92 Hugh Dickins 2023-06-08 111 static inline void pte_unmap(pte_t *pte)
0d940a9b270b92 Hugh Dickins 2023-06-08 112 {
a349d72fd9efc8 Hugh Dickins 2023-07-11 113 rcu_read_unlock();
0d940a9b270b92 Hugh Dickins 2023-06-08 114 }
974b9b2c68f3d3 Mike Rapoport 2020-06-08 115 #endif
974b9b2c68f3d3 Mike Rapoport 2020-06-08 116
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-01-12 14:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 12:09 [PATCH v3 0/3] Cleanup for PAT Wupeng Ma
2024-01-11 12:09 ` [PATCH v3 1/3] x86/mm/pat: Move follow_phys to pat-related file Wupeng Ma
2024-01-12 14:55 ` kernel test robot [this message]
2024-01-11 12:09 ` [PATCH v3 2/3] x86/mm/pat: Cleanup unused parameter in follow_phys Wupeng Ma
2024-01-12 6:35 ` kernel test robot
2024-01-12 10:49 ` kernel test robot
2024-01-11 12:09 ` [PATCH v3 3/3] x86/mm/pat: Remove WARN_ON_ONCE if follow_phys fails Wupeng Ma
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=202401122234.MfmlPf9b-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bp@suse.de \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mawupeng1@huawei.com \
--cc=mingo@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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