linux-kernel - Re: [PATCH v3] selftests/mm: add process

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <9aa51324-10b7-4bd0-9d83-5722d1ea0628@lucifer.local>
Date: Wed, 9 Jul 2025 13:51:35 +0100
From: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
To: wang lian <lianux.mm@...il.com>
Cc: ziy@...dia.com, Liam.Howlett@...cle.com, akpm@...ux-foundation.org,
        brauner@...nel.org, david@...hat.com, gkwang@...x-info.com,
        jannh@...gle.com, linux-kernel@...r.kernel.org,
        linux-kselftest@...r.kernel.org, linux-mm@...ck.org,
        p1ucky0923@...il.com, ryncsn@...il.com, sj@...nel.org, vbabka@...e.cz,
        zijing.zhang@...ton.me
Subject: Re: [PATCH v3] selftests/mm: add process_madvise() tests

On Wed, Jul 09, 2025 at 08:32:24PM +0800, wang lian wrote:
> 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

Hi Wang,

Please try to include the context of what you're replying to in your
messages, reading the above I have to _just remember_ what Zi said, and I'm
old so that's hard now ;)

Please note that mm tests _must_ work without make headers_install being
run.

Your test must not rely upon those.

Thanks, Lorenzo