From: wang lian <lianux.mm@gmail.com>
To: ziy@nvidia.com
Cc: Liam.Howlett@oracle.com, akpm@linux-foundation.org,
brauner@kernel.org, david@redhat.com, gkwang@linx-info.com,
jannh@google.com, lianux.mm@gmail.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-mm@kvack.org, lorenzo.stoakes@oracle.com,
p1ucky0923@gmail.com, ryncsn@gmail.com, shuah@kernel.org,
sj@kernel.org, vbabka@suse.cz, zijing.zhang@proton.me
Subject: Re: [PATCH v3] selftests/mm: add process_madvise() tests
Date: Wed, 9 Jul 2025 20:32:24 +0800 [thread overview]
Message-ID: <20250709123224.6593-1-lianux.mm@gmail.com> (raw)
In-Reply-To: <48D7AAD0-07C9-4E2D-9171-081A503B47AF@nvidia.com>
Hi Zi Yan,
Thanks for testing the patch and reporting this build failure.
I don't have an arm64 environment readily available for testing, so I
appreciate you catching this. I suspect this is caused by missing or
older userspace headers in the cross-compilation toolchain.
I will try to fix this in the next version. If the problem persists, a
good solution would be to manually define the syscall wrapper to avoid
the dependency on <sys/pidfd.h>.
I'll send out a v4 with a fix.
Thanks again for your help.
Best regards,
Wang Lian
next prev parent reply other threads:[~2025-07-09 12:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 4:43 wang lian
2025-07-05 19:32 ` Lorenzo Stoakes
2025-07-06 6:07 ` [PATCH v3] selftests/vm: Add tests for process_madvise() 王炼
2025-07-08 17:44 ` [PATCH v3] selftests/mm: add process_madvise() tests Zi Yan
2025-07-09 12:32 ` wang lian [this message]
2025-07-09 12:51 ` Lorenzo Stoakes
2025-07-10 11:29 ` wang lian
2025-07-09 14:46 ` Zi Yan
2025-07-10 8:42 ` Mark Brown
2025-07-10 16:28 ` Zi Yan
2025-07-11 8:34 ` Mark Brown
2025-07-11 8:49 ` Lorenzo Stoakes
2025-07-11 12:09 ` wang lian
2025-07-10 11:40 ` wang lian
2025-07-10 13:42 [PATCH v4] " Mark Brown
2025-07-11 12:19 ` [PATCH v3] " wang lian
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=20250709123224.6593-1-lianux.mm@gmail.com \
--to=lianux.mm@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=david@redhat.com \
--cc=gkwang@linx-info.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=p1ucky0923@gmail.com \
--cc=ryncsn@gmail.com \
--cc=shuah@kernel.org \
--cc=sj@kernel.org \
--cc=vbabka@suse.cz \
--cc=zijing.zhang@proton.me \
--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
all inboxes | Powered by JetHome®