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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aBWscQBhh9qRmxAY@gpd3>
Date: Sat, 3 May 2025 07:41:05 +0200
From: Andrea Righi <arighi@...dia.com>
To: Ihor Solodrai <ihor.solodrai@...ux.dev>
Cc: Tejun Heo <tj@...nel.org>, Changwoo Min <changwoo@...lia.com>,
	Alexei Starovoitov <ast@...nel.org>, bpf@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: selftests/sched_ext: testing on BPF CI

Hi Ihor,

On Fri, May 02, 2025 at 02:40:45PM -0700, Ihor Solodrai wrote:
> On 2025-01-28 4:21 p.m., Ihor Solodrai wrote:
> > Hi Tejun, Andrea.
> > 
> > I tested a couple of variants of bpf-next + sched_ext source tree,
> > just sharing the results.
> > 
> > I found a working state: BPF CI pipeline ran successfully twice
> > (that's 8 build + run of selftests/sched_ext/runner in total).
> > 
> > Working state requires most patches between sched_ext/master and
> > sched_ext/for-6.14-fixes [1], and also the patch
> >    "tools/sched_ext: Receive updates from SCX repo" [2]
> > 
> > On plain bpf-next the dsp_local_on test fails [3].
> > Without the patch [2] there is a build error [4]: missing
> > SCX_ENUM_INIT definition.
> > 
> > We probably don't want to enable selftests/sched_ext on BPF CI with
> > that many "temporary" patches. I suggest to wait until all of this is
> > merged upstream.
> > 
> 
> Hi everyone. I tried enabling sched_ext selftests on CI today, and there
> are no issues on bpf-next tip (f263336a41da).
> 
> https://github.com/kernel-patches/vmtest/actions/runs/14802453691
> 
> If there are no objections, I'm going to push this to BPF CI on Monday.
> 
> As a reminder, this means that selftests/sched_ext test runner will be built
> and executed for pending BPF patches, and BPF CI pipeline will fail in case
> of problems there.

I don't have any objection. The sched_ext selftests are in a stable state
now and I think it's a good idea to run them periodically against the
latest BPF patches to catch potential breakages early.

Thanks,
-Andrea

> 
> > You can check the full list of patches here:
> > https://github.com/kernel-patches/vmtest/pull/332/files
> > 
> > [1] https://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext.git/log/?h=for-6.14-fixes
> > [2] https://lore.kernel.org/all/Z1ucTqJP8IeIXZql@slm.duckdns.org/
> > [3] https://github.com/kernel-patches/vmtest/actions/runs/13019837022
> > [4] https://github.com/kernel-patches/vmtest/actions/runs/13020458479
> 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ