From: Wei Yang <richard.weiyang@gmail.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: oe-kbuild@lists.linux.dev, Wei Yang <richard.weiyang@gmail.com>,
willy@infradead.org, akpm@linux-foundation.org, david@kernel.org,
lorenzo.stoakes@oracle.com, Liam.Howlett@oracle.com,
vbabka@suse.cz, rppt@kernel.org, surenb@google.com,
mhocko@suse.com, ziy@nvidia.com, baolin.wang@linux.alibaba.com,
npache@redhat.com, ryan.roberts@arm.com, dev.jain@arm.com,
baohua@kernel.org, lance.yang@linux.dev, lkp@intel.com,
oe-kbuild-all@lists.linux.dev, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH] mm/huge_memory: consolidate order-related checks into folio_split_supported()
Date: Wed, 19 Nov 2025 12:39:05 +0000 [thread overview]
Message-ID: <20251119123905.ak67ykufvfr4iulr@master> (raw)
In-Reply-To: <202511151652.GKPwEctt-lkp@intel.com>
On Wed, Nov 19, 2025 at 03:37:09PM +0300, Dan Carpenter wrote:
>Hi Wei,
>
>kernel test robot noticed the following build warnings:
>
>url: https://github.com/intel-lab-lkp/linux/commits/Wei-Yang/mm-huge_memory-consolidate-order-related-checks-into-folio_split_supported/20251114-155833
>base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
>patch link: https://lore.kernel.org/r/20251114075703.10434-1-richard.weiyang%40gmail.com
>patch subject: [PATCH] mm/huge_memory: consolidate order-related checks into folio_split_supported()
>config: i386-randconfig-141-20251115 (https://download.01.org/0day-ci/archive/20251115/202511151652.GKPwEctt-lkp@intel.com/config)
>compiler: gcc-12 (Debian 12.4.0-5) 12.4.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>
>| Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
>| Closes: https://lore.kernel.org/r/202511151652.GKPwEctt-lkp@intel.com/
>
>smatch warnings:
>mm/huge_memory.c:3696 folio_split_supported() warn: signedness bug returning '(-22)'
>
>vim +3696 mm/huge_memory.c
>
>aa27253af32c74 Wei Yang 2025-11-06 3690 bool folio_split_supported(struct folio *folio, unsigned int new_order,
> ^^^^
>This is a bool function.
>
>aa27253af32c74 Wei Yang 2025-11-06 3691 enum split_type split_type, bool warns)
>58729c04cf1092 Zi Yan 2025-03-07 3692 {
>ab62f1bb0caaa5 Wei Yang 2025-11-14 3693 const int old_order = folio_order(folio);
>ab62f1bb0caaa5 Wei Yang 2025-11-14 3694
>ab62f1bb0caaa5 Wei Yang 2025-11-14 3695 if (new_order >= old_order)
>ab62f1bb0caaa5 Wei Yang 2025-11-14 @3696 return -EINVAL;
Thanks, this is noticed.
>
>s/-EINVAL/false/
>
>ab62f1bb0caaa5 Wei Yang 2025-11-14 3697
>58729c04cf1092 Zi Yan 2025-03-07 3698 if (folio_test_anon(folio)) {
>58729c04cf1092 Zi Yan 2025-03-07 3699 /* order-1 is not supported for anonymous THP. */
>58729c04cf1092 Zi Yan 2025-03-07 3700 VM_WARN_ONCE(warns && new_order == 1,
>58729c04cf1092 Zi Yan 2025-03-07 3701 "Cannot split to order-1 folio");
>28753037121116 Zi Yan 2025-11-05 3702 if (new_order == 1)
>28753037121116 Zi Yan 2025-11-05 3703 return false;
>
>--
>0-DAY CI Kernel Test Service
>https://github.com/intel/lkp-tests/wiki
--
Wei Yang
Help you, Help me
prev parent reply other threads:[~2025-11-19 12:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 7:57 Wei Yang
2025-11-14 8:49 ` David Hildenbrand (Red Hat)
2025-11-14 12:43 ` Zi Yan
2025-11-14 14:30 ` Wei Yang
2025-11-14 20:53 ` Zi Yan
2025-11-15 2:42 ` Wei Yang
2025-11-14 15:03 ` Wei Yang
2025-11-14 19:36 ` David Hildenbrand (Red Hat)
2025-11-15 2:51 ` Wei Yang
2025-11-15 5:07 ` Matthew Wilcox
2025-11-15 9:43 ` Wei Yang
2025-12-04 15:13 ` Wei Yang
2025-11-19 12:37 ` Dan Carpenter
2025-11-19 12:39 ` Wei Yang [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=20251119123905.ak67ykufvfr4iulr@master \
--to=richard.weiyang@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=dan.carpenter@linaro.org \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=lance.yang@linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=npache@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oe-kbuild@lists.linux.dev \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--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