linux-kernel - Re: [PATCH bpf-next] selftests/bpf: Update the aarch64 tests deny list

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: <CABRcYm+O-_GGhnAmJW6_=9vKeKSvzVLcxBRq3Pfjb3W0_HNjhw@mail.gmail.com>
Date:   Thu, 27 Apr 2023 16:52:29 +0200
From:   Florent Revest <revest@...omium.org>
To:     bpf@...r.kernel.org, linux-kernel@...r.kernel.org
Cc:     ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
        kpsingh@...nel.org, mykolal@...com, martin.lau@...ux.dev,
        song@...nel.org, xukuohai@...weicloud.com, mark.rutland@....com
Subject: Re: [PATCH bpf-next] selftests/bpf: Update the aarch64 tests deny list

On Thu, Apr 27, 2023 at 4:32 PM Florent Revest <revest@...omium.org> wrote:
>
> This patch updates the list of BPF selftests which are known to fail so
> the BPF CI can validate the tests which pass now.

Note: I tested this denylist a few months back by sending a manual PR
to https://github.com/kernel-patches/bpf.
At the time, it worked
https://github.com/kernel-patches/bpf/actions/runs/4106542133/jobs/7085514761
(even though there seemed to be a known flake in the gcc variant but
unrelated to the new arch support)

Every time I wanted to have the CI run on my PRs, I had to annoy Manu
by email (I wouldn't have the rights to trigger the CI by myself
otherwise). So I haven't tested this *actual* patch rebased on the
current CI before sending it to the list. (e.g. the
module_fentry_shadow test has been added since then and I just assumed
it would pass in CI like the rest)

My understanding is that this patch should soon be picked up by the
testing bot and we can use that CI run to check that everything works
as intended. Let's wait for a CI green light before merging this! :)
If there are errors I'll send a v2