All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Jane Chu <jane.chu@oracle.com>
Cc: oe-kbuild-all@lists.linux.dev, 0day robot <lkp@intel.com>
Subject: mm/filemap.c:2768:undefined reference to `is_raw_hwpoison_page_in_folio'
Date: Thu, 18 Jun 2026 08:11:40 +0200	[thread overview]
Message-ID: <202606180853.3higmX1J-lkp@intel.com> (raw)

tree:   https://github.com/intel-lab-lkp/linux/commits/Jane-Chu/mm-memory-failure-make-is_raw_hwpoison_page_in_hugepage-general-purpose/20260618-012902
head:   ad6812ce0c4c46ffdd13060f0251f31b3412017b
commit: 12e5a24644d326a21bd49526746156ea59e376c4 mm: factor out adjust_range_hwpoison() from hugetlbfs
date:   13 hours ago
config: s390-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260618/202606180853.3higmX1J-lkp@intel.com/config)
compiler: s390x-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260618/202606180853.3higmX1J-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/202606180853.3higmX1J-lkp@intel.com/

All errors (new ones prefixed by >>):

   s390x-linux-gnu-ld: mm/filemap.o: in function `adjust_range_hwpoison':
>> mm/filemap.c:2768:(.text+0x1df4): undefined reference to `is_raw_hwpoison_page_in_folio'
>> s390x-linux-gnu-ld: mm/filemap.c:2777:(.text+0x1e2e): undefined reference to `is_raw_hwpoison_page_in_folio'
   s390x-linux-gnu-ld: mm/filemap.c:2777:(.text+0x1e58): undefined reference to `is_raw_hwpoison_page_in_folio'
   s390x-linux-gnu-ld: mm/filemap.c:2777:(.text+0x1e92): undefined reference to `is_raw_hwpoison_page_in_folio'
   s390x-linux-gnu-ld: mm/filemap.c:2777:(.text+0x1eb4): undefined reference to `is_raw_hwpoison_page_in_folio'


vim +2768 mm/filemap.c

  2752	
  2753	/**
  2754	 * adjust_range_hwpoison - adjust clean readable range to avoid hwpoison.
  2755	 * @folio: folio that contains hwpoison(s).
  2756	 * @offset: bytes into the folio where subsequent read starts.
  2757	 * @bytes: number of bytes wish to read.
  2758	 *
  2759	 * Return: adjusted total number of bytes starting off @offset that can be
  2760	 * safely read from the @folio.
  2761	 */
  2762	size_t adjust_range_hwpoison(struct folio *folio, size_t offset,
  2763			size_t bytes)
  2764	{
  2765		struct page *page = folio_page(folio, offset / PAGE_SIZE);
  2766		size_t safe_bytes;
  2767	
> 2768		if (is_raw_hwpoison_page_in_folio(page))
  2769			return 0;
  2770	
  2771		/* Safe to read the remaining bytes in this page. */
  2772		safe_bytes = PAGE_SIZE - (offset % PAGE_SIZE);
  2773		page++;
  2774	
  2775		/* Check each remaining page as long as we are not done yet. */
  2776		for (; safe_bytes < bytes; safe_bytes += PAGE_SIZE, page++)
> 2777			if (is_raw_hwpoison_page_in_folio(page))
  2778				break;
  2779	
  2780		return min(safe_bytes, bytes);
  2781	}
  2782	EXPORT_SYMBOL_GPL(adjust_range_hwpoison);
  2783	

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

                 reply	other threads:[~2026-06-18  6:12 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=202606180853.3higmX1J-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=jane.chu@oracle.com \
    --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 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.