From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Miaohe Lin <linmiaohe@huawei.com>
Cc: Paul Gazzillo <paul@pgazz.com>,
Necip Fazil Yildiran <fazilyildiran@gmail.com>,
oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
kernel test robot <lkp@intel.com>
Subject: Re: kismet: WARNING: unmet direct dependencies detected for HUGETLBFS when selected by PPC_8xx
Date: Thu, 6 Feb 2025 09:47:18 +0100 [thread overview]
Message-ID: <5c99458f-4a91-485f-8a35-3618a992e2e4@csgroup.eu> (raw)
In-Reply-To: <d6c06a9c-4d43-4528-c5d1-019f91087f30@huawei.com>
Le 06/02/2025 à 08:12, Miaohe Lin a écrit :
> On 2025/2/6 14:30, Christophe Leroy wrote:
>>
>>
>> Le 06/02/2025 à 03:08, Miaohe Lin a écrit :
>>> On 2025/2/6 0:35, Christophe Leroy wrote:
>>>>
>>>>
>>>> Le 05/02/2025 à 03:39, Miaohe Lin a écrit :
>>>>> On 2025/1/24 6:24, kernel test robot wrote:
>>>>>> tree: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.kernel.org%2Fpub%2Fscm%2Flinux%2Fkernel%2Fgit%2Ftorvalds%2Flinux.git&data=05%7C02%7Cchristophe.leroy%40csgroup.eu%7C4568427e535f47ba6e7108dd467da005%7C8b87af7d86474dc78df45f69a2011bb5%7C0%7C0%7C638744227571348001%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=rpToSy%2BI2rTH5db2ST62gNZF0efdupnNQRpYevV2CRY%3D&reserved=0 master
>>>>>> head: d0d106a2bd21499901299160744e5fe9f4c83ddb
>>>>>> commit: f8142cf94d4737ea0c3baffb3b9bad8addcb9b6b hugetlb: make hugetlb depends on SYSFS or SYSCTL
>>>>>> date: 2 years, 4 months ago
>>>>>> config: powerpc-kismet-CONFIG_HUGETLBFS-CONFIG_PPC_8xx-0-0 (https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdownload.01.org%2F0day-ci%2Farchive%2F20250124%2F202501240611.LDmD2nkj-lkp%40intel.com%2Fconfig&data=05%7C02%7Cchristophe.leroy%40csgroup.eu%7C4568427e535f47ba6e7108dd467da005%7C8b87af7d86474dc78df45f69a2011bb5%7C0%7C0%7C638744227571371397%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=27pzb6aOPaarlX2fX%2B3%2FvCp8GWwysleJoVw9L6Yrytc%3D&reserved=0)
>>>>>> reproduce: (https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdownload.01.org%2F0day-ci%2Farchive%2F20250124%2F202501240611.LDmD2nkj-lkp%40intel.com%2Freproduce&data=05%7C02%7Cchristophe.leroy%40csgroup.eu%7C4568427e535f47ba6e7108dd467da005%7C8b87af7d86474dc78df45f69a2011bb5%7C0%7C0%7C638744227571381016%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=XEjM2tEaDz%2BINDJbCOD2ciJU24koPd9msdwNiP3lPLw%3D&reserved=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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flore.kernel.org%2Foe-kbuild-all%2F202501240611.LDmD2nkj-lkp%40intel.com%2F&data=05%7C02%7Cchristophe.leroy%40csgroup.eu%7C4568427e535f47ba6e7108dd467da005%7C8b87af7d86474dc78df45f69a2011bb5%7C0%7C0%7C638744227571390239%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=W%2F8GHsXQwmaG22bsTyQes1zdMG7o2aHc%2Fly%2BHO57LwI%3D&reserved=0
>>>>>
>>>>> Thanks for report. Sorry for late respond. I was on my Spring Festival vacation.
>>>>>
>>>>>>
>>>>>> kismet warnings: (new ones prefixed by >>)
>>>>>>>> kismet: WARNING: unmet direct dependencies detected for HUGETLBFS when selected by PPC_8xx
>>>>>> WARNING: unmet direct dependencies detected for HUGETLBFS
>>>>>> Depends on [n]: (X86 || IA64 || SPARC64 || ARCH_SUPPORTS_HUGETLBFS [=y] || BROKEN [=n]) && (SYSFS [=n] || SYSCTL [=n])
>>>>>> Selected by [y]:
>>>>>> - PPC_8xx [=y] && <choice>
>>>>>
>>>>> I am a bit confused. HUGETLBFS depends on SYSFS or SYSCTL. How can it be selected while SYSFS [=n] || SYSCTL [=n]?
>>>>> Or am I miss something?
>>>>
>>>> CONFIG_HUGETLBFS is selected by CONFIG_PPC_8xx, see commit 34536d780683 ("powerpc/8xx: Add a function to early map kernel via huge pages")
>>>
>>> Thanks for your providing. But I'm saying that since HUGETLBFS depends on (SYSFS or SYSCTL), how CONFIG_PPC_8xx succeeds to select it while
>>> SYSFS and SYSCTL are disabled? I'm not really familiar with Kconfig but I assume Kconfig will confirm that the dependencies are satisfied
>>> before HUGETLBFS is enabled. Or am I miss something?
>>
>> I suggest you read https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.kernel.org%2Fkbuild%2Fkconfig-language.html&data=05%7C02%7Cchristophe.leroy%40csgroup.eu%7C4568427e535f47ba6e7108dd467da005%7C8b87af7d86474dc78df45f69a2011bb5%7C0%7C0%7C638744227571400924%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=UtQJlI0P7JV%2BQy0jlHFoGZ8ipnl5SzhuL1G%2Bbr0an9Y%3D&reserved=0
>
> Thanks.
>
>>
>> Extract:
>>
>> Note:
>> select should be used with care. select will force a symbol to a value without visiting the dependencies. By abusing select you are able to select a symbol FOO even if FOO depends on BAR that is not set.
>
> IMHO, it seems it's the use of "select" breaks the dependencies and leads to the kismet warnings. So it might be better to fix the PPC_8xx side.
The dependencies are wrong, I have a kernel without CONFIG_SYSFS and
without CONFIG_SYSCTL and hugetlbfs works perfecly well.
I boot the kernel with following parameters:
hugepagesz=512k hugepages=8 hugepagesz=8M hugepages=2
dmesg shows:
[ 0.560754] HugeTLB: registered 512 KiB page size, pre-allocated 8 pages
[ 0.567293] HugeTLB: 0 KiB vmemmap can be freed for a 512 KiB page
[ 0.593912] HugeTLB: registered 8.00 MiB page size, pre-allocated 2 pages
[ 0.600543] HugeTLB: 0 KiB vmemmap can be freed for a 8.00 MiB page
hugetlb selftest works well:
:~# ./map_hugetlb 4 19
TAP version 13
1..1
# 512 kB hugepages
# Mapping 4 Mbytes
# Returned address is 0x77800000
# First hex is 0
# First hex is 10203
ok 1 Read correct data
# Totals: pass:1 fail:0 xfail:0 xpass:0 skip:0 error:0
~# ./map_hugetlb 16 23
TAP version 13
1..1
# 8192 kB hugepages
# Mapping 16 Mbytes
# Returned address is 0x76800000
# First hex is 0
# First hex is 10203
ok 1 Read correct data
# Totals: pass:1 fail:0 xfail:0 xpass:0 skip:0 error:0
So I think your commit f8142cf94d47 ("hugetlb: make hugetlb depends on
SYSFS or SYSCTL") is just wrong and has to be reverted.
Christophe
next prev parent reply other threads:[~2025-02-06 8:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 22:24 kernel test robot
2025-02-05 2:39 ` Miaohe Lin
2025-02-05 16:35 ` Christophe Leroy
2025-02-06 2:08 ` Miaohe Lin
2025-02-06 6:30 ` Christophe Leroy
2025-02-06 7:12 ` Miaohe Lin
2025-02-06 8:47 ` Christophe Leroy [this message]
2025-02-06 11:39 ` Miaohe Lin
-- strict thread matches above, loose matches on Subject: below --
2025-08-22 12:07 kernel test robot
2025-05-13 7:54 kernel test robot
2025-03-01 1:55 kernel test robot
2023-11-19 4:09 kernel test robot
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=5c99458f-4a91-485f-8a35-3618a992e2e4@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=akpm@linux-foundation.org \
--cc=fazilyildiran@gmail.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paul@pgazz.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