From: kernel test robot <lkp@intel.com>
To: Wupeng Ma <mawupeng1@huawei.com>,
akpm@linux-foundation.org, david@redhat.com, osalvador@suse.de,
nao.horiguchi@gmail.com, linmiaohe@huawei.com, mhocko@suse.com
Cc: oe-kbuild-all@lists.linux.dev, mawupeng1@huawei.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] mm: memory-failure: update ttu flag inside unmap_poisoned_folio
Date: Fri, 17 Jan 2025 12:49:50 +0800 [thread overview]
Message-ID: <202501171215.KLa8VDaS-lkp@intel.com> (raw)
In-Reply-To: <20250116061657.227027-2-mawupeng1@huawei.com>
Hi Wupeng,
kernel test robot noticed the following build warnings:
[auto build test WARNING on akpm-mm/mm-everything]
url: https://github.com/intel-lab-lkp/linux/commits/Wupeng-Ma/mm-memory-failure-update-ttu-flag-inside-unmap_poisoned_folio/20250116-142614
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link: https://lore.kernel.org/r/20250116061657.227027-2-mawupeng1%40huawei.com
patch subject: [PATCH v2 1/3] mm: memory-failure: update ttu flag inside unmap_poisoned_folio
config: x86_64-buildonly-randconfig-002-20250117 (https://download.01.org/0day-ci/archive/20250117/202501171215.KLa8VDaS-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/20250117/202501171215.KLa8VDaS-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/202501171215.KLa8VDaS-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from mm/memory_hotplug.c:41:
mm/internal.h:1142:1: error: expected identifier or '(' before '{' token
1142 | {
| ^
>> mm/internal.h:1141:19: warning: 'unmap_poisoned_folio' used but never defined
1141 | static inline int unmap_poisoned_folio(struct folio *folio, unsigned long pfn, bool must_kill);
| ^~~~~~~~~~~~~~~~~~~~
vim +/unmap_poisoned_folio +1141 mm/internal.h
1121
1122 extern u32 hwpoison_filter_dev_major;
1123 extern u32 hwpoison_filter_dev_minor;
1124 extern u64 hwpoison_filter_flags_mask;
1125 extern u64 hwpoison_filter_flags_value;
1126 extern u64 hwpoison_filter_memcg;
1127 extern u32 hwpoison_filter_enable;
1128 #define MAGIC_HWPOISON 0x48575053U /* HWPS */
1129 void SetPageHWPoisonTakenOff(struct page *page);
1130 void ClearPageHWPoisonTakenOff(struct page *page);
1131 bool take_page_off_buddy(struct page *page);
1132 bool put_page_back_buddy(struct page *page);
1133 struct task_struct *task_early_kill(struct task_struct *tsk, int force_early);
1134 void add_to_kill_ksm(struct task_struct *tsk, const struct page *p,
1135 struct vm_area_struct *vma, struct list_head *to_kill,
1136 unsigned long ksm_addr);
1137 unsigned long page_mapped_in_vma(const struct page *page,
1138 struct vm_area_struct *vma);
1139
1140 #else
> 1141 static inline int unmap_poisoned_folio(struct folio *folio, unsigned long pfn, bool must_kill);
1142 {
1143 return -EBUSY;
1144 }
1145 #endif
1146
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-01-17 4:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 6:16 [PATCH v2 0/3] mm: memory_failure: unmap poisoned filio during migrate properly Wupeng Ma
2025-01-16 6:16 ` [PATCH v2 1/3] mm: memory-failure: update ttu flag inside unmap_poisoned_folio Wupeng Ma
2025-01-17 3:57 ` kernel test robot
2025-01-17 4:16 ` mawupeng
2025-01-17 4:39 ` kernel test robot
2025-01-17 4:49 ` kernel test robot [this message]
2025-01-20 6:24 ` Miaohe Lin
2025-01-20 7:49 ` David Hildenbrand
2025-01-20 8:46 ` David Hildenbrand
2025-01-21 3:20 ` Miaohe Lin
2025-01-21 7:58 ` David Hildenbrand
2025-01-22 7:38 ` Miaohe Lin
2025-01-21 2:46 ` Miaohe Lin
2025-01-20 9:06 ` mawupeng
2025-01-20 7:55 ` David Hildenbrand
2025-01-16 6:16 ` [PATCH v2 2/3] hwpoison, memory_hotplug: lock folio before unmap hwpoisoned folio Wupeng Ma
2025-01-20 9:25 ` David Hildenbrand
2025-01-16 6:16 ` [PATCH v2 3/3] mm: memory-hotplug: check folio ref count first in do_migrate_rang Wupeng Ma
2025-01-20 6:32 ` Miaohe Lin
2025-01-21 2:17 ` mawupeng
2025-01-20 8:01 ` David Hildenbrand
2025-01-20 9:11 ` mawupeng
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=202501171215.KLa8VDaS-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mawupeng1@huawei.com \
--cc=mhocko@suse.com \
--cc=nao.horiguchi@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=osalvador@suse.de \
/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