From: kernel test robot <lkp@intel.com>
To: Juan Yescas <jyescas@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>, Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>, Zi Yan <ziy@nvidia.com>,
linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
tjmercier@google.com, isaacmanjarres@google.com,
kaleshsingh@google.com, Minchan Kim <minchan@kernel.org>
Subject: Re: [PATCH v5] mm: Add CONFIG_PAGE_BLOCK_ORDER to select page block order
Date: Sun, 18 May 2025 19:05:43 +0800 [thread overview]
Message-ID: <202505181825.FdKgAQ16-lkp@intel.com> (raw)
In-Reply-To: <20250516232341.659513-1-jyescas@google.com>
Hi Juan,
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/Juan-Yescas/mm-Add-CONFIG_PAGE_BLOCK_ORDER-to-select-page-block-order/20250517-072434
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link: https://lore.kernel.org/r/20250516232341.659513-1-jyescas%40google.com
patch subject: [PATCH v5] mm: Add CONFIG_PAGE_BLOCK_ORDER to select page block order
config: i386-randconfig-r072-20250518 (https://download.01.org/0day-ci/archive/20250518/202505181825.FdKgAQ16-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
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/202505181825.FdKgAQ16-lkp@intel.com/
smatch warnings:
mm/compaction.c:302 pageblock_skip_persistent() warn: always true condition '(compound_order(page) >= (((((22 - 12))) < ((0))) ?(((22 - 12))):((0)))) => (0-u32max >= 0)'
mm/page_alloc.c:618 compaction_capture() warn: unsigned 'order' is never less than zero.
vim +302 mm/compaction.c
9721fd82351d47a Baolin Wang 2023-06-14 289
21dc7e023611fbc David Rientjes 2017-11-17 290 /*
2271b016bf368d1 Hui Su 2020-12-14 291 * Compound pages of >= pageblock_order should consistently be skipped until
b527cfe5bc23208 Vlastimil Babka 2017-11-17 292 * released. It is always pointless to compact pages of such order (if they are
b527cfe5bc23208 Vlastimil Babka 2017-11-17 293 * migratable), and the pageblocks they occupy cannot contain any free pages.
21dc7e023611fbc David Rientjes 2017-11-17 294 */
b527cfe5bc23208 Vlastimil Babka 2017-11-17 295 static bool pageblock_skip_persistent(struct page *page)
21dc7e023611fbc David Rientjes 2017-11-17 296 {
b527cfe5bc23208 Vlastimil Babka 2017-11-17 297 if (!PageCompound(page))
21dc7e023611fbc David Rientjes 2017-11-17 298 return false;
b527cfe5bc23208 Vlastimil Babka 2017-11-17 299
b527cfe5bc23208 Vlastimil Babka 2017-11-17 300 page = compound_head(page);
b527cfe5bc23208 Vlastimil Babka 2017-11-17 301
b527cfe5bc23208 Vlastimil Babka 2017-11-17 @302 if (compound_order(page) >= pageblock_order)
21dc7e023611fbc David Rientjes 2017-11-17 303 return true;
b527cfe5bc23208 Vlastimil Babka 2017-11-17 304
b527cfe5bc23208 Vlastimil Babka 2017-11-17 305 return false;
21dc7e023611fbc David Rientjes 2017-11-17 306 }
21dc7e023611fbc David Rientjes 2017-11-17 307
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-05-18 11:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 23:23 Juan Yescas
2025-05-17 18:39 ` kernel test robot
2025-05-18 5:23 ` kernel test robot
2025-05-18 11:05 ` kernel test robot [this message]
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=202505181825.FdKgAQ16-lkp@intel.com \
--to=lkp@intel.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=isaacmanjarres@google.com \
--cc=jyescas@google.com \
--cc=kaleshsingh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=tjmercier@google.com \
--cc=vbabka@suse.cz \
--cc=ziy@nvidia.com \
/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