linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Yunsheng Lin <linyunsheng@huawei.com>
To: Kevin Brodsky <kevin.brodsky@arm.com>, <linux-mm@kvack.org>,
	<linux-kselftest@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	David Hildenbrand <david@kernel.org>,
	Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	Mark Brown <broonie@kernel.org>,
	Ryan Roberts <ryan.roberts@arm.com>,
	Shuah Khan <shuah@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH 1/4] selftests/mm: remove flaky header check
Date: Thu, 18 Dec 2025 15:21:37 +0800	[thread overview]
Message-ID: <1f87565f-46e5-4281-a3af-64c6a8235848@huawei.com> (raw)
In-Reply-To: <c59eb8d7-c6bb-4618-b7d4-2ce5df88b5f1@arm.com>

On 2025/12/17 17:58, Kevin Brodsky wrote:
> On 17/12/2025 04:18, Yunsheng Lin wrote:
>> On 2025/12/16 22:26, Kevin Brodsky wrote:
>>> Commit 96ed62ea0298 ("mm: page_frag: fix a compile error when kernel
>>> is not compiled") introduced a check to avoid attempting to build
>>> the page_frag module if <linux/page_frag_cache.h> is missing.
>>>
>>> Unfortunately this check only works if KDIR points to
>>> /lib/modules/... or an in-tree kernel build. It always fails if KDIR
>>> points to an out-of-tree build (i.e. when the kernel was built with
>>> O=$KDIR make) because only generated headers are present under
>>> $KDIR/include/ in that case.
>>>
>>> <linux/page_frag_cache.h> was added more than a year ago (v6.13) so
>>> we can probably live without that check.
>> As some commercial OS still uses v6.6, I am wondering if we need that
> 
> Fair point, I hadn't considered that kselftests are supposed to be
> buildable against older stable kernels.
> 
>> check for a little longer, is it possible to do something like below to
>> avoid the flaky check?
>>
>> @@ -46,7 +46,8 @@ CFLAGS += -U_FORTIFY_SOURCE
>>
>>  KDIR ?= /lib/modules/$(shell uname -r)/build
>>  ifneq (,$(wildcard $(KDIR)/Module.symvers))
>> -ifneq (,$(wildcard $(KDIR)/include/linux/page_frag_cache.h))
>> +KSRC := $(shell readlink -f $(KDIR)/source 2>/dev/null || echo $(KDIR))
>> +ifneq (,$(wildcard $(KSRC)/include/linux/page_frag_cache.h))
>>  TEST_GEN_MODS_DIR := page_frag
>>  else
>>  PAGE_FRAG_WARNING = "missing page_frag_cache.h, please use a newer kernel"
> 
> That seems reasonable, and it works for my out-of-tree setup.
> 
> Will do that in v2, shall I add your Suggested-by, or maybe Co-developed-by?

Yes if you want to go that direction.


  reply	other threads:[~2025-12-18  7:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-16 14:26 [PATCH 0/4] Various mm kselftests improvements/fixes Kevin Brodsky
2025-12-16 14:26 ` [PATCH 1/4] selftests/mm: remove flaky header check Kevin Brodsky
2025-12-17  3:18   ` Yunsheng Lin
2025-12-17  9:58     ` Kevin Brodsky
2025-12-18  7:21       ` Yunsheng Lin [this message]
2025-12-17 10:04   ` Mark Brown
2025-12-18 13:24     ` Kevin Brodsky
2025-12-18 14:25       ` Mark Brown
2025-12-29 15:40         ` Kevin Brodsky
2025-12-16 14:26 ` [PATCH 2/4] selftests/mm: pass down full CC and CFLAGS to check_config.sh Kevin Brodsky
2025-12-18  8:04   ` David Hildenbrand (Red Hat)
2025-12-16 14:26 ` [PATCH 3/4] selftests/mm: fix faulting-in code in pagemap_ioctl test Kevin Brodsky
2025-12-16 14:56   ` Ryan Roberts
2025-12-16 15:11     ` Kevin Brodsky
2025-12-18  8:05     ` David Hildenbrand (Red Hat)
2025-12-18 13:18       ` Kevin Brodsky
2025-12-19  8:29         ` David Hildenbrand (Red Hat)
2025-12-29 11:46           ` Kevin Brodsky
2025-12-16 14:26 ` [PATCH 4/4] selftests/mm: fix exit code in pagemap_ioctl Kevin Brodsky
2025-12-16 14:58   ` Ryan Roberts
2025-12-17 10:08   ` Mark Brown
2025-12-18 13:20     ` Kevin Brodsky
2025-12-18  8:07   ` David Hildenbrand (Red Hat)

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=1f87565f-46e5-4281-a3af-64c6a8235848@huawei.com \
    --to=linyunsheng@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=david@kernel.org \
    --cc=kevin.brodsky@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=pabeni@redhat.com \
    --cc=ryan.roberts@arm.com \
    --cc=shuah@kernel.org \
    /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